From: David Jander <david.jander@protonic.nl>
To: Wolfgang Denk <wd@denx.de>
Cc: HappyPhot <happyphot@gmail.com>, linuxppc-embedded@ozlabs.org
Subject: Re: VFS: Cannot open root device "31:03" or unknown-block(31,3)
Date: Mon, 9 Jan 2006 09:45:21 +0100 [thread overview]
Message-ID: <200601090945.22564.david.jander@protonic.nl> (raw)
In-Reply-To: <20060106150854.918FF353A43@atlas.denx.de>
On Friday 06 January 2006 16:08, Wolfgang Denk wrote:
> This is a serious misunderstanding. There is no such thing like a
> specific kernel version which is supported by the ELDK.
True, but not entirely.
ELDK-3.1.1 has a glibc compiled with support of a certain version of the
kernel (I guess it's 2.4.xx), so newer kernels might run (because they are
obviously backwards compatible), but some features of 2.6 cannot be used
(e.g. support for the latest syscalls, different HZ, etc...)
A second issue is the boot procedure. If you are a beginner with linux, you'd
probably start booting from NFS root as it gets installed in the ELDK/ppc_xxx
directory. That probably won't work very well with latest 2.6 kernels (device
files missing, sysfs not mounted, shmfs has different name, etc...)
A third issue is the compiler issue. Some newer kernels might not compile
correctly anymore with older compilers.
These three things are what I meant with "supported" or "not supported".
> The ELDK is primarily a *toolkit* which works with arbitrary C and
> C++ programs and with any version of the kernel tree (at least in
> theory; very recent version s of the Linux kernel [ > 2.6.14] cannot
> be compiled with ELDK 3.1.x any more, but this is a different issue).
See what I mean? HappyPhot did just that: compile 2.6.14.2 with ELDK 3.1.1!!!
> > > Do you know where to get the infomation about which kernel version it
> > > supports?
>
> The ELDK supports *any* kernel version.
Ok, let's talk about "recommended" kernel then. I would never recommend
someone unexperienced to start with a combination of ELDK-3.1.1 and kernel
2.6.xx.
> > The one that comes with that version of ELDK? Just a guess ;-)
>
> Wrong guess.
But it'd still be the one with most chances of success unless there are known
problems with that kernel on a Sandpoint board.
Greetings,
--
David Jander
Protonic Holland.
next prev parent reply other threads:[~2006-01-09 8:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 14:48 VFS: Cannot open root device "31:03" or unknown-block(31,3) HappyPhot
2006-01-02 15:57 ` David Jander
2006-01-03 2:48 ` HappyPhot
[not found] ` <200601031410.55884.david.jander@protonic.nl>
[not found] ` <004701c611a8$557dbf00$0760120a@photon>
2006-01-05 7:52 ` David Jander
2006-01-06 14:09 ` HappyPhot
2006-01-06 14:19 ` David Jander
2006-01-06 15:08 ` Wolfgang Denk
2006-01-09 8:45 ` David Jander [this message]
2006-01-09 13:05 ` 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=200601090945.22564.david.jander@protonic.nl \
--to=david.jander@protonic.nl \
--cc=happyphot@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wd@denx.de \
/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).