On 01/06/2015 03:58 AM, Bjørn Mork wrote:
> Johan Hovold <johan@xxxxxxxxxx> writes:
>
>> Ok, let's move the PID to option and if it turns out that more of these
>> devices require the modem-control signals (e.g. with more recent
>> firmware) we can consider moving it back after adding such support to
>> qcserial.
>>
>> Bjørn, do you see any problems with this? Are there more interface
>> layouts for these devices out there perhaps (making options blacklisting
>> a bad fit)?
> No, I don't see any problem. It seems like the reasonable thing to do.
> I would have added these devices to the option driver in the first place
> had I known about the setup requirements. Sorry for not catching that
> earlier. And thanks to Reinhard for tracking this down.
>
> There are plenty of different interface layouts for these devices, but
> Sierra Wireless use consistent interface numbering for different
> functions, so the blacklist_info should work fine regardless.
>
> Note however that these devices also have multiple PID identities (and
> possibly also different VIDs?). The other identities may or may not have
> similar issues with the qcserial driver. I don't know. But some of these
> identities are shared with other devices, which complicates matters a
> bit.
>
This also affects the Dell Wireless 5808e, a branded version of the
Sierra Wireless EM7355. Again, moving it from the qcserial driver to the
option driver, which calls send_setup, allows URCs to appear.
Is it possible to test if the MC7710 also works with the option driver
(does send_setup cause problems with it)? If that still works, are there
any reasons not to move all of the devices using the Sierra Wireless
layout (DEVICE_SWI) from the qcserial driver to the option driver?
David
��.n��������+%������w��{.n�����{���)�� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
