summaryrefslogtreecommitdiffstats
path: root/arch/arm64/include/asm/mmu.h
diff options
context:
space:
mode:
authorChristoph Nuscheler <christoph.nuscheler@t-online.de>2013-02-09 15:56:23 -0300
committerMauro Carvalho Chehab <mchehab@redhat.com>2013-02-13 18:05:29 -0200
commited72d37a33fdf43dc47787fe220532cdec9da528 (patch)
tree8adf78a59864771fd6443360bb262461e1f0e43d /arch/arm64/include/asm/mmu.h
parentb9e2afff1e6b36d05a0e12b6114eb0aaf8949c09 (diff)
downloadop-kernel-dev-ed72d37a33fdf43dc47787fe220532cdec9da528.zip
op-kernel-dev-ed72d37a33fdf43dc47787fe220532cdec9da528.tar.gz
[media] media: Add 0x3009 USB PID to ttusb2 driver (fixed diff)
The "Technisat SkyStar USB plus" is a TT-connect S-2400 clone, which the V4L-DVB drivers already support. However, some of these devices (like mine) come with a different USB PID 0x3009 instead of 0x3006. There have already been patches simply overwriting the USB PID in dvb-usb-ids.h. Of course these patches were rejected because they would have disabled the 0x3006 PID. This new patch adds the 0x3009 PID to dvb-usb-ids.h, and adds references to it within the ttusb2.c driver. PID 0x3006 devices will continue to work. The only difference between the two hardware models seems to be the EEPROM chip. In fact, Windows BDA driver names the 0x3009 device with a "(8 kB EEPROM)" suffix. In spite of that, the 0x3009 device works absolutely flawlessly using the existing ttusb2 driver. Signed-off-by: Christoph Nuscheler <christoph.nuscheler@t-online.de> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'arch/arm64/include/asm/mmu.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud