On Thu, 17 May 2012 00:01:35 +0200
Bjørn Mork <bjorn@xxxxxxx> wrote:
> I believe the main reason is that it will bind to the correct serial
> interfaces and nothing else, while the option driver will bind to almost
> anything - including any QMI/wwan interface.
>
> > bNumInterfaces 6
>
> But that won't work with qcserial. It requires bNumInterfaces to be 1, 3
> or 4. So use option, but make sure to blacklist the interface used for
> QMI/wwan. I'm guessing that's interface #3, but please test.
>
I don't quite understand how the blacklisting is supposed to work. If I wanted option not to bind to specific interfaces, should I use option_blacklist_info.reserved for this?
I actually tried the following in option.c:
#define TELEWELL_PRODUCT_TW3G_HSPA 0x9801
static const struct option_blacklist_info telewell_tw3g_hspa_blacklist = {
.sendsetup = BIT(0) | BIT(1) | BIT(2) | BIT(3) | BIT(4) | BIT(5) | BIT(6) | BIT(7) | BIT(8),
.reserved = BIT(0) | BIT(1) | BIT(2) | BIT(3) | BIT(4) | BIT(5) | BIT(6) | BIT(7) | BIT(8),
};
...
{ USB_DEVICE(LONGCHEER_VENDOR_ID, TELEWELL_PRODUCT_TW3G_HSPA),
.driver_info = (kernel_ulong_t)&telewell_tw3g_hspa_blacklist
},
and no matter what blacklist bits I set (I figure the one above should pretty much blacklist everything?), dmesg always tells me stuff like this:
[81165.237890] option 2-3.4:1.0: GSM modem (1-port) converter detected
[81165.238079] usb 2-3.4: GSM modem (1-port) converter now attached to ttyUSB0
and consequently there will be four ttyUSB devices, of which only the two in the middle I am able to use for dialing.
I started with .driver_info = (kernel_ulong_t)&net_intf3_blacklist, I believe this is what you suggested me to do, no?
So, is the blacklisting procedure supposed to prevent those two extra ttyUSB devices from being created? Sorry I'm a bit lost here :)
-Olli
--
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
