On Tue, 2015-03-17 at 20:49 +0100, Bjørn Mork wrote:
> Sami Farin <[email protected]> writes:
> > On Mon, Feb 23, 2015 at 11:59:14 +0100, Bjørn Mork wrote:
> >> So my conclusion is that there is some higher level USB communication
> >> problem here, not directly involving neither usbnet nor the minidriver.
> >
> > Do you have new ideas as to where the problem might be?
> > I have now used the cdc_ether driver to transfer 1 TiB with zero rx/tx
> > errors.
>
> OK, that is an indication that my wild guess was wrong.
>
> I have really no idea why this fails. We obviously do something the
> modem doesn't like, but I don't know what it is. Sorry
>
> > I also noticed cdc_ether initialization or something does not work with
> > kernel
> > 4.0.0-rc4, I have to first setup it in 3.18.9 and then reboot to 4.0.0-rc4.
>
> That is unexpected and even more difficult to explain. There aren't
> many changes to usbnet or cdc_ether between v3.18 and v4.0-rc4:
>
> bjorn@nemi:/usr/local/src/git/linux$ git log --oneline v3.18..v4.0-rc4 --
> drivers/net/usb/{usbnet,cdc_ether}.c
> 51487ae736fe usbnet: re-use native hex2bin()
> f46ad73ac696 cdc-ether: implement MULTICAST flag on the device
> 55b42b5ca2dc Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
>
>
> I gues the only possibility is the multicast filter change, but it
> doesn't look like that should change anything by default. Any ideas on
> this one, Oliver?
Are you sure there's no firmware upload involved? Otherwise, yes
the most likely is the multicast change.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
