mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-28 07:04:00 +08:00
94d4350c54
I added a code to the driver to force it to produce a warning. This were intended to remind me about a very bad hack. I never found a way to workaround. So, instead of those warnings: drivers/staging/tm6000/tm6000-core.c: In function ‘tm6000_init_analog_mode’: drivers/staging/tm6000/tm6000-core.c:328: warning: ISO C90 forbids mixed declarations and code Let's document the issue and hope if someone with the support of the vendor might fix it. 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-input.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 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