[linux-usb-devel] Patch : Select other-than-default configuration when no driver available for the default configuration

2003-08-01 Thread Bertin Philippe 
'Llo All,

The title seems contradictory : who would want to select
another-than-default configuration ? Is the default configuration not
_default_, are there no drivers for even the default configuration ? Well,
this is indeed not always the case. When a Windows driver e.g. NEEDS the
first configuration to be RNDIS (I'd doubt that it's legally even permitted
to make an RNDIS driver for Linux - read the RNDIS spec, first para of 1.1
...), there is to be a means to select the second USB configuration (being a
CDC- one). Well, usb.c does not foresee this (I'm speaking of the 2.4.20-
version).

This patch switches to the second (and so on, and so on ...) configuration
when there is no driver available for this configuration. It is made against
the (old) 2.4.20. I hope I don't make anyone furious about it ;)   I can
make it against the 2.6 too, if it gets granted. This patch works on SuSE
8.2 on Dell Laptop 8100.

Regards,

Philippe Bertin.


 usb.c.diff 


usb.c.diff
Description: Binary data

RE: [linux-usb-devel] Patch : Select other-than-default configuration when no driver available for the default configuration

2003-08-01 Thread Bertin Philippe 
True, but imagine what the situation was before : there was no checking at
all if the call to usb_find_drivers succeeded yes or no. So there, the
situation was not any better, was it ? It just supposed the 'default' driver
was available.

With the patch, there is still no checking whether there will, in the end,
be a loaded driver. But at least it gives the chance to the other drivers to
take a ticket ...

Regards,

Philippe Bertin.

-Original Message-
From: Oliver Neukum [mailto:[EMAIL PROTECTED]
Sent: vrijdag 1 augustus 2003 10:58
To: Bertin Philippe; '[EMAIL PROTECTED]'
Subject: Re: [linux-usb-devel] Patch : Select other-than-default
configuration when no driver available for the default configuration


 
 This patch switches to the second (and so on, and so on ...) configuration
 when there is no driver available for this configuration. It is made
against
 the (old) 2.4.20. I hope I don't make anyone furious about it ;)   I can
 make it against the 2.6 too, if it gets granted. This patch works on SuSE
 8.2 on Dell Laptop 8100.

How do you cope with the driver not being present at hotplug time?
With this scheme the device is in a random configuration when the
legitimate driver is loaded.

Regards
Oliver


---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel