On Saturday 09 February 2013 20:16:20 Bjørn Mork wrote:
> Oliver Neukum <oli...@neukum.org> writes:
> > On Saturday 09 February 2013 18:41:52 Bjørn Mork wrote:
> Well, OK..., "generic" then. In the sense that the attribute stays the
> same regardless of whether the value is hardcoded in the driver (QMI),
> or parsed from wMaxCommand (CDC WDM) or wMaxControlMessage (CDC MBIM)
>
> Not sure I understand what you want here... I am trying to avoid having
> three different attributes for the three drivers currently needing this
> number.
I would say that the most generic solution would be an ioctl()
> > Really, ideally user space would not know what driver is handling
> > the control channel.
>
> Well, as it is now user space has a long tradition for looking at driver
> names. ModemManager has done that for quite while when it comes to
> serial drivers, because the driver name is one of the few information
> sources available telling it something about the expected protocols.
But that has caused the problems. If you get cdc-acm, you know nothing.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
