Am 25.02.2011 01:06, schrieb Greg KH:
On Fri, Feb 25, 2011 at 12:31:29AM +0100, Josua Dietze wrote:
Am 24.02.2011 23:25, schrieb Greg KH:
Also, the line above isn't even _needed_ for people to test this device,
they can just echo the device id to the "new_id" file for the driver and
get it to bind properly, no driver changes are needed at all.
This is what was done initially. But the device (composite) will
need a mix of serial and network ports; one serial port is used to
initiate the connection via AT commands.
The interfaces have all class 255 AFAIK. The new_id attribute is not selective.
Or is there a way to exclude some of the interfaces from binding?
Just don't bind them in the probe function.
What I meant is if there is a way to influence the user space driver binding via
"new_id" to target only specific interfaces of a composite device ...
Josua Dietze
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
