From: Ian Thompson <iant@palmchip.com>
To: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Can't open root device
Date: Tue, 19 Jun 2001 17:13:21 -0700 [thread overview]
Message-ID: <3B2FEAA1.34DD1FFB@palmchip.com> (raw)
Hi,
I'm having some issues trying to open a ROM fs via initrd. It seems
like kind of a paradox: mount_root() calls blkdev_get(), which calls
rd_open(). In blkdev_get(), the comments mention that the block device
->open() method is not supposed to access anthing in the 'inode'
argument except ->i_rdev. However, rd_open() checks inode->i_bdev when
->i_rdev isn't INITRD_MINOR (->i_rdev is set to bd_dev in blkdev_get).
Currently my minor number is 0 (major is 1). Am I using the correct
major/minor numbers? Should I use INITRD_MINOR instead of 0? If I am
ok with 0, it appears that there is an inconsistency in the code...
Also, is there another driver I should try using instead of the ramdisk
driver? uClinux has a blkmem driver, but I haven't seen that here...
Thanks for your time,
-ian
--
----------------------------------------
Ian Thompson tel: 408.952.2023
Firmware Engineer fax: 408.570.0910
Palmchip Corporation www.palmchip.com
This message resent by the uclinux-dev@uclinux.org list server
http://www.uClinux.org/
reply other threads:[~2001-06-20 0:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3B2FEAA1.34DD1FFB@palmchip.com \
--to=iant@palmchip.com \
--cc=linux-mips@oss.sgi.com \
/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