Commit be304970 authored by Mauro Carvalho Chehab's avatar Mauro Carvalho Chehab
Browse files

[media] move tm6000 to drivers/media/video

The serious bugs got fixed already.

Signed-off-by: default avatarMauro Carvalho Chehab <>
parent 45dbf0db
......@@ -1019,6 +1019,8 @@ source "drivers/media/video/tlg2300/Kconfig"
source "drivers/media/video/cx231xx/Kconfig"
source "drivers/media/video/tm6000/Kconfig"
source "drivers/media/video/usbvision/Kconfig"
source "drivers/media/video/et61x251/Kconfig"
......@@ -107,6 +107,7 @@ obj-$(CONFIG_VIDEO_CX231XX) += cx231xx/
obj-$(CONFIG_VIDEO_USBVISION) += usbvision/
obj-$(CONFIG_VIDEO_PVRUSB2) += pvrusb2/
obj-$(CONFIG_VIDEO_CPIA2) += cpia2/
obj-$(CONFIG_VIDEO_TM6000) += tm6000/
obj-$(CONFIG_VIDEO_MXB) += mxb.o
obj-$(CONFIG_VIDEO_HEXIUM_ORION) += hexium_orion.o
obj-$(CONFIG_VIDEO_HEXIUM_GEMINI) += hexium_gemini.o
......@@ -32,8 +32,6 @@ source "drivers/staging/go7007/Kconfig"
source "drivers/staging/cx25821/Kconfig"
source "drivers/staging/tm6000/Kconfig"
source "drivers/staging/cxd2099/Kconfig"
source "drivers/staging/usbip/Kconfig"
......@@ -7,7 +7,6 @@ obj-$(CONFIG_ET131X) += et131x/
obj-$(CONFIG_SLICOSS) += slicoss/
obj-$(CONFIG_VIDEO_GO7007) += go7007/
obj-$(CONFIG_VIDEO_CX25821) += cx25821/
obj-$(CONFIG_VIDEO_TM6000) += tm6000/
obj-$(CONFIG_DVB_CXD2099) += cxd2099/
obj-$(CONFIG_LIRC_STAGING) += lirc/
obj-$(CONFIG_USBIP_CORE) += usbip/
- Fix the loss of some blocks when receiving the video URB's
- Add a lock at tm6000_read_write_usb() to prevent two simultaneous access to the
URB control transfers
- Properly add the locks at tm6000-video
- Add audio support
- Add vbi support
- Add IR support
- Do several cleanups
- I think that frame1/frame0 are inverted. This causes a funny effect at the image.
the fix is trivial, but require some tests
- My tm6010 devices sometimes insist on stop working. I need to turn them off, removing
from my machine and wait for a while for it to work again. I'm starting to think that
it is an overheat issue - is there a workaround that we could do?
- Sometimes, tm6010 doesn't read eeprom at the proper time (hardware bug). So, the device
got miss-detected as a "generic" tm6000. This can be really bad if the tuner is the
Low Power one, as it may result on loading the high power firmware, that could damage
the device. Maybe we may read eeprom to double check, when the device is marked as "generic"
- Coding Style fixes
- sparse cleanups
Please send patches to
There a few things to do before putting this driver in production:
- IR NEC with tm5600/6000 TV cards
- IR RC5 with tm5600/6000/6010 TV cards
- CodingStyle;
- Fix audio;
- Fix some panic/OOPS conditions.
Please send patches to
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment