From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: Kernel Firmware Loading
Date: Fri, 04 Nov 2005 15:14:40 +0000 [thread overview]
Message-ID: <436B7AE0.9070809@ums.usu.ru> (raw)
In-Reply-To: <4365DBD9.2040407@ukonline.co.uk>
Duncan Sands wrote:
>On Friday 4 November 2005 15:46, Alexander E. Patrakov wrote:
>
>
>>Duncan Sands wrote:
>>
>>
>>
>>>>... I don't see why the kernel can't wait until userspace has been mounted before it tries to load the firmware.
>>>>
>>>>
>>>>
>>>>
>>>Me neither. I mean, why do coldplugging of all devices (rather than just an
>>>essential few) before the root filesystem is mounted?
>>>
>>>
>>>
>>>
>>Please propose how are you going to tell the kernel the list of
>>"essential" devices.
>>
>>
>
>Hopefully the list of essential devices needing coldplugging is empty. I had in mind:
>just what's needed to mount the root filesystem. What's the problem with that?
>
>
E.g., you want to specify that only /dev/sda is needed because you have
your root filesystem on your SCSI disk. But your SCSI controller is a
PCI device. So we need to walk over all PCI devices and bind drivers to
them. One of them will register itself as a SCSI controller driver. But
all PCI devices before that one will also be initialized then, and may
(or may not) want firmware or other initialization!
And now suppose that after hardware upgrade your PCI cards were
shuffled, how would you handle that?
--
Alexander E. Patrakov
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-11-04 15:14 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 8:54 Kernel Firmware Loading Andrew Benton
2005-10-31 9:37 ` Alexander E. Patrakov
2005-10-31 10:04 ` Andrew Benton
2005-10-31 10:59 ` Duncan Sands
2005-10-31 10:59 ` Alexander E. Patrakov
2005-10-31 11:08 ` Marco d'Itri
2005-10-31 11:18 ` Duncan Sands
2005-10-31 11:50 ` Marco d'Itri
2005-10-31 13:10 ` Kay Sievers
2005-10-31 13:27 ` Duncan Sands
2005-10-31 14:35 ` Kay Sievers
2005-10-31 14:41 ` Duncan Sands
2005-10-31 14:54 ` Kay Sievers
2005-10-31 16:29 ` linas
2005-10-31 16:33 ` Marco d'Itri
2005-10-31 21:15 ` Andrew Benton
2005-11-01 9:48 ` Duncan Sands
2005-11-01 11:15 ` Andrew Benton
2005-11-01 15:56 ` Alexander E. Patrakov
2005-11-01 16:59 ` linas
2005-11-01 21:19 ` Andrew Benton
2005-11-02 2:09 ` Alexander E. Patrakov
2005-11-02 6:20 ` Alexander E. Patrakov
2005-11-02 6:28 ` Alexander E. Patrakov
2005-11-02 23:22 ` Andrew Benton
2005-11-03 8:08 ` Duncan Sands
2005-11-04 14:46 ` Alexander E. Patrakov
2005-11-04 14:52 ` Duncan Sands
2005-11-04 15:14 ` Alexander E. Patrakov [this message]
2005-11-07 15:48 ` Patrick Mansfield
2005-11-08 8:16 ` Alexander E. Patrakov
2005-11-08 17:54 ` Greg KH
2005-11-08 18:37 ` Patrick Mansfield
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=436B7AE0.9070809@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).