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: /sbin/hotplug invocation for USB devices in 2.5.40
Date: Tue, 08 Oct 2002 07:32:07 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-103406277101783@msgid-missing> (raw)

As almost no one noticed, I changed the environment variables that
/sbin/hotplug is called with in 2.5.40 :)

This is what has changed from the previously documented info at
http://linux-hotplug.sourceforge.net/?selected=usb

For USB devices, /sbin/hotplug is called for the main device, and every
interface.  For the interfaces, the info in the above link is still set.
Previously, /sbin/hotplug only got called once, and we only sent the
first interface's information.  We should now be able to handle compound
devices much easier.

For the USB device (not the interface), the only environment variable
is:
	DEVICE = <place in driverfs tree for the device>
For the interface, it's the same as it used to be.

This variable is also set for every other /sbin/hotplug call that
happens (which is now for every type of device in the kernel, not just
the types we used to have.)

Now I know this overloads the existing DEVICE usage for USB devices, but
I think we can determine what do properly (basically just test for
DEVFS, and if it's not set, then we are looking at the driverfs entry
for the device.)

I also created a lot of individual driverfs files for the USB device,
basically everything that used to be specified by a environment variable
in the call to /sbin/hotplug, is now a value in a file.  So ideally, we
can get rid of those other variables for the USB call, and just rely on
the info present in driverfs.

I'll be doing the same thing for PCI devices to try to get rid of their
extra variables.

Does this all sound ok?  Problematic?  Even make any sense?

thanks,

greg k-h


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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

             reply	other threads:[~2002-10-08  7:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-08  7:32 Greg KH [this message]
2002-10-08 17:02 ` /sbin/hotplug invocation for USB devices in 2.5.40 David Brownell
2002-10-08 17:49 ` Patrick Mochel
2002-10-08 17:55 ` Oliver Neukum
2002-10-08 18:14 ` David Brownell
2002-10-08 18:18 ` Oliver Neukum
2002-10-08 18:18 ` Greg KH
2002-10-08 18:25 ` Greg KH
2002-10-08 21:00 ` David Brownell
2002-10-08 21:17 ` Greg KH
2002-10-08 21:18 ` David Brownell
2002-10-08 21:28 ` David Brownell
2002-10-08 21:39 ` Greg KH
2002-10-09 15:15 ` David Brownell
2002-10-10 20:35 ` Greg KH

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-103406277101783@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).