kernel-ark/drivers/staging/tm6000
Stefan Ringel 1b376dac05 V4L/DVB: tm6000: bugfix data handling
Signed-off-by: Stefan Ringel <stefan.ringel@arcor.de>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2010-09-27 22:22:02 -03:00
..
Kconfig V4L/DVB: tm6000: depends on IR_CORE 2010-09-27 22:21:43 -03:00
Makefile V4L/DVB: tm6000: add ir support 2010-08-02 15:29:31 -03:00
README V4L/DVB: tm6000: README - add vbi 2010-05-19 12:59:16 -03:00
tm6000-alsa.c V4L/DVB: tm6000: Improve set bitrate routines used by alsa 2010-08-02 14:05:58 -03:00
tm6000-cards.c V4L/DVB: tm6000: add ir support 2010-08-02 15:29:31 -03:00
tm6000-core.c V4L/DVB: tm6000: Improve set bitrate routines used by alsa 2010-08-02 14:05:58 -03:00
tm6000-dvb.c V4L/DVB: tm6000: Use an enum for extension type 2010-08-02 14:05:52 -03:00
tm6000-i2c.c V4L/DVB: Staging: tm6000: Fix coding style issues 2010-08-02 14:05:44 -03:00
tm6000-input.c V4L/DVB: tm6000: bugfix data handling 2010-09-27 22:22:02 -03:00
tm6000-regs.h V4L/DVB: tm6000: add request to registers of the group 05 2010-05-18 00:47:11 -03:00
tm6000-stds.c V4L/DVB: Staging: tm6000: Fix coding style issues 2010-08-02 14:05:44 -03:00
tm6000-usb-isoc.h V4L/DVB: tm6000: rewrite copy_streams 2010-08-02 14:05:40 -03:00
tm6000-video.c V4L/DVB: tm6000: Partially revert some copybuf logic 2010-08-02 14:06:02 -03:00
tm6000.h V4L/DVB: tm6000: add ir support 2010-08-02 15:29:31 -03:00

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 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 linux-media@vger.kernel.org