From: Ben Collins <bcollins@debian.org>
To: "David N. Welton" <davidw@eidetix.com>
Cc: linux-kernel@vger.kernel.org, davidwnwelton@gmail.com
Subject: Re: boot from usb flash - wake boot process when disk is ready?
Date: Fri, 28 May 2004 08:12:50 -0400 [thread overview]
Message-ID: <20040528121250.GC26289@phunnypharm.org> (raw)
In-Reply-To: <40B700F2.80208@eidetix.com>
On Fri, May 28, 2004 at 11:05:54AM +0200, David N. Welton wrote:
> [ Please CC replies to me - thanks! ]
>
> Hi,
>
> We're toying around with the idea of booting an embedded system off of
> USB flash (pros, cons, and advice about this would be appreciated, by
> the way), and I had a look at several of the existing patches to do this
> without going through the process of creating an initrd image. That
> adds complexity and time to the boot process that we would prefer to
> avoid, although it appears that the kernel folks in the first thread
> cited are in favor of initrd....
We have the same problem for firewire and sbp2 disks. I've often thought
of adding a CONFIG_IEEE1394_BOOT_SUPPORT config option where the
ieee1394 subsystem, if compiled with this option and built into the
kernel, would block it's init until the bus scan and device probes were
complete.
It gets kind of complicated, mainly because this should only be done
when a new host is added, and not for normal bus resets, and ideally
only at boot (e.g. not when a PCMCIA card is inserted sometime after
boot).
The complicated part is that the host controllers are seperate drivers
from the core. So the core can't block in it's init, since there are no
controllers at that point. The logic needs to be in the host-add
callbacks (same for USB and firewire). Since there's the possibility
(especially with USB) that there is more than one host controller, you
would have to do this for all of them, since the disk device may be on a
later controller in the PCI detection process.
Question is, is there a variable that can be looked at to see if init
has been started yet? If there is, then the logic could be invoked in
host-add whenever we are in pre-init state (IOW, no userspace is running
yet).
That would make it work more like standard SCSI hosts. USB could do the
same.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
prev parent reply other threads:[~2004-05-28 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 9:05 boot from usb flash - wake boot process when disk is ready? David N. Welton
2004-05-28 9:28 ` Kalin KOZHUHAROV
2004-05-28 9:33 ` Kalin KOZHUHAROV
2004-05-28 9:37 ` Kalin KOZHUHAROV
2004-05-28 12:12 ` Ben Collins [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=20040528121250.GC26289@phunnypharm.org \
--to=bcollins@debian.org \
--cc=davidw@eidetix.com \
--cc=davidwnwelton@gmail.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