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: [linux-usb-devel] Re: (usb) hotplugging with current modutils and
Date: Tue, 09 Jan 2001 16:25:01 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-97905747513546@msgid-missing> (raw)

This seems to me like a linux-usb issue ... I think some
things should to be done with usbutils, including:

    - Update them for 2.4.0 FCS style "modules.usbmap"

    - Resolve the issue of "forked libusb" (there's the
      libusb.sourceforge.net, and the one in "usbutils";
      don't install either one, pending resolution)

    - Provide RPM/APT support for usbutils

    - (maybe) merge the USB hotplug agent into this

That may or may not involve moving usbutils to the linux-usb
project.  I sort of like the idea that distros would just
bundle one package, but that would need some working.

Clearly, "end users" shouldn't need more than RPM/APT.

- Dave


----- Original Message ----- 
From: Norbert Preining <preining@logic.at>
To: <linux-hotplug-devel@lists.sourceforge.net>
Sent: Tuesday, January 09, 2001 12:18 AM
Subject: Re: [linux-usb-devel] Re: hotplugging with current modutils and usbdcvs


> On Die, 09 Jan 2001, Miles Lane wrote:
> > The only CVS tree I can find referenced in any way from
> > the homepage that mentioned usbutils is for libusb.
> 
> Take a look at  http://usb.cs.tum.edu/download.html
> 
> -- 
> ciao
> norb
> 



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

                 reply	other threads:[~2001-01-09 16:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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