linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Usb hotplug on 2.2 kernels
Date: Sun, 21 Jan 2001 18:40:50 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-98010216103190@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98005781016853@msgid-missing>

There's a certain level of support already, as I understand it,
which relies on something other than modutils providing the
tables mapping device descriptors to driver names.

The current hotplug scripts ship a "usb.distmap" file with
that information.  Currently generated using a 2.4 build
(mostly correct for 2.2.18 drivers).

- Dave


----- Original Message ----- 
From: Keith Owens <kaos@ocs.com.au>
To: <linux-hotplug-devel@lists.sourceforge.net>
Sent: Saturday, January 20, 2001 10:16 PM
Subject: Usb hotplug on 2.2 kernels


> Some people have mentioned usb hotplug support on 2.2 kernels, as an
> add on patch.  Does it use depmod or does it use a separate hand built
> table?  If it uses depmod, what does struct usb_device_id look like?
> 
> 
> _______________________________________________
> Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
> Linux-hotplug-devel@lists.sourceforge.net
> http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel


_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

      parent reply	other threads:[~2001-01-21 18:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-21  6:16 Usb hotplug on 2.2 kernels Keith Owens
2001-01-21 17:06 ` Greg KH
2001-01-21 18:40 ` David Brownell [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=marc-linux-hotplug-98010216103190@msgid-missing \
    --to=david-b@pacbell.net \
    --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).