Greg KH wrote:
In a quick glance, I don't see a problem. But make sure the driver is
correctly intregrated into the build process, otherwise the hotplug
tables will not get updated properly.
Good luck,
Hello,
I found this in drivers/usb/core/usb.c (usb_register):
[...] The list of unattached
*
On Sat, Feb 07, 2004 at 09:10:00AM +0100, Alexander Schulz wrote:
> Greg KH wrote:
> >On Fri, Feb 06, 2004 at 09:10:27PM +0100, Alexander Schulz wrote:
> >
> >>usbserial 1-1.3:1.0: Saal Serial converter detected
> >>usb 1-1.3: Saal Serial converter now attached to ttyUSB0 (or usb/tts/0
> >>for dev
On Fri, Feb 06, 2004 at 09:10:27PM +0100, Alexander Schulz wrote:
> usbserial 1-1.3:1.0: Saal Serial converter detected
> usb 1-1.3: Saal Serial converter now attached to ttyUSB0 (or usb/tts/0 for devfs)
> usb 1-1.3: Saal Serial converter now attached to ttyUSB1 (or usb/tts/1 for devfs)
Ah, so thi
Greg KH wrote:
On Fri, Feb 06, 2004 at 07:54:59PM +0100, Alexander Schulz wrote:
Hello,
I have a homebuild device here with 3 Interfaces. Two of them are
simple char devices handled by drivers derived from usb-sceleton.c
When I load these drivers and the device is already connected, it
is detecte
On Fri, Feb 06, 2004 at 07:54:59PM +0100, Alexander Schulz wrote:
> Hello,
>
> I have a homebuild device here with 3 Interfaces. Two of them are
> simple char devices handled by drivers derived from usb-sceleton.c
> When I load these drivers and the device is already connected, it
> is detected by
Hello,
I have a homebuild device here with 3 Interfaces. Two of them are
simple char devices handled by drivers derived from usb-sceleton.c
When I load these drivers and the device is already connected, it
is detected by the drivers. I can use both drivers immediately.
But when I load the driver f
