From: John Williams <jwilliams@itee.uq.edu.au>
To: uClinux development list <uclinux-dev@uclinux.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [uClinux-dev] ENOENT creating /dev/root on MTD RAM partition
Date: Tue, 03 Apr 2007 14:39:07 +1000 [thread overview]
Message-ID: <4611DA6B.5000409@itee.uq.edu.au> (raw)
In-Reply-To: <461057B4.8030209@itee.uq.edu.au>
I wrote:
> I'm working on the 2.6 kernel for MicroBlaze (embedded, NOMMU) arch.
> Like some other nommu archs, we typically mount root on an MTD RAM
> partition (either CRAMFS or ROMFS).
>
> All of this is working fine on 2.6.19 plus SnapGear 2.6.19-uc0-bigpatch
> NOMMU patchset.
>
> However, since coming forward to 2.6.20 (plus equiv. SnapGear patchset)
> mount_root is failing.
Problem solved. An error in the arch link script resulted in the
initcall_rootfs initcalls to not be invoked - thus the stub init_ramfs
wasn't mounted, and /dev didn't exist.
John
prev parent reply other threads:[~2007-04-03 4:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 1:09 ENOENT creating /dev/root on MTD RAM partition John Williams
2007-04-03 4:39 ` John Williams [this message]
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=4611DA6B.5000409@itee.uq.edu.au \
--to=jwilliams@itee.uq.edu.au \
--cc=linux-mtd@lists.infradead.org \
--cc=uclinux-dev@uclinux.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