mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Andreas Jellinghaus [c]" <aj@ciphirelabs.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] why was MODALIAS removed from usb kernel events? [u]
Date: Fri, 17 Aug 2007 17:05:35 +0200	[thread overview]
Message-ID: <200708171705.35793.aj@ciphirelabs.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0708171047170.2546-100000@iolanthe.rowland.org>

Am Freitag, 17. August 2007 schrieb Alan Stern:
> On Fri, 17 Aug 2007, Andreas Jellinghaus [c] wrote:
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit
> >diff;h=9f8b17e643fe6aa505629658445849397bda4e4f
> >
> > removes MODALIAS from one of the events, this breaks user space
> > applications like openct - everything that depends on getting an event
> > that has both the DEVICE= path to the usb device and any information on
> > the interface, so it can check if the device is something it supports (in
> > case of openct: smart card reader, i.e. bInterfaceClass 0b).
>
> There is no MODALIAS for these events because there are no drivers for
> the devices they report.  Perhaps you should be looking at
> usb_if_uevent() in drivers/usb/core/message.c instead.  Is the problem
> that this routine doesn't set DEVICE, BUSNUM, or DEVNUM?

I need some kernel event that has both DEVICE and MODALIAS set. 
up to including kernel 2.6.21 this seems to come from 
drivers/usb/core/driver.c if I read the code correctly, and then
it was removed.

udevmonitor --kernel --environment shows one event with both on 2.6.21 plain, 
but not on 2.6.22 plain.

Regards, Andreas

  reply	other threads:[~2007-08-17 15:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-17 14:22 Andreas Jellinghaus [c]
2007-08-17 14:50 ` [linux-usb-devel] " Alan Stern
2007-08-17 15:05   ` Andreas Jellinghaus [c] [this message]
2007-08-17 17:12     ` Alan Stern
2007-08-18 19:32       ` Andreas Jellinghaus [c]
2007-08-20 15:59         ` Alan Stern
2007-08-21  6:45           ` Andreas Jellinghaus [c]
2007-08-21  7:36 ` Greg KH
2007-08-21  8:39   ` Andreas Jellinghaus [c]
2007-08-21 11:41   ` Kay Sievers
2007-08-21 12:21     ` Andreas Jellinghaus [c]
2007-08-21 15:22       ` Kay Sievers
2007-08-21 12:41     ` Andreas Jellinghaus [c]

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=200708171705.35793.aj@ciphirelabs.com \
    --to=aj@ciphirelabs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    /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®