[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_Kpj3tT6qfcD-Tpeqgof-k-PX-EPv_cMFo_NeEdLHfyN8Qfw@mail.gmail.com>
Date: Fri, 19 Oct 2012 15:53:05 +0200
From: Alexey Orishko <alexey.orishko@...il.com>
To: Bjørn Mork <bjorn@...k.no>
Cc: Oliver Neukum <oliver@...kum.org>, netdev@...r.kernel.org,
linux-usb@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Greg Suarez <gpsuarez2512@...il.com>,
"Fangxiaozhi (Franko)" <fangxiaozhi@...wei.com>,
Dan Williams <dcbw@...hat.com>,
Aleksander Morgado <aleksander@...edo.com>
Subject: Re: [PATCH net-next 02/14] net: cdc_ncm: use device rx_max value if
update failed
On Fri, Oct 19, 2012 at 2:18 PM, Bjørn Mork <bjorn@...k.no> wrote:
>
> OK, I may have misunderstood you here. Quoting the errata text:
>
> <quote>
> If bit D5 is set in the bmNetworkCapabilities field of function’s NCM
> Functional Descriptor, the host may set wLength either to 4 or to
> 8. If wLength is 4, the function shall assume that wNtbInMaxDatagrams
> is to be set to zero. If wLength is 8, then the function shall use the
> provided value as the limit. The function shall return an error
> response (a STALL PID) if wLength is set to any other value.
> </quote>
>
> So the 4 byte variant is always supported and we might as well just use
> it unconditionally because we don't set, or need to set, the
> wNtbInMaxDatagrams.
>
> Is that right? It will simplify the code even more without any loss of
> functionality, except for the possibility of failing on some other buggy
> device not supporting the 4 byte variant...
Agree, since 4-byte version must be supported by all devices,
we can drop 8-byte variant
/alexey
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists