Hi!
I read your mail from the wwan0 interface :) .
This time I was able to understand the "netif" thing by re-reading the code.
The device works in ncm mode - the wdm device has became inaccessible, and any
attempt to write to it results in a LOT of unknown notifications, obviously.
My dmesg:
...
[ 124.508433] cdc_ncm 1-2:1.1: unknown notification 42 received: index 1 len 8
[ 137.673907] IPv6: ADDRCONF(NETDEV_UP): wwan0: link is not ready
[ 137.674431] usb 1-2: NCM: unexpected notification 0x01!
[ 137.674594] IPv6: ADDRCONF(NETDEV_CHANGE): wwan0: link becomes ready
[ 215.212011] usb 1-2: NCM: unexpected notification 0x01!
[ 215.338349] usb 1-2: NCM: unexpected notification 0x01!
[ 215.556161] usb 1-2: NCM: unexpected notification 0x01!
[ 215.732430] usb 1-2: NCM: unexpected notification 0x01!
[ 215.868418] usb 1-2: NCM: unexpected notification 0x01!
[ 216.108429] usb 1-2: NCM: unexpected notification 0x01!
[ 216.204367] usb 1-2: NCM: unexpected notification 0x01!
[ 216.364424] usb 1-2: NCM: unexpected notification 0x01!
[ 216.452420] usb 1-2: NCM: unexpected notification 0x01!
[ 216.676428] usb 1-2: NCM: unexpected notification 0x01!
[ 216.772163] usb 1-2: NCM: unexpected notification 0x01!
[ 216.876425] usb 1-2: NCM: unexpected notification 0x01!
[ 217.100426] usb 1-2: NCM: unexpected notification 0x01!
[ 217.244420] usb 1-2: NCM: unexpected notification 0x01!
[ 217.332432] usb 1-2: NCM: unexpected notification 0x01!
But now - no problems, the thing is quiet and all seems fine!
On Mon, 1 Jul 2013, Bj?rn Mork wrote:
==Date: Mon, 01 Jul 2013 19:59:51 +0200
==From: Bj?rn Mork <bjorn@xxxxxxx>
==To: Enrico Mioso <mrkiko.rs@xxxxxxxxx>
==Cc: linux-usb@xxxxxxxxxxxxxxx
==Subject: Re: Huawei E3131 wwan interface, partial success?
==
==Enrico Mioso <mrkiko.rs@xxxxxxxxx> writes:
==
==> Ah - I didn't knew there where other devices with an embedded AT channel - I
==> really don't imagine what could hide on those devices! :)
==
==Yes, but I did not think of it because in the case of the E367 this is a
==highly optional feature. MBIM has a standard management protocol, and
==the AT channel doesn't add anything useful.
==
==> I can't find the function call you're referrint to, sorry. :(
==
==Sorry, I should have noticed this was recently changed. It used to be
==
== netif_carrier_off(dev->net);
==
==before commit 8a34b0ae ("usbnet: cdc_ncm: apply usbnet_link_change"). I
==guess you are working in a v3.9 based tree?
==
==Remove that and see if you can get the network interface going.
==
==> And - another question. how can the cdc_ncm driver handle notifications if it
==> has no control over the ->control endpoint anymore?
==
==We'd need to extend the cdc-wdm subdriver interface with additional
==callbacks, so that cdc-wdm can call the appropriate network driver
==functions when it receives notifications it doesn't handle. But I
==believe implementing this can wait. Better focus on getting the basic
==functionality in place for now.
==
==> And - why I'm using a function called *_release_interface_* when I'm not
==> talking about an interface, but an endpoint? But guess this is off-topic :) !!
==
==I don't know...
==
==
==
==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
