Dan Williams <dcbw@xxxxxxxxxx> writes:
> On Wed, 2012-01-25 at 14:31 +0100, Bjørn Mork wrote:
>> Encouraged by all the nice comments and feedback I got on the first
>> series with demo-quality code, I have now cleaned up the mess and
>> am hopefully closer to something that can be accepted.
>
> So I have to admit I got a bit side-tracked with something else. Could
> you give me a quick summary of where things are at WRT to these devices?
The split interface mode ("Linux mode") of the Huawei E392/E398 is
supported in usb-next/net-next.
The combined control/data qmi+wwan interface is not yet supported. The
"usb: cdc-wdm: subdriver support" patch series with the addition of the
required bugfix "usb: cdc-wdm: use dedicated lock for device list to fix
autoresume on open" will allow very simple usbnet based mini-drivers to
export the encapsulated QMI using cdc-wdm. This subdriver mode is still
under review in this thread.
> And then given the fun layout of the Qualcomm devices that I've talked
> about before, what's the path forward with those?
>
> IIRC the problem was with cdc-wdm and USB interface matching since the
> Gobi devices use the same class/subclass/protocols numbers for multiple
> ports. Oliver wasn't so keen on stuffing the interface number into the
> driver_data field, which is what we do to option.c for blacklisting
> specific interfaces.
As long as the interface is combined control+data, then the probing must
be done by the usbnet mini-driver anyway. cdc-wdm will just use whatever
interface and endpoint the main driver points it to.
IMHO we can just as well try to merge all these different QMI devices
into the qmi_wwan driver, and see if we can do some intelligent probing
there. I can try to put together something for testing Gobi if you
like.
Bjørn
--
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
