[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200708171705.35793.aj@ciphirelabs.com>
Date: Fri, 17 Aug 2007 17:05:35 +0200
From: "Andreas Jellinghaus [c]" <aj@...hirelabs.com>
To: Alan Stern <stern@...land.harvard.edu>
Cc: linux-kernel@...r.kernel.org, linux-usb-devel@...ts.sourceforge.net
Subject: Re: [linux-usb-devel] why was MODALIAS removed from usb kernel events? [u]
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists