From: Oliver Neukum <oliver@neukum.name>
To: linux-hotplug@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: hotplugging to deal with firmware download
Date: Sun, 02 Jun 2002 21:59:37 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-102305527630492@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102297360623547@msgid-missing>
Am Sonntag, 2. Juni 2002 19:16 schrieb David Brownell:
> >>>>The problem is that this cannot simply work, because a filesystem
> >>>> may be mounted by nfs.
>
> If the goal is to boot a diskless Linux box (who supports those?)
> using a USB networking device that needs firmware download before
> it can be used ... that'd be _exactly_ analagous to needing to
> boot from a disk controller that needs firmware downloaded before
> it will work. In both cases, if the boot ROM doesn't download it,
> then the system won't boot.
Hi,
getting the firmware is not the problem, but getting the firmware
to the device can deadlock if you cause writing to the device
by allocating memory for the downloading.
Any memory allocation from user space can case writing to any
filesystem with dirty pages in cache.
Regards
Oliver
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
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:[~2002-06-02 21:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-01 23:16 [linux-usb-devel] Re: hotplugging to deal with firmware download Brad Hards
2002-06-02 5:50 ` Oliver Neukum
2002-06-02 8:19 ` Oliver Neukum
2002-06-02 11:11 ` Brad Hards
2002-06-02 17:16 ` David Brownell
2002-06-02 21:59 ` Oliver Neukum [this message]
2002-06-02 22:21 ` Brad Hards
2002-06-03 4:18 ` Oliver Neukum
2002-06-03 17:52 ` Greg KH
2002-06-03 21:00 ` Oliver Neukum
2002-06-03 21:55 ` Greg KH
2002-06-03 22:02 ` David Brownell
2002-06-03 22:26 ` Oliver Neukum
2002-06-03 22:35 ` Greg KH
2002-06-03 22:37 ` Greg KH
2002-06-03 22:48 ` Oliver Neukum
2002-06-03 22:58 ` Oliver Neukum
2002-06-03 23:05 ` Greg KH
2002-06-03 23:30 ` Oliver Neukum
2002-06-03 23:40 ` Greg KH
2002-06-04 8:06 ` Oliver Neukum
2002-06-04 19:32 ` David Brownell
2002-06-04 19:44 ` David Brownell
2002-06-05 11:45 ` Oliver Neukum
2002-06-05 14:19 ` David Brownell
2002-06-05 14:32 ` Oliver Neukum
2002-06-05 14:54 ` David Brownell
2002-06-05 21:48 ` Oliver Neukum
2002-06-06 0:25 ` David Brownell
2002-06-06 9:04 ` Andries.Brouwer
2002-06-06 12:54 ` Oliver Neukum
2002-06-06 14:55 ` Oliver Neukum
2002-06-06 17:16 ` David Brownell
2002-06-06 19:19 ` Andries.Brouwer
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=marc-linux-hotplug-102305527630492@msgid-missing \
--to=oliver@neukum.name \
--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).