Help New Kernel For Pdaxrom

[louigi600]

Ok ... I manually checked every single entry in the menuconfig ... (copying the old .config from the 2.6.16 kernel does not work ... not sure why because I've used thid technique many times when upgrading kernel)

Anyway I also applied some pdaxrom specifig patches:
0218_linux-2.6.16-bootargs.patch.bz2 (for the u-boot boot parameters)
and part of
0200_linux-2.6.16-pxa27x-ovl.patch.bz2

I got as far as linking kernel again:
drivers/built-in.o: In function `tosaled_amber_set':
ledtrig-ide-disk.c:(.text+0x70d30): undefined reference to `tosascoop_jc_device'
drivers/built-in.o: In function `tosaled_green_set':
ledtrig-ide-disk.c:(.text+0x70d68): undefined reference to `tosascoop_jc_device'
make: *** [.tmp_vmlinux1] Error 1

Anyone have any ideas ?

[xjqian]

I got as far as linking kernel again:
drivers/built-in.o: In function `tosaled_amber_set':
ledtrig-ide-disk.c:(.text+0x70d30): undefined reference to `tosascoop_jc_device'
drivers/built-in.o: In function `tosaled_green_set':
ledtrig-ide-disk.c:(.text+0x70d68): undefined reference to `tosascoop_jc_device'
make: *** [.tmp_vmlinux1] Error 1
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

Those are specific to tosa (6000l). Tosaled_amber/green_set are probably the functions to control the led light behavior. You can certainly comment those out if you don't care about tosa support or take a look at [a href=\"http://www.do13.de/openzaurus/]http://www.do13.de/openzaurus/[/url]. Maybe you are missing some tosa specific patches.

[louigi600]

Those are specific to tosa (6000l). Tosaled_amber/green_set are probably the functions to control the led light behavior. You can certainly comment those out if you don't care about tosa support or take a look at http://www.do13.de/openzaurus/. Maybe you are missing some tosa specific patches.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160251\"][{POST_SNAPBACK}][/a][/div]

Yep I figured that out ... I accidentally enabled this feature:
"LED Support for the Sharp SL-6000 series"
I had it already removed when I rescanned the thread for updates ;-)

Now I have another error:

  MODPOST vmlinux
  OBJCOPY arch/arm/boot/Image
  Kernel: arch/arm/boot/Image is ready
  AS      arch/arm/boot/compressed/head.o
  GZIP    arch/arm/boot/compressed/piggy.gz
  AS      arch/arm/boot/compressed/piggy.o
  CC      arch/arm/boot/compressed/misc.o
  AS      arch/arm/boot/compressed/head-xscale.o
  AS      arch/arm/boot/compressed/head-sharpsl.o
  LD      arch/arm/boot/compressed/vmlinux
  OBJCOPY arch/arm/boot/zImage
  Kernel: arch/arm/boot/zImage is ready
  Building modules, stage 2.
  MODPOST 249 modules
WARNING: drivers/usb/gadget/pxa2xx_udc.o - Section mismatch: reference to .init.text:pxa2xx_udc_probe from .data between '$d' (at offset 0x0) and 'memory'
WARNING: drivers/usb/gadget/pxa2xx_udc.o - Section mismatch: reference to .exit.text:pxa2xx_udc_remove from .data between '$d' (at offset 0x4) and 'memory'
WARNING: "wm8731_dai" [sound/soc/pxa/snd-soc-corgi.ko] undefined!
WARNING: "soc_codec_dev_wm8731" [sound/soc/pxa/snd-soc-corgi.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2

Any ieas ?

[louigi600]

Ok I removed anothe option for the corgi soc .... now it's building.
I'm attaching my config and the patche sequence I used.

BTW: my config should also fix iptables in pdaxrom current ;-)

[louigi600]

Ok I't boots but the kernel flash layout (whether detected or sculptured in code) is all wrong .... so do not try unless you want to corrupt data in the root .

I get the defaulr OZ layout with
root on /dev/mtd2
home on /dev/mtd3

In pdaxrom there should be on mtd3 at all and just the bog root: anyone know howto fix this ?

[louigi600]

Ok it's also necessary to patch manually 0215_linux-2.6.16-nandparts.patch.bz2 as it gets rejected. (it's easy ... very simple patch).

Now it's working ;-)

Thanks to everyone who contributed.

In any case there is other problems that arise with the new kernel:
in X I get a shatow of everithing in the menu bar,
there is some problems with the touch screen activating multiple clicks when only 1 click is actually done (especially in the window operation buttons),
after exiting from X the text console is even more fucked up.

[louigi600]

The work I've done so far seems to be working and my C760 is currently running with such a kernel but the /etc/rc.d/init.d/zaurushw thing broke.

it depends on these 2 pdaxrom specific patches:
0212_linux-2.6.16-pxafb-spitz.patch.bz2
linux-2.6.16-sharpsl-param.patch.bz2

Unfortunately the functions targeted by these patches have changed so much that my programming skills make it impossible for me to apply the patches manually.

Can anyone help me ?

[Civil]

I've managed to boot into kernel 2.6.21.1 (root on sd - rootfs is gentoo 2006.1 EABI ).
Just a few changes into existing patches... If anyone interested I can post updated versions of them.

[louigi600]

I've managed to boot into kernel 2.6.21.1 (root on sd - rootfs is gentoo 2006.1 EABI ).
Just a few changes into existing patches... If anyone interested I can post updated versions of them.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160485\"][{POST_SNAPBACK}][/a][/div]

Yes please do

[Civil]

Some patches for 2.6.21.1 kernel.

P.S. It's tar.bz2 archive in tar archive...
Most of patches are OZ's one. pxa27x_udc have only one modification - name of one header changed in 2.6.21 kernel. lzo_kernel - a little typo (misssing ";" ) and a patch for asoc - fixing kernel bug #8429 (a typo in kernel).
P.S. asoc 0.13.0 (a part for Zauruses) is no in mainline kernel. As kexec-patch is.

[louigi600]

Ok got it building and booting to with a plain cross toolchain from pdaxrom ... but apparently there is an issue with suspend in this version (2.6.21.1).

I'm working with Civil to see if we can fix it (his 3100 is also afflicted).

[Capn_Fish]

Does this mean there'll be a working 2.6.21 kernel for pdaX, with a DM9601 driver (can you tell I really want my USB-to-Ethernet adapter working?)?

[louigi600]

Does this mean there'll be a working 2.6.21 kernel for pdaX, with a DM9601 driver (can you tell I really want my USB-to-Ethernet adapter working?)?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160554\"][{POST_SNAPBACK}][/a][/div]

Well ... fully working kernel for pdaxrom will require some developer work to get all the things working for the distro.
Me and Civil are working to get the basics working ... hoping that the developers will benefit from our experiments.

Keep in mind that there is also issues with touchscreen behaviour so even if we get the basics working it still needs work done by developers to become usable in the distro.

[Capn_Fish]

Does this mean there'll be a working 2.6.21 kernel for pdaX, with a DM9601 driver (can you tell I really want my USB-to-Ethernet adapter working?)?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160554\"][{POST_SNAPBACK}][/a][/div]

Well ... fully working kernel for pdaxrom will require some developer work to get all the things working for the distro.
Me and Civil are working to get the basics working ... hoping that the developers will benefit from our experiments.

Keep in mind that there is also issues with touchscreen behaviour so even if we get the basics working it still needs work done by developers to become usable in the distro.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160555\"][{POST_SNAPBACK}][/a][/div]

I appreciate your efforts. Hope this leads to a 2.6.21 kernel being put into pdaX.

[louigi600]

Just a reminder ... this is where the 2.6.21 kernel (and 2.6.20.6) were left.

ASAP I'll see if 2.6.21.4 is any better ... but looking at the changelog I see no changes addressing the issues that were afflicting Z devices.

I'll try to find the time to see if there are any new patches ....
Also I must try to make my build script automatically download newest patches from ZO and apply them automatically to kernel sources .... the process is too manual to be repeated every time there is new patches avalible.