Pasi Kärkkäinen writes:
> I applied the patch on top of Linux 3.13.6 kernel and now I'm able to use the
> wwan0 NCM interface successfully!
> I do get an IP with a dhcp client (this failed earlier without the patch),
> and Internet seems to work OK.
> So the patch definitely fixes the problem
On Mon, Mar 17, 2014 at 03:23:22PM +0100, Bjørn Mork wrote:
> Pasi Kärkkäinen writes:
> > On Mon, Mar 17, 2014 at 02:15:23PM +0100, Bjørn Mork wrote:
> >
> >> I still don't know for sure, but I do hope this bug is the real cause of
> >> the problems you are having. I'll send you a patch for testi
linux-usb@vger.kernel.org,
==Enrico Mioso , Oliver Neukum
==Subject: Re: [PATCH net-next v6 0/3] The huawei_cdc_ncm driver / E3276 problem
==
==Pasi Kärkkäinen writes:
==> On Mon, Mar 17, 2014 at 02:15:23PM +0100, Bjørn Mork wrote:
==>
==>> I still don't know for sure, but I d
Pasi Kärkkäinen writes:
> On Mon, Mar 17, 2014 at 02:15:23PM +0100, Bjørn Mork wrote:
>
>> I still don't know for sure, but I do hope this bug is the real cause of
>> the problems you are having. I'll send you a patch for testing as soon
>> as it is ready.
>>
>
> Sure. I'll be happy to test the
On Mon, Mar 17, 2014 at 02:15:23PM +0100, Bjørn Mork wrote:
> Pasi Kärkkäinen writes:
>
> > After playing with it for a while I got this:
> >
> > [ 1082.972880] cdc_ncm_setup: huawei_cdc_ncm 3-1:1.1: dwNtbInMaxSize=262144
> > dwNtbOutMaxSize=32768 wNdpOutPayloadRemainder=2 wNdpOutDivisor=4
> >
Pasi Kärkkäinen writes:
> After playing with it for a while I got this:
>
> [ 1082.972880] cdc_ncm_setup: huawei_cdc_ncm 3-1:1.1: dwNtbInMaxSize=262144
> dwNtbOutMaxSize=32768 wNdpOutPayloadRemainder=2 wNdpOutDivisor=4
> wNdpOutAlignment=4 wNtbOutMaxDatagrams=0 flags=0x1f
> [ 1082.972893] cdc_n
Bjørn Mork writes:
> But looking closer, I see that the SET_NTB_FORMAT returned -EPIPE,
> i.e. stall. The driver currently ignores this error, which is why we
> end up with different device and host settings.
>
> Anyone know what the proper driver action is? Note that this error
> cannot happen
Bjørn Mork writes:
> But here we have a device which does not comform to spec (that's OK,
> Huawei doesn't claim it does - this is a vendor specific function after
> all), and which seems to be locked to 32 bit mode? Either it requires
> the 32 bit variant, or we are doing something "wrong" duri
On Mon, Mar 17, 2014 at 01:59:19PM +0200, Pasi Kärkkäinen wrote:
> On Mon, Mar 17, 2014 at 12:31:53PM +0100, Bjørn Mork wrote:
> > Pasi Kärkkäinen writes:
> >
> > > http://pasik.reaktio.net/huawei-e3276-usbmon3.pcapng
> > >
> > > (I did move the dongle to a different usb bus nr 3 to make it the o
On Mon, Mar 17, 2014 at 12:31:53PM +0100, Bjørn Mork wrote:
> Pasi Kärkkäinen writes:
>
> > http://pasik.reaktio.net/huawei-e3276-usbmon3.pcapng
> >
> > (I did move the dongle to a different usb bus nr 3 to make it the only
> > device on that bus before capturing..)
>
> Thanks. That helps.
>
Pasi Kärkkäinen writes:
> http://pasik.reaktio.net/huawei-e3276-usbmon3.pcapng
>
> (I did move the dongle to a different usb bus nr 3 to make it the only device
> on that bus before capturing..)
Thanks. That helps.
> So what I did:
>
> - Start wireshark capture on USB bus nr 3.
> - Plug in t
On Fri, Mar 14, 2014 at 12:16:55PM -0500, Dan Williams wrote:
> On Fri, 2014-03-14 at 16:25 +0200, Pasi Kärkkäinen wrote:
> > On Fri, Mar 14, 2014 at 02:33:36PM +0100, Bjørn Mork wrote:
> > > Pasi Kärkkäinen writes:
> > > > On Fri, Mar 14, 2014 at 10:24:51AM +0100, Bjørn Mork wrote:
> > > >> Pasi
On Fri, 2014-03-14 at 16:25 +0200, Pasi Kärkkäinen wrote:
> On Fri, Mar 14, 2014 at 02:33:36PM +0100, Bjørn Mork wrote:
> > Pasi Kärkkäinen writes:
> > > On Fri, Mar 14, 2014 at 10:24:51AM +0100, Bjørn Mork wrote:
> > >> Pasi Kärkkäinen writes:
> > >>
> > >> > # ifconfig wwp0s26u1u5i1
> > >> > w
On Fri, Mar 14, 2014 at 02:33:36PM +0100, Bjørn Mork wrote:
> Pasi Kärkkäinen writes:
> > On Fri, Mar 14, 2014 at 10:24:51AM +0100, Bjørn Mork wrote:
> >> Pasi Kärkkäinen writes:
> >>
> >> > # ifconfig wwp0s26u1u5i1
> >> > wwp0s26u1u5i1: flags=4163 mtu 1500
> >> > inet 10.8.219.204 net
Pasi Kärkkäinen writes:
> On Fri, Mar 14, 2014 at 10:24:51AM +0100, Bjørn Mork wrote:
>> Pasi Kärkkäinen writes:
>>
>> > # ifconfig wwp0s26u1u5i1
>> > wwp0s26u1u5i1: flags=4163 mtu 1500
>> > inet 10.8.219.204 netmask 255.255.255.248 broadcast 10.8.219.207
>> > inet6 fe80::e5b:
On Fri, Mar 14, 2014 at 10:24:51AM +0100, Bjørn Mork wrote:
> Pasi Kärkkäinen writes:
>
> > # ifconfig wwp0s26u1u5i1
> > wwp0s26u1u5i1: flags=4163 mtu 1500
> > inet 10.8.219.204 netmask 255.255.255.248 broadcast 10.8.219.207
> > inet6 fe80::e5b:8fff:fe27:9a64 prefixlen 64 sco
Am 14.03.2014 10:24, schrieb Enrico Mioso:
Other than this, I do not have this device at hand, so can't see what happens.
From the version number, I expect the firmware being HiSilicon (not Qualcomm).
Try also using dhcpcd if you can / want / like :) .
Thank you.
dhcpcd doesn’t work too.
I h
net-next v6 0/3] The huawei_cdc_ncm driver / E3276 problem
==
==Pasi Kärkkäinen writes:
==
==> # ifconfig wwp0s26u1u5i1
==> wwp0s26u1u5i1: flags=4163 mtu 1500
==> inet 10.8.219.204 netmask 255.255.255.248 broadcast 10.8.219.207
==> inet6 fe80::e5b:8fff:fe27:9a64
Pasi Kärkkäinen writes:
> # ifconfig wwp0s26u1u5i1
> wwp0s26u1u5i1: flags=4163 mtu 1500
> inet 10.8.219.204 netmask 255.255.255.248 broadcast 10.8.219.207
> inet6 fe80::e5b:8fff:fe27:9a64 prefixlen 64 scopeid 0x20
> ether 0c:5b:8f:27:9a:64 txqueuelen 1000 (Ethernet)
rnel.org, Enrico Mioso ,
==Oliver Neukum
==Subject: Re: [PATCH net-next v6 0/3] The huawei_cdc_ncm driver / E3276 problem
==
==On Fri, Mar 14, 2014 at 09:58:43AM +0100, Bjørn Mork wrote:
==> Pasi Kärkkäinen writes:
==>
==> > ^NDISSTAT:1,,,"IPV4"
==> > ^RSSI: 2
On Fri, Mar 14, 2014 at 09:58:43AM +0100, Bjørn Mork wrote:
> Pasi Kärkkäinen writes:
>
> > ^NDISSTAT:1,,,"IPV4"
> > ^RSSI: 21
> >
> >
> > ^DHCP: CCDB080A,F8FF,C9DB080A,C9DB080A,E67B59C0,E77B59C0,85600,85600
>
>
> The hex numbers are IPv4 addresses in little endian. The decimal numbers
> a
Pasi Kärkkäinen writes:
> ^NDISSTAT:1,,,"IPV4"
> ^RSSI: 21
>
>
> ^DHCP: CCDB080A,F8FF,C9DB080A,C9DB080A,E67B59C0,E77B59C0,85600,85600
The hex numbers are IPv4 addresses in little endian. The decimal numbers
at the end are speed down/up IIRC.
Printed in a more readable form, this is:
10
On Fri, Mar 14, 2014 at 09:34:39AM +0100, Bjørn Mork wrote:
> Pasi Kärkkäinen writes:
> > On Fri, Mar 14, 2014 at 12:08:12AM +0200, Pasi Kärkkäinen wrote:
> >>
> >> I've been using:
> >>
> >> ATQ0 V1 E1 S0=0
> >> AT^NDISDUP=1,1,"internet"
> >> AT^DHCP?
> >>
> >
> > Oh, I forgot to mention.. after
Pasi Kärkkäinen writes:
> On Fri, Mar 14, 2014 at 12:08:12AM +0200, Pasi Kärkkäinen wrote:
>>
>> I've been using:
>>
>> ATQ0 V1 E1 S0=0
>> AT^NDISDUP=1,1,"internet"
>> AT^DHCP?
>>
>
> Oh, I forgot to mention.. after I send AT^NDISDUP=1,1,"internet" I get this:
>
> ^NDISSTAT:1,,,"IPV4"
>
> .. whic
On Fri, Mar 14, 2014 at 08:58:03AM +0100, Mrkiko Rs wrote:
> Which dhcp client are you using?
>
"dhclient" in fedora 20..
-- Pasi
> Inviato da iPhone
>
> > Il giorno 14/mar/2014, alle ore 08:55, "Pasi Kärkkäinen" ha
> > scritto:
> >
> >> On Fri, Mar 14, 2014 at 12:08:12AM +0200, Pasi Kärkkä
Which dhcp client are you using?
Inviato da iPhone
> Il giorno 14/mar/2014, alle ore 08:55, "Pasi Kärkkäinen" ha
> scritto:
>
>> On Fri, Mar 14, 2014 at 12:08:12AM +0200, Pasi Kärkkäinen wrote:
>>> On Thu, Mar 13, 2014 at 04:41:47PM -0500, Dan Williams wrote:
On Thu, 2014-03-13 at 22:25 +0
On Fri, Mar 14, 2014 at 12:08:12AM +0200, Pasi Kärkkäinen wrote:
> On Thu, Mar 13, 2014 at 04:41:47PM -0500, Dan Williams wrote:
> > On Thu, 2014-03-13 at 22:25 +0200, Pasi Kärkkäinen wrote:
> > > On Mon, Nov 04, 2013 at 09:50:46AM +0100, Bjørn Mork wrote:
> > > >
> > > > [quote Enrico Mioso]
> >
On Thu, Mar 13, 2014 at 04:41:47PM -0500, Dan Williams wrote:
> On Thu, 2014-03-13 at 22:25 +0200, Pasi Kärkkäinen wrote:
> > On Mon, Nov 04, 2013 at 09:50:46AM +0100, Bjørn Mork wrote:
> > >
> > > [quote Enrico Mioso]
> > >
> > > So this is a new, revised, edition of the huawei_cdc_ncm.c driver,
On Thu, 2014-03-13 at 22:25 +0200, Pasi Kärkkäinen wrote:
> On Mon, Nov 04, 2013 at 09:50:46AM +0100, Bjørn Mork wrote:
> >
> > [quote Enrico Mioso]
> >
> > So this is a new, revised, edition of the huawei_cdc_ncm.c driver, which
> > supports devices resembling the NCM standard, but using it als
On Mon, Nov 04, 2013 at 09:50:46AM +0100, Bjørn Mork wrote:
>
> [quote Enrico Mioso]
>
> So this is a new, revised, edition of the huawei_cdc_ncm.c driver, which
> supports devices resembling the NCM standard, but using it also as a mean
> to encapsulate other protocols, as is the case for the
From: Bjørn Mork
Date: Mon, 4 Nov 2013 09:50:46 +0100
> Enrico has been kind enough to let me repost his driver with the changes
> requested by Oliver Neukum during the last review of this series.
>
> The changes I have made from Enricos original v5 series to this version
> are:
>
> v6:
> - f
31 matches
Mail list logo
