Bjørn Mork wrote:
> +++ b/Documentation/ABI/testing/sysfs-class-net-cdc_ncm
> @@ -0,0 +1,143 @@
> +What: /sys/class/net/<iface>/cdc_ncm/min_tx_pkt
> +Date: May 2014
> +KernelVersion: 3.16
> +Contact: Bjørn Mork <bj...@mork.no>
> +Description:
> + The driver will pad frames longer than this to tx_max,
^^^^^^
longer or shorter?
> +What: /sys/class/net/<iface>/cdc_ncm/rx_max
> +Date: May 2014
> +KernelVersion: 3.16
> +Contact: Bjørn Mork <bj...@mork.no>
> +Description:
> + The maximum NCM Transfer Block (NTB) size for RX.
> + Cannot exceed the maximum value supported by the
> + device. Must allow at least one max sized datagram
> + plus headers.
> +
> + The actual limits are device dependent. See
> + dwNtbInMaxSize.
> +
> + Note: Some devices will silently ignore changes to
> + this value, resulting in oversized NTBs and
> + corresponding framing errors.
That behavior makes the setting only so-so useful. Could the driver
know which devices do this, or is it inconsistent even across
individual devices which are otherwise indistinguishable?
> +What: /sys/class/net/<iface>/cdc_ncm/tx_timer_usecs
> +Date: May 2014
> +KernelVersion: 3.16
> +Contact: Bjørn Mork <bj...@mork.no>
> +Description:
> + Datagram aggregation timeout in µs. The driver will
> + wait up to 3 times this timeout for more datagrams to
> + aggregate before transmitting a NTB frame.
^
"an NTB frame" might be better since N sounds like "enn".
> +
> + Valid range: 5 to 4000000
> +
> + Set to 0 to disable aggregation.
> +
> +The following read only attributes all represent fields of the
read-only?
//Peter
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
