Zire 72 and 2.6.25rc3, request for comments
Hi, all!
I report that during some weeks I was testing PXA architecture on recent bleeding edge kernels
and find it quite working. Among things which we need for palms functionality, missing parts are:
WM97xx touchscreen support. Sound works ok.
Some pxafb weirdness (possible to work around).
Some unique hardware device drivers.
Some of these things are available as patches and are pushed to kernel,
while they are probably will not get there in this version. For now we could
depend on extarnal patches (but we should mark them this way).
So it is good opportunity to not miss a train and start using current Linus git as
base for palms for newer development (leaving our current tree for
maintenance/bug fixing/old and badly maintained devices).
Any suggestions?
I see several pros here:
1. Easier integration with Vanilla (little to no work there).
2. Possibility to publish to LAKML and subsystems (even if not integrated, this gives
visibility to a project and developers personally). Visibility in this
world might mean better paid jobs for developers who have their trace in kernel
and kernel mail list, which should stimulate them for farther development.
3. Less dependency on certain lazy developers (and less hypocritical excuses
about who responsible for what).
We have lots of code collected over time and it requires hard work to update it.
Devices die, people lose interest, and we have some code rotten beyond usability.
We have some weird code snippets nobody have any idea about.
People, lets work on improvement!

Sound's interesting, but
Sound's interesting, but from the title I guess you speak about 2.4.X kernel, what about 2.6.X? 2.4.X is more suitable for us? 2.6.X misses a lot of necessary things?
Sorry for a typo. of course,
Sorry for a typo.
of course, bleeding edge is 2.6.x
Now it sounds even more
Now it sounds even more interesting, did you managed to build current kernel for your zire? I'm certainly interested. If you start new repo and if you have working zire72 patch, I'll try to add TX and T|T5.
This is mostly request for
This is mostly request for volunteers. I basically made kernel start with display without much patching.
I used standard wm97xx patch from LAKML. I just tested basic touchscreen and framebuffer.
I did not tested any specific features, and power management.
Well, I'm one lazy and busy
Well, I'm one lazy and busy volunteer who likes this idea and wants to participate....
Applause So we have
Applause
So we have volunteer.
I'm busy volunteer, but lets
I'm busy volunteer, but lets try...
I'd love to help somehow,
I'd love to help somehow, but my knowledge on both C and Linux is far away from what you guys need..but if I could do something, just ask!
Go for it slapin!
So we've got some
So we've got some volunteers. Now question is what should we do? I noticed that there is something like vanilla git in git.hackndev.com/srv/git/linux-2.6 Should we start commiting there support for our devices? Any general idea what should be done and how? Well, maybe this can go to bugzilla, but it seems that our bugzilla is still down :-( So what are our plans, slapin?
Here's a suggestion on how
Here's a suggestion on how to get started, while waiting for slapin's thoughts:
I created a branch ato-palmtc-wip for my work in progress palmtc/vanilla stuff there. I suggest others create their own branches for their hacking to get things working with vanilla. Then when a driver is working, tested and cleaned up it can move into a stable branch with proper Signed-off-by and whatnot in preparation for pushing to LAKML. You can make a mess debugging in a wip branch but the stable must be clean as possible, with no unnecessary patches.
Without any external patches I have successfully tested touchscreen, SD/MMC and wifi on T|C with latest vanilla so far (it uses UCB1400 which nicely is already merged in vanilla, not WM9712 like the other palms). The existing keyboard driver needs to be cleaned up and isn't working properly for me (only the "f" key responds for some reason). I've a theory on how to resume from sleep without reflash (after some tracing with qemu) but it's going to necessarily be pretty ugly. Marex bricked the T|C he was working on when trying to write an mtd driver, so I'm bit scared to try that.
By the way, quick git howto
By the way, quick git howto if you're struggling with it. This is just how I understand it, may not be best practice. ;-)
Get a copy of the tree:
git clone git+ssh://git.hackndev.com/srv/git/linux-2.6If you have some other vanilla git based tree lying around you can greatly speed up cloning with:
git clone --reference /path/to/some/other/git/tree/.git git+ssh://git.hackndev.com/srv/git/linux-2.6Then make a new branch to work in (don't forget to do this!). You can specify a particular version to work off if you like.
git checkout -b myname-palmxx-wip v2.6.25-rc5You could make a branch for working on a particular feature too:
git checkout -b myname-palmxx-wip-wifi myname-palmxx-wipAnd later merge it into your plain wip branch.
git checkout myname-palmxx-wipgit merge myname-palmxx-wip-wifi
Hack away commit etc.
git diffgit add some_new_file.c
git commit -a -m"Did some stuff"
git log
When you want to publish your changes (git push repo src-branch:dest-branch):
git fetch origin # makes sure you're up to dategit push origin myname-palmxx-wip:myname-palmxx-wip
I've been trying to get
I've been trying to get PalmTX working with vanilla lately, bud I had some problems, so I decided to start with something small and partially working. So I created miska-palmtx-wip branch and committed there some basic code for TX. It can use some cleanups and it misses a lot of functionality, but we can do that later. But this kernel can boot TX and framebuffer works - it's just the beginning ;-)
should I start a cron job
should I start a cron job for updating our vanilla clone?
I think, it can be usefull.
I think, it can be usefull. slapin said that wm97xx is in vanilla git now, so we should update it anyway...
In our vanilla git, master
In our vanilla git, master branch is still 2.6.25-rc8 but there are also tags for newer versions. How can I use them? Can somebody more skilled with git merge these newer tags into the master?