From: David Miller <davem@davemloft.net>
To: bay@hackerdom.ru
Cc: oliver@neukum.org, gregkh@linuxfoundation.org,
tglx@linutronix.de, info@metux.net, allison@lohutok.net,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cdc_ncm: Implement the 32-bit version of NCM Transfer Block
Date: Sun, 08 Mar 2020 22:04:03 -0700 (PDT) [thread overview]
Message-ID: <20200308.220403.2013988891795466479.davem@davemloft.net> (raw)
In-Reply-To: <20200305203318.8980-1-bay@hackerdom.ru>
From: Alexander Bersenev <bay@hackerdom.ru>
Date: Fri, 6 Mar 2020 01:33:16 +0500
> The NCM specification defines two formats of transfer blocks: with 16-bit
> fields (NTB-16) and with 32-bit fields (NTB-32). Currently only NTB-16 is
> implemented.
>
> This patch adds the support of NTB-32. The motivation behind this is that
> some devices such as E5785 or E5885 from the current generation of Huawei
> LTE routers do not support NTB-16. The previous generations of Huawei
> devices are also use NTB-32 by default.
>
> Also this patch enables NTB-32 by default for Huawei devices.
>
> During the 2019 ValdikSS made five attempts to contact Huawei to add the
> NTB-16 support to their router firmware, but they were unsuccessful.
>
> Signed-off-by: Alexander Bersenev <bay@hackerdom.ru>
Oliver et al., please review.
Thank you.
next prev parent reply other threads:[~2020-03-09 5:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 20:33 [PATCH] cdc_ncm: Implement the 32-bit version of NCM Transfer Block Alexander Bersenev
2020-03-09 5:04 ` David Miller [this message]
2020-03-09 10:17 ` Oliver Neukum
[not found] ` <CAPomEdycThBH5D3Eo3dNCPRrEg0W2fQ9JS9j6TbANTDVChVcog@mail.gmail.com>
2020-03-10 14:17 ` Fwd: " Александр Берсенев
2020-03-10 14:24 ` Александр Берсенев
2020-03-12 5:59 ` David Miller
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200308.220403.2013988891795466479.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=allison@lohutok.net \
--cc=bay@hackerdom.ru \
--cc=gregkh@linuxfoundation.org \
--cc=info@metux.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).