Skip to contentSkip to conversation

tm6010 status

DISCUSSION matthieu castet 2 participants 3 messages Oct 4, 2009 – Oct 5, 2009 1 message not in the archive Media (V4L/DVB)

lore
Share & tools
lore
#1 lore raw
Quoted 14 lines · matthieu castet

Hi,

what's the status of tm6010 support ?

http://www.mail-archive.com/[email protected]/msg04048.html announced some patches, but nothing seems to have happened ?

Matthieu

Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Mauro has it on his TODO list:

http://www.mail-archive.com/[email protected]/msg08770.html

I'm not spending any time on this at the moment, and probably won't in the future. I spent some time reading the code for the existing driver and submitted a few trivial patches, and quite a bit of time with a USB sniffer to try and determine where the Linux and Windows XP driver behaved differently. But I have subsequently purchased an Asus My-Cinema U3100 Mini (DVB-T only) that is cheap and worked out of the box on Ubuntu. So I no longer have much motivation to work on this.

I was surprised to find that data sheets are difficult to obtain for the tm6010, and for a lot of other chips used in TV devices as well. Why? I thought these companies made money by selling chips in significant volume rather than by selling development kits. So surely they would sell more chips by making documentation available to anyone who wants to support their products. If there are trade secrets they are trying to protect surely these are in the hardware and firmware rather than the driver and the protocols used to communicate with the hardware. Perhaps someone on this list can explain how this makes business sense.

So it seems it is common practice to use reverse engineering to get drivers working. This is a lot of work and makes me really appreciate the work that has been put in by v4l developers.

Kevin Wells

author
#3 lore raw
In reply to a message not in the archive

Hi,

Quoted 6 lines · Dênis Goes

Hi Matthieu...
I made the same answer yesterday... I want to help in development for use my PixelView 405 USB.

Do you have the correct tridvid.sys file to extract the firmware ?

No, I took the firmware (for the tuner) somewhere on internet.

Some time ago I have done some usb sniffing on Windows for my HVR900H, study the linux driver and start some analysis [2].

I found some strange thing on i2c bus [1]. Then I figure out what should be done to make work the digital part.
But because of lack of time and motivation (like everybody ;) ), I stopped working on this.

Matthieu

[1] http://www.mail-archive.com/[email protected]/msg00987.html

[2]
== i2c ==
0x1f zl
0xa0 eeprom
0xa2 ??? (0xff)
0xa4
0xa6->0xac ??? (0xff)
0xae 0xc2 (tuner)
== gpio ==
0 (WP eeprom ?? )
1 ZL RESET
2 tuner_reset_gpio
4 input sel ???
5 (led green)
7 (led blue)
== eeprom format ==
0x0-0x3 : magic ???
0x4-0x15 : GetDescriptor device
0xc VID
0xE PID
0x10 DID
0x12 iManufacturer
0x13 Product string
0x14 SerialNumber

0x40 string size (10 03) ???
0x42-0x4f (Product string @32)
0x94 string size (16 03)
0x96-0xa9 (SerialNumber @64)
0x16 string size (02 03)
0x18- (iManufacturer @16)

0x60 : iConfiguration index ???
0x6a string size (0a 03)
0x6c (iConfiguration @48)

where is mac address and rev ???