summaryrefslogtreecommitdiffstats
path: root/drivers/media/video/cx231xx/Makefile
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab@redhat.com>2010-09-03 15:50:24 +0200
committerMauro Carvalho Chehab <mchehab@redhat.com>2010-09-28 03:21:52 +0200
commit3bfb317f97cfddbbec67bbe8e35ad38af3507397 (patch)
treef855bf32a53b9e8a0b3004deaa79ae9d60f47ca4 /drivers/media/video/cx231xx/Makefile
parentV4L/DVB: mceusb: add two new ASUS device IDs (diff)
downloadlinux-3bfb317f97cfddbbec67bbe8e35ad38af3507397.tar.xz
linux-3bfb317f97cfddbbec67bbe8e35ad38af3507397.zip
V4L/DVB: Don't identify PV SBTVD Hybrid as a DibCom device
As reported by Carlos, Prolink Pixelview SBTVD Hybrid is based on Conexant cx231xx + Fujitsu 86A20S demodulator. However, both shares the same USB ID. So, we need to use USB bcdDevice, in order to properly discover what's the board. We know for sure that bcd 0x100 is used for a dib0700 device, while bcd 0x4001 is used for a cx23102 device. This patch reserves two ranges, the first one from 0x0000-0x3f00 for dib0700, and the second from 0x4000-0x4fff for cx231xx devices. This may need fixes in the future, as we get access to other devices. Thanks-to: Carlos Americo Domiciano <c_domiciano@yahoo.com.br> Cc: stable@kernel.org Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'drivers/media/video/cx231xx/Makefile')
-rw-r--r--drivers/media/video/cx231xx/Makefile1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/media/video/cx231xx/Makefile b/drivers/media/video/cx231xx/Makefile
index 755dd0ce65ff..6f2b57384488 100644
--- a/drivers/media/video/cx231xx/Makefile
+++ b/drivers/media/video/cx231xx/Makefile
@@ -11,4 +11,5 @@ EXTRA_CFLAGS += -Idrivers/media/video
EXTRA_CFLAGS += -Idrivers/media/common/tuners
EXTRA_CFLAGS += -Idrivers/media/dvb/dvb-core
EXTRA_CFLAGS += -Idrivers/media/dvb/frontends
+EXTRA_CFLAGS += -Idrivers/media/dvb/dvb-usb