From: Marc <marvin24@gmx.de>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: patching arm-linux 2.4.18 on sharp zaurus sl-5500
Date: Fri, 27 Jan 2006 20:30:23 +0100 [thread overview]
Message-ID: <200601272030.24079.marvin24@gmx.de> (raw)
In-Reply-To: <20060127143832.GG3673@harddisk-recovery.com>
Le Friday 27 January 2006 15:38, vous avez écrit :
> On Fri, Jan 27, 2006 at 09:28:07AM -0500, Lorne J. Leitman wrote:
> > We are a group of researchers at University of Pittbsurgh trying to
> > implement an ad-hoc routing protocol on the Sharp Zaurus 5500 pda. Our
> > network is running the following environment:
> > -arm-linux kernel 2.4.18-pxa3-embedix-021129
>
> ncftp /pub/linux/kernel/v2.4 > dir patch-2.4.18.bz2
> -rw-rw-r-- 1 536 536 826105 Feb 25 2002
> patch-2.4.18.bz2
>
> Any particular reason why you're using a 4 year old kernel?
>
> > -OpenZaurus 3.5.1
as far as I know, OpenZaurus 3.5.4 is comming soon, but the standard kernel is
still 2.4.18-xyz. The Zaurus 5500 was not ported to newer kernels, because
the implementation from sharp/lineo was just to ugly. Instead a direct 2.6
port was started but not finished up to now (see
http://www.cs.wisc.edu/~lenz/zaurus).
I don't know if netfilter is activated in the OpenZaurus kernels, but you can
build a kernel yourself and activate it (see www.openzaurus.org and
http://oe.handhelds.org/cgi-bin/moin.cgi/GettingStarted for the toolchain and
buildsystem).
Pavel Machek has send some patches recently to lkml for the 2.6 kernel, but I
don't know what the status is right now.
marvin
next prev parent reply other threads:[~2006-01-27 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 14:28 Lorne J. Leitman
2006-01-27 14:38 ` Erik Mouw
2006-01-27 19:30 ` Marc [this message]
2006-01-29 15:12 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200601272030.24079.marvin24@gmx.de \
--to=marvin24@gmx.de \
--cc=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome