cdc_ncm tagging of Huawei devices as wwan

Aleksander Morgado aleksander at lanedo.com
Tue Nov 19 07:05:51 PST 2013


On 19/11/13 14:21, Bjørn Mork wrote:
>>>>> Hard to tell... I guess we'll end up needing either a list of wwan
>>>>> >>> > modules or a list of non-wwan modules, whatever is easier?
>>> >> I guess that is easy after all: I current know of 1 - one - non-wwan PID
>>> >> and 0 - zero - wwan PIDs.
>>> >> 
>>> >> So it has to be wwan by default with a per-PID non-wwan whitelist.
>> >
>> > I wonder if some automagic can be setup so that e.g. if the device
>> > doesn't expose an AT port it is by default non-wwan.
> It's hard to do that in the kernel.
> 
> The whole wlan/eth/usb/wwan type issue is misplaced.  That kind of
> information has never had anything to do in the kernel, and we've seen
> it for a long time.  Having to add specific entries in class drivers
> flagging devices as "wwan" is so wrong it's not even funny.  But it's
> probably too late to whine more about that.
> 
> But maybe userspace should just start to ignore some of these kernel
> hints, taking them as nothing more than hints?

In particular, ModemManager won't do anything if it only gets a wwan
port from a device, it will just completely ignore it. Didn't check, but
maybe NetworkManager is actually assuming that if the net device is
flagged as wwan then it's MM territory, while it shouldn't do that?

-- 
Aleksander


More information about the ModemManager-devel mailing list