aboutsummaryrefslogtreecommitdiff
path: root/drivers/staging
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab@redhat.com>2010-05-03 04:38:15 -0300
committerMauro Carvalho Chehab <mchehab@redhat.com>2010-05-19 12:58:22 -0300
commit6bc4631dbc535a906193fe8110556bf84e1786e3 (patch)
treeb3ff322631470e252f9fb96ada571b8a77d98b3c /drivers/staging
parent4223871357a2b64248b3c41c8d89fbf03c2531ea (diff)
V4L/DVB: tm6000: update the todo list
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'drivers/staging')
-rw-r--r--drivers/staging/tm6000/README24
1 files changed, 17 insertions, 7 deletions
diff --git a/drivers/staging/tm6000/README b/drivers/staging/tm6000/README
index cff09b7b477..078e803e47b 100644
--- a/drivers/staging/tm6000/README
+++ b/drivers/staging/tm6000/README
@@ -1,11 +1,21 @@
Todo:
- - checkpatch.pl cleanups
+ - 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 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
- - convert to new i2c approach
- - better support DVB
- - fix reading from i2c, if possible
- - fix loosing frames
- - fix oops?
Please send patches to linux-media@vger.kernel.org
-