From: Ron Bianco <ronb@lcsaudio.com>
To: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: Kernel choices for 824x with ext3 FS
Date: Tue, 21 Oct 2003 15:36:48 -0700 [thread overview]
Message-ID: <000701c39823$d04388b0$4d00a8c0@warp-speed> (raw)
In-Reply-To: <20031021201042.534DAC59E4@atlas.denx.de>
> >
> > I've been looking at Denx's 2.4.4 port, linuxppc 2.5, linux 2.4.22 and the
> > latest 2.6.0-test trees.
>
> You can also use our linuxppc_2_4_devel tree from CVS (version 2.4.20)
Thanks, I wasn't sure what that module name referred to or the tree's status.
I just did a cvs checkout on it.
I suppose it is a superset of the linux_2_4_devel tree at penguinppc.org?
> > Unfortunately we can't use 2.4.4 as ext3 FS support is not present.
> > FYI, we may also have a need to use RTAI.
>
> We use our linuxppc_2_4_devel tree to validate the PowerPC port of RTAI.
Very cool and helpful.
I see other advantages to 'following the lead' of folks that are much more
kernel savvy, as well.
It's probably best for us to go with that 2.4.20 for now.
Our specific patches for our rather odd ball board should be easier on 2.6.0
later, once I get some experience with 2.4.20.
> I think our 2.4.20 tree is pretty stable; this is one reason we don't
> support more recent versions yet.
Yes that is a major concern. Unfortunately we still don't have much in the way
of resources to contribute to general kernel debugging or development. But I
will post what might be of interest as things proceed.
Cheers, Ron
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-10-21 22:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 19:47 Kernel choices for 824x with ext3 FS Ron Bianco
2003-10-21 20:10 ` Wolfgang Denk
2003-10-21 22:36 ` Ron Bianco [this message]
2003-10-22 8:31 ` Wolfgang Denk
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='000701c39823$d04388b0$4d00a8c0@warp-speed' \
--to=ronb@lcsaudio.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).