Help New Kernel For Pdaxrom

[louigi600]

PdaXrom kernel has remained pretty much the same since beta4 (2.6.16) and now over
at kernel.org  version 2.6.21.1 stable is avalible ... and that means that we are about 1
year behind current kernel developement.
Also over at OZ the have fixed quite a few things from which we could also benefit.

Can anyone help me retreive the patch sequence for the OZ kernel ?
... this will help me merge pdaXrom specific patches with all the stuff that OZ already
have fixed.

[Civil]

http://projects.gentoo.ru/gentoo-pda/wiki/...%9A%D0%9F%D0%9A for example. Or look for scripts at http://www.openembedded.org/filebrowser/or...packages/linux/ (  linux-rp_2.6.20.bb +  linux-rp.inc )

[Capn_Fish]

If you get this built and working, please post the steps involved for building and installing it. I'd like to to build it for my C3100 for the DM9601 driver.

Thanks, and best of luck!

[InSearchOf]

If you get this built and working, please post the steps involved for building and installing it. I'd like to to build it for my C3100 for the DM9601 driver.

Thanks, and best of luck!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160071\"][{POST_SNAPBACK}][/a][/div]

I have been lookin at upgrading the kernel to the newest for the past few months and I haven't had enough time to focus on pdaXrom to get that implemented...

I'm going to try to find time to get back in to it... but it is time allowing..

Late

[Civil]

If you get this built and working, please post the steps involved for building and installing it. I'd like to to build it for my C3100 for the DM9601 driver.

Thanks, and best of luck!

It is easy to do with gentoo. Just use ebuild from gentoo-pda overlay
If you don't you must apply folowing patches (in this order):

Code: [Select]

#!/bin/bash

DOSRC = "http://www.do13.de/openzaurus/patches"
RPSRC = "http://www.rpsys.net/openzaurus/patches/archive"
JLSRC = "http://www.cs.wisc.edu/~lenz/zaurus/files"
BASRC = "http://www.orca.cx/zaurus/patches"
CHSRC = "http://oz.drigon.com/patches"
TKSRC = "http://www.informatik.hu-berlin.de/~tkunze/zaurus/patches"

SRC_URI = "http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.20.tar.bz2 \
           http://www.kernel.org/pub/linux/kernel/v2.6/patch-2.6.20.6.bz2 \
           http://opensource.wolfsonmicro.com/~lg/asoc/asoc-v0.13.3.patch \
           ${RPSRC}/oprofile_always_bt_arm-r0.patch \
           ${RPSRC}/lzo_kernel-r0.patch \
           ${RPSRC}/lzo_jffs2-r0.patch \
           ${RPSRC}/lzo_crypto-r0a.patch \
           ${RPSRC}/lzo_jffs2_lzomode-r0.patch \
           ${RPSRC}/lzo_jffs2_sysfs-r0.patch \
           ${RPSRC}/hx2750_base-r28.patch \
           ${RPSRC}/hx2750_bl-r8.patch \
           ${RPSRC}/hx2750_pcmcia-r2.patch \
           ${RPSRC}/pxa_keys-r7.patch \
           ${RPSRC}/tsc2101-r16.patch \
           ${RPSRC}/hx2750_test1-r6.patch \
           ${RPSRC}/pxa_timerfix-r0.patch \
           ${RPSRC}/input_power-r6.patch \
           ${RPSRC}/pxa25x_cpufreq-r2.patch \
           ${RPSRC}/sharpsl_pm_fixes1-r0.patch \
           ${RPSRC}/pm_changes-r1.patch \
           ${RPSRC}/usb_add_epalloc-r3.patch \
           ${RPSRC}/usb_pxa27x_udc-r3.patch \
           ${RPSRC}/kexec-arm-r4a.patch \
           ${RPSRC}/locomo_kbd_tweak-r1.patch \
           ${RPSRC}/poodle_pm-r3.patch \
           ${RPSRC}/pxa27x_overlay-r5.patch \
           ${RPSRC}/w100_extaccel-r0.patch \
           ${RPSRC}/w100_extmem-r0.patch \
           file://hostap-monitor-mode.patch \
           file://serial-add-support-for-non-standard-xtals-to-16c950-driver.patch \
           ${RPSRC}/logo_oh-r0.patch.bz2 \
           ${RPSRC}/logo_oz-r2.patch.bz2 \
           ${RPSRC}/pxa-linking-bug.patch \
           ${RPSRC}/mmcsd_large_cards-r0.patch \
           ${RPSRC}/mmcsd_no_scr_check-r0.patch \
           ${RPSRC}/integrator_rgb-r1.patch \
           ${RPSRC}/pxa_cf_initorder_hack-r1.patch \
           file://pxa-serial-hack.patch \
           file://connectplus-remove-ide-HACK.patch \
           file://squashfs3.0-2.6.15.patch;status=external \
           file://vesafb-tng-1.0-rc2-2.6.20-rc2.patch;status=external \
           file://sharpsl-rc-r1.patch \
           file://defconfig-c7x0 \
           file://defconfig-hx2000 \
           file://defconfig-collie \
           file://defconfig-poodle \
           file://defconfig-akita \
           file://defconfig-spitz \
           file://defconfig-qemuarm \
           file://defconfig-qemux86 \
           file://defconfig-tosa "
wget ${SRC_URI}
http://www.openembedded.org/repo/org.opene...defconfig-spitz - config for spitz/borzoi/terrier (you just need to enable jffs support and change cmdline to boot from mtdblock)

[Civil]

In fact the only thing you need to build OZ kernel 2.6.20 is http://www.openembedded.org/repo/org.opene...ux/linux-rp.inc and http://www.openembedded.org/repo/org.opene...ux-rp_2.6.20.bb
This is sh-scripts that will download most files (except of 2 or 3 you need to download manualy) and patch the kernel.

[Capn_Fish]

If you get this built and working, please post the steps involved for building and installing it. I'd like to to build it for my C3100 for the DM9601 driver.

Thanks, and best of luck!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160071\"][{POST_SNAPBACK}][/a][/div]

I have been lookin at upgrading the kernel to the newest for the past few months and I haven't had enough time to focus on pdaXrom to get that implemented...

I'm going to try to find time to get back in to it... but it is time allowing..

Late
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160076\"][{POST_SNAPBACK}][/a][/div]

If there's anything I can do to help push this along, let me know.

[louigi600]

http://projects.gentoo.ru/gentoo-pda/wiki/...%9A%D0%9F%D0%9A for example. Or look for scripts at http://www.openembedded.org/filebrowser/or...packages/linux/ (  linux-rp_2.6.20.bb +  linux-rp.inc )
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160056\"][{POST_SNAPBACK}][/a][/div]

Thanks Civil ... those are very good starting pointers.

Capn_Fish of caurse I'll share anything good that might come out of this.

InSearchOf yea but maybe you can help me anyway ... it will cost less time and if I get anywhere then I can tell you what I did.

Unfortunately today I'm working on mt external battery charger ... but I'll get pack to this tomorrow.

[Civil]

I have been lookin at upgrading the kernel to the newest for the past few months and I haven't had enough time to focus on pdaXrom to get that implemented...

I think the only problem is updating pdaXrom-specific patches (if they exists). Most of other work has been done by OZ (look at http://www.openembedded.org/filebrowser/or...packages/linux/ - there you can find sh-scripts for building kernel - it won't take much time to make your own)

[xjqian]

does it make sense to incorporate pdaxrom as a distro into the openembbed build environment?

I'm sure it's possible and would benefit both sides but not sure how much political issues, if any, it will arouse.

[koen]

does it make sense to incorporate pdaxrom as a distro into the openembbed build environment?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160096\"][{POST_SNAPBACK}][/a][/div]

Summary: We (OE + OZ) offered that long ago, but pdaX wasn't interested.

[ZDevil]

does it make sense to incorporate pdaxrom as a distro into the openembbed build environment?

I'm sure it's possible and would benefit both sides but not sure how much political issues, if any, it will arouse.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160096\"][{POST_SNAPBACK}][/a][/div]

One thing I am pretty sure about is that at the end of the day using which distro or "rom" simply doesn't matter, let alone any ego war. What he wants is simply a usable and stable working environment, and no mere hacker's dream toy.

[Capn_Fish]

I don't really get the whole OE thing. What benefits would there be to switching to OE?

[Meanie]

I don't really get the whole OE thing. What benefits would there be to switching to OE?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160116\"][{POST_SNAPBACK}][/a][/div]

In the past, when most OZ users were using OPIE rather than GPE and everything was based around 2.4 kernels, there was a big difference between OZ and pdaXrom. Now, that everyone is moving to a 2.6 kernel and EABI, there isn't so much of a difference anymore. OE is the builder tool to build OZ/Angstrom similar to the pdaXrom builder. The advantages of the pdaXrom builder was that it could spit out a X86 as well as a ARM version of pdaXrom. The X86 version could be booted off a CDROM or used from inside VMWare or other virtual machines. In addition, pdaXrom builder also build a ready to use native zgcc image for the Zaurus. These and the fact that pdaXrom was still based around 2.4 kernel which was although slower than the 2.6 kernel, much more stable and supported all the Zaurus' (clamshell models) hardware, and glibc 2.2 which made it easy to port to Sharp/Cacko, ie pdaXqtrom.
Now, there isn't much of a differentiator anymore. Everything is aiming at using 2.6 kernel, the use of EABI means that the latest glibc and gcc will be used. The only difference will be the packaging and even in that, both distros are becoming more and more similar in that regard. One difference that remains is the ipk format, but that isn't a big issue.
CJK was one of the reason pdaXrom was more popular for some people, but it isn't really supported well in the latest of either distros. Application wise, OZ/Angstrom tends to only provide optimised applications that run quickly and use little resources, whereas pdaXrom enphazised on supporting almost any opensource linux application that users wanted to use on their Zaurus.
So to answer the question, the difference would be much smaller these days, but the effort to convert everything to using OE would be quite considered and what gain would that provide? It isn't like pdaXrom doesn't have a build tool yet or its current tool doesn't do the job properly, so there isn't really a point in moving to OE.

[adf]

hmmmm. what in particular prevents one from grabbin pdax source and putting it all in OE, or putting all of Angstrom through the pdaX builder? Other tha the simple pain of rounding up the sources in a useable fashion, that is.  It seems to me that if they are getting that close, and it has seemed that we are looking at pretty much the same kernel for 2.6, then it would simply be a matter of time and ambition yes? no?