From: Enrico Mioso <mrkiko.rs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Oliver Neukum <oneukum-l3A5Bk7waGM@public.gmane.org>
Cc: youtux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [cdc_ncm] guidance and help refactoring cdc_ncm
Date: Mon, 1 Jun 2015 13:41:34 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.20.1506011319330.4326@localhost.localdomain> (raw)
In-Reply-To: <1433155778.1884.12.camel-l3A5Bk7waGM@public.gmane.org>
Thank you Oliver, thank you all for reading this thread and the attention.
For a more detailed discussion and how we got here, you might google for the
thread:
"Is this 32-bit NCM?"
and
"Is this 32-bit NCM?y" (follow up).
Where the "y" letter comes from a mistake of mine.
The specification does only mandate the position of the NTH (header). The rest
can be in any order and position in general. This will work with most devices:
except, of course, those from Huawei.
Our aggregate looks something like this from my perspective (anyone correct me
in case):
NTH: header
NDP: contains indexing informations
ethernet packet 1
ethernet packet 2
...
ethernet packet n;
While it should look like:
NTH: header
ethernet packet 1
ethernet packet 2
...
ethernet packet n;
NDP: contains indexing informations
but, when introducing such a change: you might break other devices now working.
Infact, clearly there are multiple vendors producing NCM device, as you might
also see by looking at the dirver's comments.
So in general, we should be able to dynamically change the way in which the
driver order things in the package.
and that's why I initially proposed the "redesign".
thank you guys, for the patience and time.
Enrico
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-06-01 11:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-31 14:37 [cdc_ncm] guidance and help refactoring cdc_ncm Enrico Mioso
[not found] ` <alpine.LNX.2.20.1505311628420.16456-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2015-06-01 0:59 ` Greg KH
[not found] ` <20150601005917.GB5320-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-06-01 6:53 ` Enrico Mioso
[not found] ` <alpine.LNX.2.20.1506010818110.3158-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2015-06-01 7:48 ` Oliver Neukum
[not found] ` <1433144906.1557.2.camel-IBi9RG/b67k@public.gmane.org>
2015-06-01 8:24 ` Enrico Mioso
2015-06-01 10:49 ` Oliver Neukum
[not found] ` <1433155778.1884.12.camel-l3A5Bk7waGM@public.gmane.org>
2015-06-01 11:41 ` Enrico Mioso [this message]
2015-06-01 12:00 ` Oliver Neukum
[not found] ` <1433160022.1884.18.camel-IBi9RG/b67k@public.gmane.org>
2015-06-01 12:08 ` Enrico Mioso
2015-06-02 5:46 ` [RFC cdc_ncm] introducing allocation mode 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.20.1506011319330.4326@localhost.localdomain \
--to=mrkiko.rs-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=oneukum-l3A5Bk7waGM@public.gmane.org \
--cc=youtux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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).