5a11b6fe5d
Randy Dunlap <randy.dunlap@oracle.com> reported a breakage while compiling drivers/staging/tm6000, due to this change: commit 1c1b78bee1a94f98deeb9c24b21c4812e191646c Author: Greg Kroah-Hartman <gregkh@suse.de> Date: Thu Apr 29 15:46:07 2010 -0700 USB: remove unused usb_buffer_alloc and usb_buffer_free macros Now that all callers are converted over, remove the compatibility functions and all is good. As the function got renamed, the rename should also be applied at tm6000. Acked-by: Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com> |
||
---|---|---|
.. | ||
Kconfig | ||
Makefile | ||
README | ||
tm6000-alsa.c | ||
tm6000-cards.c | ||
tm6000-core.c | ||
tm6000-dvb.c | ||
tm6000-i2c.c | ||
tm6000-regs.h | ||
tm6000-stds.c | ||
tm6000-usb-isoc.h | ||
tm6000-video.c | ||
tm6000.h |
Todo: - 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 Please send patches to linux-media@vger.kernel.org