Re: [RFC 2/3] if_ether.h: Add IEEE 802.1 Local Experimental Ethertype 1.

[RFC 0/3] caif: Add support for CAIF over CDC NCM USB interface · Sjur Br��ndeland <hidden> · 2011-11-30
[RFC 1/3] caif: Add support for flow-control on device's tx-queue · Sjur Br��ndeland <hidden> · 2011-11-30
[RFC 2/3] if_ether.h: Add IEEE 802.1 Local Experimental Ethertype 1. · Sjur Br��ndeland <hidden> · 2011-11-30
Re: [RFC 2/3] if_ether.h: Add IEEE 802.1 Local Experimental Ethertype 1. · Rémi Denis-Courmont <hidden> · 2011-12-01
Re: [RFC 2/3] if_ether.h: Add IEEE 802.1 Local Experimental Ethertype 1. · Sjur Brændeland <hidden> · 2011-12-05
Re: [RFC 2/3] if_ether.h: Add IEEE 802.1 Local Experimental Ethertype 1. · Rémi Denis-Courmont <hidden> · 2011-12-05
Re: [RFC 2/3] if_ether.h: Add IEEE 802.1 Local Experimental Ethertype 1. · Sjur Brændeland <hidden> · 2011-12-05
Re: [RFC 2/3] if_ether.h: Add IEEE 802.1 Local Experimental Ethertype 1. · Rémi Denis-Courmont <hidden> · 2011-12-05
[RFC 3/3] caif: Add support for CAIF over CDC NCM USB interface · Sjur Br��ndeland <hidden> · 2011-11-30

From: Sjur Brændeland <hidden>
Date: 2011-12-05 14:33:51

Hi Rémi,

It's even weirder then. If you have control over both ends and the NCM 1.0
interface is not adequate, then you really should use your own CDC class
for the purpose.

The reason we use NCM is performance: CDC normally gives less than 100Mbps,
while NCM can give you up to 200Mbps.

Regards,
Sjur

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help