OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> Simpad Kernel Source Needed, 2.4.25-vrs2
scholbert
post Nov 21 2005, 02:04 PM
Post #1





Group: Members
Posts: 48
Joined: 21-November 05
Member No.: 8,576



Hello,

i'm new to this forum and i'm not a hardcore programmer.
The simpad i own has been reanimated many times.

Respect to guylhem and the other guys who already made a lot of mods to the simpad.

At the moment i try to play around with linux drivers for my simpad.
I'd like to use the 2.4.25-vrs2-pxa1-jpm1 kernel for these purpose.
As far as i know Mickeyl has used this kernel for his 0.9.0-rc1 opie distri (great job!)

Unfortunately i was not able to get a working zImage from 2.4.25-simpad kernel you can find at externe.net.
I used the good old 2.95.3 gcc for that.
Even compiled with gcc 3.3.2 from handhelds it was not possible to boot my simpad.

I also tried to patch the original 2.4.25 and failed because of missing patches.

I'd like to use the 2.95.3 gcc to compile all that stuff.
Could anyone give me a hint how to go on?

Thanks a lot!!!!!
scholbert
Go to the top of the page
 
+Quote Post
fredyd
post Nov 22 2005, 01:46 AM
Post #2





Group: Members
Posts: 38
Joined: 4-April 05
Member No.: 6,787



Dear scholbert,
You should pull out openembedded <http://oe.handhelds.org/>.
It contains the latest kernel versions for the simpad (both 2.4 and 2.6), and will build the appropriate cross-compilers for you.

Fred
Go to the top of the page
 
+Quote Post
scholbert
post Nov 22 2005, 07:05 AM
Post #3





Group: Members
Posts: 48
Joined: 21-November 05
Member No.: 8,576



Hi Fred,

thanks for your advice.
The openembedded environment maybe the best tool to build quite everything,
but it is a full-blown development system too.
Also you need a lot of disk space and computing power.

I'd like to use only a simple cross-toolchain and the kernel sources for my experiments. The other thing is i'd like to carry it around on a memory stick and/or use it inside colinux distribution.

I think it would be complicate to integrate openembedded into colinux, wouldn't it?

So, is there any possibility to get the 2.4.25-vrs2-pxa1-jpm1 as a tarball or at least working patches to modify the original kernel sources?

Otherwise i'd have to buy new hardware and go openembedded.

Thanks a lot so far.

Greets,

scholbert
Go to the top of the page
 
+Quote Post
lardman
post Nov 22 2005, 07:14 AM
Post #4





Group: Members
Posts: 4,515
Joined: 25-October 03
From: Bath, UK
Member No.: 464



Download the OE meta data and you can look at the appropriate .bb file to find the urls of the source & pathces and the order in which to apply the patches.


Si
Go to the top of the page
 
+Quote Post
fredyd
post Nov 23 2005, 01:35 AM
Post #5





Group: Members
Posts: 38
Joined: 4-April 05
Member No.: 6,787



Hi, I put an archive with all the
opensimpad kernel patches on my site.
Please take a look at the .bb files to check in which order to apply the patches. You'll also need to download openswan.
If you intend to contribute patches, you should save a copy of the sources with the patches applied but without your modifications, in order to send me a diff afterwards.

You can try the toolchains at ftp://ftp.arm.linux.org.uk/pub/armlinux/toolchain/ but the one built in OE may include more fixes...

Fred
Go to the top of the page
 
+Quote Post
scholbert
post Nov 23 2005, 03:55 AM
Post #6





Group: Members
Posts: 48
Joined: 21-November 05
Member No.: 8,576



Hi again,

thanks to lardman for the good advice.
I picked the OE snapshot, extracted the patches with monotone and applied them to kernel.org's standard kernel.

No problem so far, but i have to test the new kernel intensely on my hardware.

Special thanks to fredyd!!
I think there will be a lot of gadget fans around who will find this very useful.

The toolchain from handhelds.org works fine. I put it also in my colinux a few weeks ago. No problem at all.
Depending on the image you use, you might have to upgrade native libc.

I will post my further experiences to this forum if they are useful for the community.

Thanks again,

scholbert
Go to the top of the page
 
+Quote Post
Martin
post Jan 12 2007, 11:05 AM
Post #7





Group: Members
Posts: 138
Joined: 5-October 04
From: konstanz, germany
Member No.: 4,874



Hi :-)

I want to use my serial keyboard with my Simpad ... I found a nice, small howto here ... but have problems with making a new kernel ...

same procedure with crosscompile on my laptop :-( getting to work and not to destroy my other compiling environment ... using gcc 4.x

anybody able to give me some more hint on doing that ... or maybe do it for me ... creating new kernel zimage with newton keyboard patch ?

THX
Martin
Go to the top of the page
 
+Quote Post
scholbert
post Jan 20 2007, 11:33 AM
Post #8





Group: Members
Posts: 48
Joined: 21-November 05
Member No.: 8,576



QUOTE(Martin @ Jan 12 2007, 08:05 PM)
Hi :-)

I want to use my serial keyboard with my Simpad ... I found a nice, small howto here ... but have problems with making a new kernel ...

same procedure with crosscompile on my laptop :-( getting to work and not to destroy my other compiling environment ... using gcc 4.x

anybody able to give me some more hint on doing that ... or maybe do it for me ... creating new kernel zimage with newton keyboard patch ?

THX
Martin
*


Hi Martin,

there's already a lot of information in this thread. If you use a precompiled toolchain, as mentioned, it is very simple and i don't think you'll harm your distri. Let me point out what i did:

The OE toolchains i used are static and compiled for /usr/local.
If you don't want to use the OE environment (which is very comfortable), grab a snapshot from their toolchain, as i did biggrin.gif .

If you want to avoid any trouble at all with your existing gcc 4.x rename the /usr/local directory to, for example /usr/local_disable and create a new /usr/local directory with the OE toolchain in it. This should be O.K. for kernel and module compilation.

Then you might set the PATH variable to the OE toolchain temporarily in your console window. Get the kernel, apply the patches and compile. It's done.
Afterwards you might tar the OE toolchain and put it where ever you like.

Don't forget to rename your original /usr/local again, so all PATH settings will point at your 4.x toolchain again.

Of course there are a million other and more elegant ways, but this is very simple and without any effects to the host, i suppose. Finally it works for me.
At least the version of your host toolchain should work together with the cross toolchain, for make menuconfig etc.

What is the kernel & gcc version you intend to use?

Regards,

scholbert
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 31st October 2014 - 10:09 PM