linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: hotplugging to deal with firmware download
Date: Mon, 03 Jun 2002 21:55:58 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-102314156128133@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102297360623547@msgid-missing>

On Mon, Jun 03, 2002 at 11:00:03PM +0200, Oliver Neukum wrote:
> Am Montag, 3. Juni 2002 19:52 schrieb Greg KH:
> > On Sat, Jun 01, 2002 at 06:07:34PM +0200, Oliver Neukum wrote:
> > > So at present it would have to be something called as a hotplug script
> > > in the usual way ?
> > > The problem is that this cannot simply work, because a filesystem may
> > > be mounted by nfs.
> > >
> > > Would you consider a firmware loading driver that takes firmware from
> > > disk ?
> >
> > No, this should be done from userspace.
> 
> Very well then, how ?
> I see no plan to do it with the present power management system.

I agree.  That's why people are still working on the power management
system :)

> The devices are simply assumed to switch from suspended to working
> in kernel space. Suspended may mean off here.

If "suspended" means off, then the device should start up in the powered
off state, and re-enumerate as a new usb device on powerup.

If you _have_ to handle this today, then just leave the firmware within
the kernel driver, like all of the usb-serial devices have done :)

If you wait a while, the rest of the power management sections of the
kernel will hopefully come together, allowing the various states of
shutdown to work properly, and be enumerated by _userspace_ tools.
That's the whole driving force behind driverfs, which I think people
forget.

thanks,

greg k-h

_______________________________________________________________

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

  parent reply	other threads:[~2002-06-03 21:55 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
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 [this message]
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-102314156128133@msgid-missing \
    --to=greg@kroah.com \
    --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).