View Single Post
Posts: 146 | Thanked: 1,615 times | Joined on Dec 2016
#35
Originally Posted by wicket View Post
As you've probably already noticed, I've been adding comments to the GitHub issues where I feel I my input might be useful. The spaghetti Fremantle boot process might be interesting. I'll take a look at what Leste is currently doing to bring up Hildon and get back to you on that one.



My vision of free mobile Linux is to start off with a solid base. By this I mean build off mainline Linux and build on top of an existing mainstream distro. When starting out small, it's the only sustainable way of keeping it up to date and to ensure that security fixes are delivered in a timely manner. Leste is the first mobile Linux to get this right. postmarketOS half got it right but it's more focused on being an after-market OS for Android devices where mainline Linux is a secondary goal.

I'm actually less concerned about the GUI. Hildon is obviously a welcome addition. We need a GUI anyway.

I wanted to create a device independent mobile Linux base, based the above ideas. My plan was to create a free version and a non-free version. The non-free version would be something somewhat similar to Leste and would include blobs needed to make it as functional as possible. The free version would obviously be less functional but in the case of the N900 for example, all that would be missing would be video acceleration, Wi-Fi and Bluetooth.

I think there is a need for a mobile OS that can be 100% vetted and this can only be done with free software. The US has virtually complete control all mobile operating systems and I'm surprised this sits well with most countries. I often wonder what kind of mobile phones are issued by non-US governments to their officials. It seems that only the Russians were smart enough to realise the problem. They funded some ex-Nokia employees to make a certain OS well known to this forum . Unfortunately they don't want to share all of it with the rest of the world and most ports are stuck with Android kernel forks.

You've seen my list of mainline Linux devices. My next list will be of SoCs used in modern phones which already have mainline support but no device support other than dev/evaluation boards. A lot of people are unaware how much work has already been done in mainline. Like I said in my previous post, I want too try to encourage contributions and it might help if more people knew they would not need to start from scratch.

That's the basis of my vision. I could elaborate more but that's a discussion for another day.
So we can have a functional Maemo Leste with some blobs, and then with Maemo Libre™ being a deblobbed version of Maemo Leste?

Agreed on the whole base discussion. We have similar ideas/thoughts.

Originally Posted by wicket View Post
I found the image-builder and jenkins-integration repos on GitHub so I'll see if I can figure it out.

I've not had a chance to talk on Freenode yet, I can probably get on there tomorrow.
Just to clarify -- we use Jenkins to build packages for the repo. I don't think it makes sense to for everyone to set up their own Jenkins instance. What I and freemangordon usually do is to develop on a amd64 VM or just on the device itself (this is what I do most of the time) and then build & test. When it's done, commit and have someone (currently, me or parazyd) rebuild the package in Jenkins.

We can definitely give some people access to Jenkins. From the UI one can rebuild packages easily.

Adding packages to Jenkins requires shell access to the jenkins account.

As for the building the image, I think it's completely separate -- I think it's a debootstrap on steriods + kernel building + other stacking scripts. You can just use our repos when doing that.

Right now most open tasks don't require one to set up their own Jenkins or build their own image, I think. When I help parazyd with debugging an image, I just test the image, fix that needs to be fixed (kernel params, packages missing, wrong versions, missing scripts, config) and then let him know. And then makes a new image - repeat.
 

The Following 10 Users Say Thank You to Wizzup_ For This Useful Post: