From: Greg KH <gregkh@linuxfoundation.org>
To: "Ruinskiy, Dima" <dima.ruinskiy@intel.com>
Cc: "Oliver Neukum" <oliver@neukum.org>,
"Oliver Neukum" <oneukum@suse.com>,
"Maciej Żenczykowski" <maze@google.com>,
"Terry Moore" <tmm@mcci.com>,
linux-usb@vger.kernel.org
Subject: Re: cdc_ncm driver and NCM 1.1 revision
Date: Wed, 22 Oct 2025 14:28:31 +0200 [thread overview]
Message-ID: <2025102259-purebred-amulet-b6d2@gregkh> (raw)
In-Reply-To: <6c22b4d5-7d6d-41ab-9b00-9dccf3ec8963@intel.com>
On Wed, Oct 22, 2025 at 03:18:07PM +0300, Ruinskiy, Dima wrote:
> Hi Oliver, how are you?
>
> You are listed at the maintainer for the cdc_ncm and usbnet Linux drivers.
>
> The cdc_ncm driver has only had a handful of changes in recent years, as the
> spec too has not been updated for some time.
>
> Recently, the USB NCM workgroup has finished and published a major revision
> to the spec - NCM 1.1 - with several new features as well as data path
> updates.
>
> The new revision is available here:
> https://www.usb.org/document-library/usb-communications-class-subclass-specifications-network-control-model-devices-v11
>
> An "executive summary" is here:
> https://www.linkedin.com/posts/mcci-corporation_usb-if-compliance-workshop-139-activity-7335815355266719744-BAdf/
>
> There are on-going initiatives to update the Windows and MacOS NCM drivers
> to support the new 1.1 features.
>
> Do you know of any plans to update the Linux driver as well? I expect there
> will be some inquiries as soon as the first NCM1.1-capable devices appear,
> which may happen already next year.
Patches are always gladly accepted to add new support like this, thanks! :)
greg k-h
next prev parent reply other threads:[~2025-10-22 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 12:18 cdc_ncm driver and NCM 1.1 revision Ruinskiy, Dima
2025-10-22 12:28 ` Greg KH [this message]
2025-10-22 14:38 ` Terry Moore
2025-10-22 14:50 ` 'Greg KH'
2025-10-22 18:24 ` Terry Moore
2025-10-22 18:33 ` Oliver Neukum
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=2025102259-purebred-amulet-b6d2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dima.ruinskiy@intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=maze@google.com \
--cc=oliver@neukum.org \
--cc=oneukum@suse.com \
--cc=tmm@mcci.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