(→Linux Kernel developers sponsored by Openmoko)
(Removed list of peope. Don't ask me why.)
|Line 162:||Line 162:|
* [https://docs.openmoko.org/trac/ticket/2235 #2235 : Monochrome display on resume]
* [https://docs.openmoko.org/trac/ticket/2235 #2235 : Monochrome display on resume]
Revision as of 11:36, 27 February 2009
Is this page meant for you?
This information is mostly useful for developers and power/curious users. If you are looking for a kernel to flash into your GTA01/GTA02 you might want to grab one from the daily builds (scroll down and you'll find it) or get one that ships with one of the Distributions. The good thing with daily builds is that the newest might be the better. The bad thing of daily builds might be that you can get a broken kernel. If you feel way too uncomfortable making decisions about which kernel to try first and you are not willing to spend the time finding out which one works for you, then this page is not meant for you and you should be looking for stable Distributions instead. The distributors make this easier for for you. You might want to scroll down for the for the blessed kernels in the daily builds.
Right now there is an ongoing effort to reduce the difference between current Linux 2.6 (mainline) and the kernel in the Openmoko repository and thanks to this work we can run the most recent released version of Linux 2.6.
The sources of the Openmoko Linux kernel live in a GIT repository. With the WEB interface you can peek at the contents of the repository:
GIT is a fast version control system suited for the workflow that many kernel developers use. It is specially useful when you need to send patches for a project (who might in turn might need to send them upstream). This is an over-simplification but it gives you the idea in case you did not know.
GIT might seem complicated at first but once you learn to use it you will find many ways to increase your productivity by using it. For completeness in this page we include the GIT commands that you need in order to build a working kernel.
If you are very new to GIT you might want to read the good manuals that already available.
If you would like to contribute code we also have a page with Hints_on_using_GIT_and_stgit where we all hope to share some cool tips and tricks that can help you. You do not need to learn stgit in order to send patches to the Kernel Mailing List but we have to tell you that once you know git, stgit will make you more productive when you need to send a few patch at once (patchsets).
GIT allow developers to use different [[branches that help speed up development (and even make it possible). You might have noticed we have a few branches if already you visited the WEB interface (http://git.openmoko.org/?p=kernel.git;a=summary).
The andy-tracking branch is the one where most of the action takes place these days.
We have branch policies that explain what each branch is for.
Think of a robot that takes whatever kernels are the most recent in GIT, builds them for you and then makes them available here:
Another robot but this one only builds the versions picked by our friendly OpenEmbedded developers. Download from:
If you understand OpenEmbedded you will get this: Those versions are tied to a specific GIT revision through conf/distro/include/sane-srcrevs.bb.
Building the andy-tracking branch
Those are the minimum survival commands:
$ git clone git://git.openmoko.org/git/kernel.git linux-2.6 $ cd linux-2.6 $ git-checkout --track -b andy-tracking origin/andy-tracking $ mkdir GTA02 $ cp ./arch/arm/configs/gta02_moredrivers_defconfig GTA02/.config
Before building this kernel you need install a Toolchain.
$ ./build GTA02
Once the script finishes you will get two files. The first is uImage-GTA02.bin and a second file with a longer name but same contents, for instance uImage-moredrivers-GTA02_andy-tracking_c16287685cb59f91.bin. Please use the second file if you publish your kernel in some server or if you talk about it in public (specially in bugs reports) because it will allow others to know what kernel you were trying (in case you don't have local changes).
In order to build the modules you can:
$ ./build GTA02 dummy
This will create a file called modules-GTA02_andy-tracking-<git hash>.tar.gz. You need to untar this on the root directory of the FR.
If you want to update the local copy of the repository so that you get the latest changes, you can type:
Before reporting that the new kernel does not build please first check for changes in the configuration file provided by Openmoko.
kernel building tips
If you are modifying Linux kernel code and building it quite often you really want to be using ccache. It will save you a lot of time.
TODO: submit a patch for the build script that makes ccache use easier.
The development resources Openmoko offers are:
We appreciate your contributions. Check the Open Issues at the end of this page to check where we need more help.
If in doubt ask in the mailing list.
Why does Openmoko cares about sending code upstream instead of (insert your task here)?
There are two very different approaches and both of them would be doomed if we stuck all our resources to only one of to them.
The first approach is not to care about upstream kernel development efforts and stick to an old kernel while struggling to make it work, ignoring the fact that it is upstream where the people who want to help us improve, maintain and support the code running in our devices hang out.
The second is to care way too much about upstream to the point that we are not willing to ship a temporal dirty hack that make users happy and able to better use their phones. We cannot afford that kind of purity.
As many things in engineering we have to find a point in the middle that works well -- we will try hard to do it.
Who's Andy and why is he sticking his name in the kernel?
He takes some credit and most the blame. It is an usual practice that in kernel development some branches are named after the person who is taking care of them. He makes sure that the kernel still builds when Linus and his friends feel like it is time to update the upstream kernel and believe us: it is not as fun as it might sound and it happens often.
Check Kernel_branches if you care about the details.
Kernel developers are not polite! They do not even care to say "Hello" when they reply to my emails!
The long version is here: Kernel-developers-are-not-polite.
To the point:
All these opensource programmers are nicer in person (if you don't interrupt them while they are programming). On the internet they might appear to be very rude, but in person things are very different specially over lunch or when sharing a beer.
They just tend to write very short text because they have to read and write a lot every day.
Unfortunately we had to update many sysfs paths (see GTA02_sysfs) and since we did it the kernel stopped working properly with some distributions. Unless the distribution is abandoned it will likely catch up with the newest kernel soon.
Please read this report if you wish to know what the current issues are.
If you can help us with one of those issues it would be a great way to help us move forward. If in doubt please write to the Openmoko Kernel Mailing List. Let us link some bugs here without overdoing it because trac is better than a normal wiki for this. If we have more than 10 bugs the following lists then we might be doing it wrong.
Those are the bugs that active kernel developers believe can be fixed by kernel programmers that might want to join us. Thus they are leaving them unfixed for some reasonable time while they work on the harder bugs.
TODO: list of bugs linking to trac.
Those are the bugs that we have not fixed because they might be hard and/or because we have not found the time to fix them. They might end up being Esasy Bugs or Evil bugs. We will use trac for them. Please do not add a list of bugs here.
Read this report to find out more about them.
Those are the evil bugs that we haven't fixed either because:
- We do not know how to it in reasonable time
- Hardware vendor doesn't want to release documentation (some of them do that unfortunately / perhaps breaking promises they made to Openmoko about making things easier for developers)
- More testing is needed (perhaps a hard-to reproduce bug)
Ok, here is the list:
English • العربية • Български • Česky • Dansk • Deutsch • Esperanto • Eesti • Español • فارسی • Suomi • Français • עברית • Magyar • Italiano • 한국어 • Nederlands • Norsk (bokmål) • Polski • Português • Română • Русский • Svenska • Slovenčina • Українська • 中文(中国大陆) • 中文(台灣) • Euskara • Català