From: Dave Taht <dave.taht@gmail.com>
To: Enrico Mioso <mrkiko.rs@gmail.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [discuss] [cdc_ncm] Refactoring cdc_ncm
Date: Mon, 19 Jan 2015 09:47:23 -0800 [thread overview]
Message-ID: <CAA93jw4SZ=j6WQ69Z7SdCQEDsQjDYvHHgt3QPYCcYWoEC4mwQQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.03.1501191743360.2081@gmail.com>
I would like to see folk poking to bufferbloat on LTE, and this looks
like a decent/chip and driver to fiddle with.
Is anyone here using that device? I am under the impression you can
only order them from overseas...
On Mon, Jan 19, 2015 at 8:51 AM, Enrico Mioso <mrkiko.rs@gmail.com> wrote:
> Hi guys.
> I am noticing that in kernel 3.19rc4, the driver from huawei,
> hw_cdc_driver
> is not able to perform the call to
> netif_msg_ifup anymore (receives error -13).
> This to say that it would be very important to continue the work on
> refactoring cdc_ncm.c driver to let it work with newer huawei devices such
> as the E3372 even at full rates.
> I received some acks regarding the patches I sent last time - and I am
> grateful to you all maintainers / reviewers. I have actually not received
> acks for all the patches so I preferred waiting and not continously
> re-sending again.
> This also happened due to me getting very busy lately with studying.
> So the situation is getting complicated.
> I sent this mail to everyone just to keep you up-to-date. Don't worry.
> Any help from any developer interested would be very apreciated.
> I would need some mentoring or help in general with coding.
>
> Thank you all very much.
>
> Sincerely.
>
> Enrico
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Dave Täht
thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
next parent reply other threads:[~2015-01-19 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AMSPR06MB6011E001029C251790CB923EE780@AMSPR06MB601.eurprd06.prod.outlook.com>
[not found] ` <877fy7myfb.fsf@nemi.mork.no>
[not found] ` <alpine.LNX.2.03.1412041326160.9926@gmail.com>
[not found] ` <54811670.5030703@audiocodes.com>
[not found] ` <8761dqjuuh.fsf@nemi.mork.no>
[not found] ` <alpine.LNX.2.03.1501191743360.2081@gmail.com>
2015-01-19 17:47 ` Dave Taht [this message]
2015-01-19 18:28 ` Enrico Mioso
2015-01-20 16:13 ` Valdis.Kletnieks
2015-01-20 18:21 ` Enrico Mioso
2015-01-20 19:54 ` Enrico Mioso
2015-01-20 21:25 ` Enrico Mioso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4SZ=j6WQ69Z7SdCQEDsQjDYvHHgt3QPYCcYWoEC4mwQQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=mrkiko.rs@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox