From: Pedro Lopez-Cabanillas <plcl@telefonica.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Vosonic's X-Drive 2030
Date: Wed, 07 May 2003 22:36:02 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-105234709004424@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-105222093406662@msgid-missing>
On Thursday 08 May 2003 00:17, Randy.Dunlap wrote:
> On Thu, 8 May 2003 00:18:33 +0200 Pedro Lopez-Cabanillas
<plcl@telefonica.net> wrote:
> | On Thursday 08 May 2003 00:24, David Brownell wrote:
> | > >>>>>usb-storage 0x0000 0x0d7d 0x0240 0x0000
> | > >>>>> 0x0000
> | > >>>>>
> | > >>>>>usb-storage 0x0003 0x7d0d 0x4002 0x0000
> | > >>>>> 0x0000
> | >
> | > IF the byte order is wrong in "modules.usbmap",
> | > that'd be some kind of modutils bug...
> |
> | Sorry, but the bug was mine. We were talking about how to setup the
> | "usb.usermap" file, and my mistake was to use vendor and product ids from
> | lsusb directly. Later, i've checked the output from usbview, what is
> | right AFAIK.
>
> So there is no problem AFA you know? with lsusb or modutils or usbview?
>
> If so, that's good news.
To clarify:
- usbview output is correct AFAIK. It parses "/proc/bus/usb/devices", then
this file is also correct.
- lsusb output is wrong, as stated by the message from Alexander Kühn, and
also from your ancient messages to the linux-usb-devel list. Maybe usbmodules
(from usbutils package) is also wrong.
- I don't know about modutils, i don't have any data to think it can be wrong.
The file "usb.usermap" is not generated by modutils at all. It's a
hand-maintained file.
Regards,
Pedro
--
ALSA Library Bindings for Pascal
http://alsapas.alturl.com
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
_______________________________________________
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:[~2003-05-07 22:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 11:32 Vosonic's X-Drive 2030 Alexander Kühn
2003-05-06 17:39 ` Pedro Lopez-Cabanillas
2003-05-06 18:30 ` Pedro Lopez-Cabanillas
2003-05-06 18:50 ` Alexander Kühn
2003-05-07 3:17 ` Randy.Dunlap
2003-05-07 3:38 ` Randy.Dunlap
2003-05-07 21:54 ` Pedro Lopez-Cabanillas
2003-05-07 22:17 ` Randy.Dunlap
2003-05-07 22:18 ` Pedro Lopez-Cabanillas
2003-05-07 22:24 ` David Brownell
2003-05-07 22:36 ` Pedro Lopez-Cabanillas [this message]
2003-05-08 18:48 ` Randy.Dunlap
2003-05-08 19:10 ` Pedro Lopez-Cabanillas
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-105234709004424@msgid-missing \
--to=plcl@telefonica.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).