kernel-fxtec-pro1x/drivers/staging/tm6000
Tejun Heo 4ef09889d7 v4l-dvb: update gfp/slab.h includes
Implicit slab.h inclusion via percpu.h is about to go away.  Make sure
gfp.h or slab.h is included as necessary.

Signed-off-by: Tejun Heo <tj@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
2010-06-28 10:19:18 +10:00
..
Kconfig V4L/DVB: tm6000: Properly select the tuners 2010-06-01 01:22:05 -03:00
Makefile V4L/DVB: tm6000: remove hack.c hack.h, switch to zl10353 module 2010-05-18 00:44:05 -03:00
README V4L/DVB: tm6000: README - add vbi 2010-05-19 12:59:16 -03:00
tm6000-alsa.c v4l-dvb: update gfp/slab.h includes 2010-06-28 10:19:18 +10:00
tm6000-cards.c v4l-dvb: update gfp/slab.h includes 2010-06-28 10:19:18 +10:00
tm6000-core.c v4l-dvb: update gfp/slab.h includes 2010-06-28 10:19:18 +10:00
tm6000-dvb.c v4l-dvb: update gfp/slab.h includes 2010-06-28 10:19:18 +10:00
tm6000-i2c.c V4L/DVB: tm6000: fix i2c read 2010-05-19 12:58:17 -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: tm6000: Replace all magic values by a register alias 2010-05-18 00:47:09 -03:00
tm6000-usb-isoc.h V4L/DVB: tm6000: fix some info messages 2010-05-18 00:44:07 -03:00
tm6000-video.c V4L/DVB: tm6000: bugfix stabilizing urb data 2010-06-01 01:22:02 -03:00
tm6000.h V4L/DVB: tm6000, reset I2C bus function 2010-06-01 01:21:57 -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