mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier.adi@gmail.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Greg KH <greg@kroah.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: usbutils 0.81 release
Date: Wed, 29 Apr 2009 21:48:33 -0400	[thread overview]
Message-ID: <8bd0f97a0904291848le808891kff973b1677b7cd33@mail.gmail.com> (raw)
In-Reply-To: <ac3eb2510904291745j48220c12oe2a2b91e981ea403@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]

On Wed, Apr 29, 2009 at 20:45, Kay Sievers wrote:
> On Thu, Apr 30, 2009 at 01:38, Mike Frysinger wrote:
>> On Wed, Apr 29, 2009 at 14:30, Greg KH wrote:
>>> On Wed, Apr 29, 2009 at 02:17:12PM -0400, Mike Frysinger wrote:
>>>> >> find being able to run `usbmodules` pretty useful ... i wrote a script
>>>> >> for fun:
>>>> >> http://sources.gentoo.org/sys-apps/usbutils/files/usbmodules.sh
>>>> >
>>>> > Did that work on any 2.6 kernel?
>>>>
>>>> it's the only version ive tested it with ... but it doesnt parse any
>>>> kernel module directly, it reads the generated modules.usbmap file
>>>>
>>>> > There's no reason we can't add "-k" support to lsusb like lspci has to
>>>> > show the modules assigned to different devices.
>>>>
>>>> the method i posted above only needs the module to be compiled, not loaded
>>>
>>> As the map files are depreciated, I wouldn't continue to rely on it, it
>>> will break in the future when the kernel stops generating those files.
>>
>> guess i'll have to rewrite it to parse the .ko modules directly like
>> the usbmap is generated now
>
> Can't you use the modules.aliases file? That should stay around and
> there should be the same information contained.

should be fine if it's going to be sticking around

any comments on the attached file ?  in theory, it could be easily
extended for pci and other busses ...
-mike

[-- Attachment #2: usbmodules.sh --]
[-- Type: application/x-sh, Size: 1071 bytes --]

  reply	other threads:[~2009-04-30  1:48 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 19:35 Greg KH
2009-04-27 20:48 ` Alan Stern
2009-04-27 21:00   ` Greg KH
2009-04-27 21:21     ` Alan Stern
2009-04-27 21:36       ` Kay Sievers
2009-04-29 14:23       ` Benny Amorsen
2009-04-29 15:51         ` Alan Stern
2009-04-29 17:27           ` Mike Frysinger
2009-04-29 17:42           ` Greg KH
2009-04-29 20:23             ` Alan Stern
2009-04-27 21:07   ` Kay Sievers
2009-04-27 21:54     ` Alan Stern
2009-04-27 22:02       ` Kay Sievers
2009-04-29 17:53 ` Mike Frysinger
2009-04-29 18:07   ` Greg KH
2009-04-29 18:17     ` Mike Frysinger
2009-04-29 18:30       ` Greg KH
2009-04-29 23:38         ` Mike Frysinger
2009-04-30  0:45           ` Kay Sievers
2009-04-30  1:48             ` Mike Frysinger [this message]
2009-04-30  1:54               ` Kay Sievers
2009-04-30  1:58                 ` Mike Frysinger
2009-04-29 18:59       ` Kay Sievers
2009-04-29 19:18         ` Henrique de Moraes Holschuh
2009-04-29 19:26           ` Greg KH
2009-04-29 19:44             ` Kay Sievers
2009-04-29 19:27           ` Kay Sievers
2009-04-29 19:50             ` Henrique de Moraes Holschuh
2009-04-29 19:55               ` Kay Sievers
2009-04-29 20:00                 ` Henrique de Moraes Holschuh
2009-04-29 20:39                   ` Kay Sievers
2009-04-30  6:31           ` Bjørn Mork
2009-04-29 19:23         ` Greg KH
2009-04-29 21:42           ` Valdis.Kletnieks
2009-04-29 21:56             ` Greg KH
2009-04-29 22:19               ` Valdis.Kletnieks
2009-04-30  1:48               ` Kay Sievers
2009-04-30  1:56                 ` Mike Frysinger
2009-04-30  2:06                   ` Kay Sievers
2009-04-30  2:13                     ` Mike Frysinger
2009-04-30  4:54                       ` Greg KH
2009-04-29 21:57             ` Kay Sievers

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=8bd0f97a0904291848le808891kff973b1677b7cd33@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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

all inboxes | Powered by JetHome®