[Angstrom-devel] Patching and development question to fix bug 4259, pxa2xx_udc in angstrom release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Good morning all, I used to use openzaurus before OE came along. In fact I used to maintain a build for the SL-5600 (poodle?) until it broke. It is so nice to see how professional the project now is compared to when the tools were all shell scripts with hardcoded bin locations! Awesome work. Anyhow someone at work has given me a Zaurus c860 (c7x0). Playing around with angstrom for a bit has highlighted a few things: Firstly the udc clock bug, which is now fixed in kernel 2.6.25 (Bug 4259), and a problem with WPA (bug 4180). I would like to tackle both to push the fixes into the standard distro. FYI I have read the wiki which details policy, but these questions apply to advice on where to start my patching work. I have currently got a building copy of angstrom (it is sooo much easier now guys, thanks so much!) Taking 4259 (pxa2xx_udc) This is fixed in 2.6.25 but I am guessing you won't want to bump the kernel version for this. If I backport the patch (might be easy, maybe not) would that be the best approach? Should I checkout a specific version of the build tree to patch against, and if so what. I haven't thought about how to fix the arc4 issue, apparently you can get some success in building the crypto modules into the kernel. This is a significant change, I don't know how much they will enlarge the kernel by. I guess this is one for discussion. Looking forward to playing with Zauruses (Zauri?) again, - -- Dr Matthew Swabey Rm3229, Bldg59 Zepler School of ECS University of Southampton University Road Southampton, SO17 1BJ England Tel: 02380 597381 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFIKtB6soSsB2Ynk1ARAjhmAJ9yQ/dfZuPjbcs3+HOJQxUlleA8zACffjUs 4xv9j1AdkDmU0DOsazidl8U= =tpcg -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Patching and development question to fix bug 4259, pxa2xx_udc in angstrom release
Matthew Swabey wrote: Anyhow someone at work has given me a Zaurus c860 (c7x0). Playing around with angstrom for a bit has highlighted a few things: Firstly the udc clock bug, which is now fixed in kernel 2.6.25 (Bug 4259), and a problem with WPA (bug 4180). I would like to tackle both to push the fixes into the standard distro. FYI I have read the wiki which details policy, but these questions apply to advice on where to start my patching work. I have currently got a building copy of angstrom (it is sooo much easier now guys, thanks so much!) Taking 4259 (pxa2xx_udc) This is fixed in 2.6.25 but I am guessing you won't want to bump the kernel version for this. If I backport the patch (might be easy, maybe not) would that be the best approach? I don't have a strong opinion on either option, but I would like at least 2 test reports from users of the chosen option (backport or 2.6.25). 2.6.24 was said to fix loads of stuff and turned out to be broken. regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Patching and development question to fix bug 4259, pxa2xx_udc in angstrom release
Andrea Adami wrote: Anyhow someone at work has given me a Zaurus c860 (c7x0). Playing around with angstrom for a bit has highlighted a few things: Nice to see a new c7x0 candidate for mantainer! +1 for me (he he, I'm just too busy atm, can only help for some testing) I don't have a strong opinion on either option, but I would like at least 2 test reports from users of the chosen option (backport or 2.6.25). 2.6.24 was said to fix loads of stuff and turned out to be broken. regards, Koen +1 from me to jump on 2.6.25 wagon +1 from me. vanilla pxa2xx_udc and RP pxa27x_udc look different. If 2.6.25 UDC works on PXA27x, there is nothing to do. If not, we should compare them. There are many new features in 2.6.25 (UDC, new wireless stack,...). Porting RP patches to 2.6.25 would be more productive than backporting new features to 2.6.24. Let's start with 2.6.25-rp as clone of 2.6.24-rp and comment out all failing patches with REBASE or DROP note. Then authors of patches will debug and fix it. The underlying problem was linux-rp-2.6.23 in .dev had big issues with suspend/resume. I personally suggested the move to 2.6.24, being desesperated by the *not resuming* device (SL-C860). Moreover Stanislav was working on Sharp remote control and the patches were only for 2.6.24. One line reject fix for 2.6.23 or 2.6.25. Porting to 2.6.26 would require some work (GPIO code changes). I have no confirmation, that it works on akita or c7x0. Especially on C7x0 + CE-RH1, the driver is only my guess. Anyway the 2.6.24 still needs some finishing: If you look at the bottom of the linux-rp-2.6.24.bb you'll see there are no mtd-module.patch for c7x0 but only for akita. Why? mtd-module.patch fixes MTD mapping of PROM, when compiled as module. I added it for machines, which were actually affected. Very minor issue, unless you want to use EN-JP dictionary database in PROM. Fixed in 2.6.25. -- Stanislav Brabec http://www.penguin.cz/~utx/zaurus ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] pxa2xx_udc on the c7x0's... (and maybe others) backported from 2.6.25
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ... and I have touched off a whole discussion :). anyway I have the patch, which seems nice and clean (lightly touches pxa2xx_udc.h and a bit more in pxa2xx_udc.c). I have it running now and am catting /dev/zero across to /dev/null. I am going to leave it running overnight. If it is still working then I shall call it a success. Oh and the error has disappeared from dmesg. Onto the other problem I am happy to begin trying to get 2.5.25 online, but would like to push this patch into the current release (and the WPA fix) for everyone else. Advice on how to do it? - -- Dr Matthew Swabey Rm3229, Bldg59 Zepler School of ECS University of Southampton University Road Southampton, SO17 1BJ England Tel: 02380 597381 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFIKxdwsoSsB2Ynk1ARAok9AKDCBwuqZ5Inv9TShISzuQURvyBR3gCgmL6L 0BTfh8dg8vZ4KBMgfcQEXc4= =Et/x -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] oe.dev deleted gpsdrive-2.10-pre4
Hallo. I have been searching for the latest gpsdrive in oe.dev. It seems, that it disappeared in your (xora) merge from 2008-03-20T06:23:52. Was it intention or a mistake of the merge? Thanks for your info. -- Stanislav Brabec http://www.penguin.cz/~utx ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] oe.dev deleted gpsdrive-2.10-pre4
On 05/14/2008 06:09 PM, Stanislav Brabec wrote: Hallo. I have been searching for the latest gpsdrive in oe.dev. It seems, that it disappeared in your (xora) merge from 2008-03-20T06:23:52. Was it intention or a mistake of the merge? Thanks for your info. I've noticed that too. It got lost together with some other recipies after the recent merge conflict. As I'm away for a while, I'm learning what's changed during the period. I plan to restore all those lost recipies tonight. Regards Gordon ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
