Dual Booting Pdaxrom And Angstrom?

[Meanie]

I had a go at making Angstrom boot of the mmc (like I do for my modded r121) but it was a no go.
I think that there is 2 problems involved:
angstrom kernel seems to have ither no support for ext2/3 (or at least only in modules),
angstrom kernel is ignoring command line parameters passed by u-boot (may need a u-boot patch).

To check out these things one would need the Angstrom kernel sources ... currently I cannot putup the OE build environment to get the sources for me and I've not been able to figure out how to make a Angstrom kernel by starting from a vanilla one.
Is someone could supply ... I'd have a look into it.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=164840\"][{POST_SNAPBACK}][/a][/div]

angstrom kernel supports ext2/ext3 but the command line parameters from uboot are ignored because those values are hardcoded in the kernel...

[louigi600]

angstrom kernel supports ext2/ext3 but the command line parameters from uboot are ignored because those values are hardcoded in the kernel...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=164843\"][{POST_SNAPBACK}][/a][/div]

While running on Angstrom kernel (r197 root) I could not mount the Angstrom ext2/3 root on SD. Since the modules were not on the r197 root for that kernel I guess some module is involved ... whether it be ext2/3 or some mmc driver module.

Yea I suspected that Angstrom kernel could have something hard coded ... that's why I want to fiddle with the config and sources (maybe I can apply nandparts.patch and pdaxrom_u-boot_params.patch patches).

[Civil]

well... It would probably be useful to merge angstrom patches to the pdaxrom kernel. EABI seems like a good idea. Further it would seem like a good idea to have a unified kernel. pas that, maybe a re-compile-fest to bring older apps with compatiblity problems up to speed?

https://www.oesf.org/forums/index.php?showtopic=23865&st=75

There was a request to bring glibc 2.4/2.5, gcc 4.1.x and eabi support to pdaXrom (see bugtracker at pdaxrom.org ).
pdaXrom now have very old glibc and gcc (gcc 3.4.x doesn't support EABI properly, and glibc 2.5 have a lot of fixes for eabi support)

not been able to figure out how to make a Angstrom kernel by starting from a vanilla one.

http://www.openembedded.org/filebrowser/or...packages/linux/ - see linux-rp there.

[louigi600]

Well appart any extra patchs that may have gotten into Angstrom kernel (they have some on ther source tree that I've not figured our wether they are old or used) then the build I have for 2.6.21.5 could be good for bothe Angstrom and pdaXrom with two extra requirement:
1) enable the EABI target and also the old ABI compatibility
2) an EABI toolcain to build it

Currently I'm using pdaxrom 3.4 cross toolchain and that is not really EABI capable.

Some time ago I attempted building kernel with the EABI toolchain from code sourcery ... bit it fails on some missing headers if I remember correctly.
If anyone has the time to fix it up ;-) ... I'm buisy reading a lot of pxa documentation.

Someone may say: "Why don't you use OE toolchain ? ... it's EABI capable"

I'll probabbly give it a go when I'll have a pc at home to set it up on.

[louigi600]

Using the current EABI cross toolchain from Code Sourcery (arm-2007q1-21-arm-none-eabi-i686-pc-linux-gnu.tar.bz2) it is possible to build the kernel I patched with mixed pdaXrom and OE patches (see the Help New Kernel For Pdaxrom thread).