OESF Portables Forum

Everything Else => General Support and Discussion => Zaurus General Forums => Archived Forums => Software => Topic started by: Joshp on March 15, 2004, 05:46:21 pm

Title: Zaurus kernel.
Post by: Joshp on March 15, 2004, 05:46:21 pm
OK, I want to start playing around with bulinding kernels for the zaurus.  I am assuming that al need a cross complier setup.  Where would find something that
I coulde get running under slackware 9.1.
Title: Zaurus kernel.
Post by: grey_moon on March 15, 2004, 05:48:46 pm
I think ceds howto is the best starting place
http://www.zaurususergroup.com/modules.php...0%28by%20Ced%29 (http://www.zaurususergroup.com/modules.php?op=modload&name=phpWiki&file=index&pagename=Special%20Kernel%20%28by%20Ced%29)
Title: Zaurus kernel.
Post by: Joshp on March 15, 2004, 06:19:09 pm
I found the howto but now where do i download the sl-5500 kernel source.
Title: Zaurus kernel.
Post by: tumnus on March 15, 2004, 08:27:36 pm
https://www.oesf.org/commu...html?group_id=5 (https://www.oesf.org/community/66.180.235.230/project/showfiles8068.html?group_id=5)
Title: Zaurus kernel.
Post by: psmith on March 16, 2004, 12:26:23 pm
i would like to have the iptables and wireless extension enabled for sharp 2.38 or 3.13, if I cross compile the kernel and modules, mix them with sharp rom, and flash the rom, will it work?
Title: Zaurus kernel.
Post by: Joshp on March 16, 2004, 12:40:11 pm
If you cross complie Sharps kernel it should work.  Just make sure that you use the right kernel version.  I think the 2.38 rom is 2.4.6 and 3.13  rom is 2.4.18.  You will also need to backup your sd card module as there is no source for it.
And on a side note am no kernel expert am just going on what have read and seen with my Z, and what I have done with differnt kernels on my computers.
Good luck.

P.S. There is a ipk for iptables both for the bin and for the modules.

JP
Title: Zaurus kernel.
Post by: Joshp on March 17, 2004, 04:24:28 pm
Ok I have cross complieing working but every time I go to complie the kernel I get:

/bin/sh: line 1: scripts/mkdep: cannot execute binary file.  

I think I know what couse this but I don\'t know how to fix it.  I think what happens is that mkdep.c gets compiled as an arm program.  As well as ever other *.c unde the scripts dir.  Any ideas.  
Thinks

JP.
Title: Zaurus kernel.
Post by: lardman on March 18, 2004, 07:22:42 am
Delete the (arm) binary, copy the command across into a clean terminal window (without anything sourced for the cross-compiler), create the binary, run make again.

However there must be other ways (for example in OE I don\'t have to do this), so it\'s probably possible to set native_gcc and cross_gcc or something similar and it will sort itself out.

Si