summaryrefslogtreecommitdiffstats
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorStefan Richter <stefanr@s5r6.in-berlin.de>2009-01-04 16:23:29 +0100
committerStefan Richter <stefanr@s5r6.in-berlin.de>2009-03-24 20:56:44 +0100
commit33580a3ef5ba3bc0ee1b520df82a24bb37ce28f0 (patch)
tree3bd567d8c5244a049eef32147f4fb84f6a19a184 /MAINTAINERS
parent1ec3c0269d7196118cc7c403654ca5f19ef4d584 (diff)
downloadkernel-crypto-33580a3ef5ba3bc0ee1b520df82a24bb37ce28f0.tar.gz
kernel-crypto-33580a3ef5ba3bc0ee1b520df82a24bb37ce28f0.tar.xz
kernel-crypto-33580a3ef5ba3bc0ee1b520df82a24bb37ce28f0.zip
firewire: cdev: add ioctl to query maximum transmission speed
While the speed of asynchronous transactions is automatically chosen by the kernel, the speed of isochronous streams has to be chosen by the initiating client. In case of 1394a bus topologies, the maximum possible speed could be figured out with some effort by evaluation of the remote node's link speed field in the config ROM, the local node's link speed field, and the PHY speeds and topologic information in the local node's or IRM's topology map CSR. However, this does not work in case of 1394b buses. Hence add an ioctl to export the maximum speed which the kernel already determined. Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions