summaryrefslogtreecommitdiffstats
path: root/drivers/media/dvb/frontends/at76c651.h
diff options
context:
space:
mode:
authorRalf Baechle <ralf@linux-mips.org>2017-01-14 00:08:05 +0100
committerRalf Baechle <ralf@linux-mips.org>2019-04-03 00:05:23 +0200
commit8a2288f22b606904766f3cec13bbcc73d35aad87 (patch)
tree7726889af67cc77fa6085be8f67dd9c5afaf5558 /drivers/media/dvb/frontends/at76c651.h
parent9b128099c349842940822e95c4a5bcd00126c5ff (diff)
NET: ROSE: Convert ROSE device creation to netlink.
ROSE does not yet support configuration via netlink and the old ioctl way of doing things has its limitations as rose addresses are longer than eight bytes: # ifconfig rose0 hw rose 1234567890 # ifconfig rose0 rose0: flags=128<NOARP> mtu 249 rose 12345678ff txqueuelen 1 (AMPR ROSE) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 That is, ifconfig was returning an incorrect last byte of the address. Until now, ROSE did create a number of ROSE devices on initialization. The number could be set by the module parameter rose_ndevs and did default to 10 while typically only a single one would be used. With this applied a new version of ip from the iproute2 is required for ROSE device creation: # ip link add type rose This will create a ROSE device which will be named rose0 for the first device thus consistent with the old naming practice. Explicit naming is possible with # ip link add name pink17 type rose which will create a ROSE device named pink17. Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
Diffstat (limited to 'drivers/media/dvb/frontends/at76c651.h')
0 files changed, 0 insertions, 0 deletions