[net-next-2.6.git] / drivers / staging / tm6000 / README

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
Commit	Line	Data
77d966a2	1	Todo:
6bc4631d MCC	2	- Fix the loss of some blocks when receiving the video URB's
	3	- Add a lock at tm6000_read_write_usb() to prevent two simultaneous access to the
	4	URB control transfers
	5	- Properly add the locks at tm6000-video
	6	- Add audio support
9986da29	7	- Add vbi support
6bc4631d MCC	8	- Add IR support
	9	- Do several cleanups
	10	- I think that frame1/frame0 are inverted. This causes a funny effect at the image.
	11	the fix is trivial, but require some tests
	12	- My tm6010 devices sometimes insist on stop working. I need to turn them off, removing
	13	from my machine and wait for a while for it to work again. I'm starting to think that
	14	it is an overheat issue - is there a workaround that we could do?
	15	- Sometimes, tm6010 doesn't read eeprom at the proper time (hardware bug). So, the device
	16	got miss-detected as a "generic" tm6000. This can be really bad if the tuner is the
	17	Low Power one, as it may result on loading the high power firmware, that could damage
	18	the device. Maybe we may read eeprom to double check, when the device is marked as "generic"
	19	- Coding Style fixes
77d966a2	20	- sparse cleanups
77d966a2 MCC	21
77d966a2 MCC	22	Please send patches to linux-media@vger.kernel.org