• Home
  • History
  • Annotate
  • only in this directory
NameDateSize

..11-May-201459

KconfigH A D11-May-20141.1 KiB

MakefileH A D11-May-2014450

READMEH A D11-May-20141.1 KiB

tm6000-alsa.cH A D11-May-201410.4 KiB

tm6000-cards.cH A D11-May-201425.1 KiB

tm6000-core.cH A D11-May-201423.4 KiB

tm6000-dvb.cH A D11-May-201410.5 KiB

tm6000-i2c.cH A D11-May-20148.9 KiB

tm6000-input.cH A D11-May-20148.5 KiB

tm6000-regs.hH A D11-May-201424.7 KiB

tm6000-stds.cH A D11-May-201430.3 KiB

tm6000-usb-isoc.hH A D11-May-20141.4 KiB

tm6000-video.cH A D11-May-201435.9 KiB

tm6000.hH A D11-May-20149.1 KiB

README

1Todo:
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
7	- Add vbi support
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
20	- sparse cleanups
21
22Please send patches to linux-media@vger.kernel.org
23