[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87d2ewbejv.fsf@nemi.mork.no>
Date: Thu, 29 May 2014 20:55:16 +0200
From: Bjørn Mork <bjorn@...k.no>
To: Jim Baxter <jim_baxter@...tor.com>
Cc: Felipe Balbi <balbi@...com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
<linux-usb@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Eric Dumazet <eric.dumazet@...il.com>,
David Laight <David.Laight@...LAB.COM>,
<netdev@...r.kernel.org>
Subject: Re: [PATCH v1 1/3] usb: gadget: NCM: RX function support multiple NDPs
Jim Baxter <jim_baxter@...tor.com> writes:
> The NDP was ignoring the wNextNdpIndex in the NDP which
> means that NTBs containing multiple NDPs would have missed
> frames.
Well, just for the record: I believe this field was meant to be reserved
and always 0 in the CDC NCM spec. Table 3-3, describing 16bit NDPs,
says so. But reading the spec now, I noticed that there is an
inconsistency between table 3-3 and table 3-4 describing 32bit NDPs. It
looks like the field is not reserved in the 32bit version.
I am pretty sure that is a specification error, but I guess it doesn't
harm to implement the support anyway. And it paves the way for an MBIM
gadget :-)
Bjørn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists