H. Langos wrote:
On Fri, Nov 13, 2009 at 11:45:07AM -0500, Devin Heitmueller wrote:
The challenge you run into there is that every driver organizes its
table of products differently, and the driver source code does not
expose what features the device supports in any easily easily parsed
manner. Also, it does not indicate what the hardware supports which
is not supported by the Linux driver.
So for example, you can have a hybrid USB device that supports
ATSC/QAM and analog NTSC. The driver won't really tell you these
things, nor will it tell you that the hardware also supports IR but
the Linux driver does not.
It's one of those ideas that sounds reasonable until you look at how
the actual code defines devices.
Yeap. I agree whole heartedly. For some simle drivers you can read that
information from the source. But most drivers support e.g. more than one
tuner and the information which device has which tuner, is not part of
the driver anymore. Rather the driver looks onto the device's i2c bus
to find out which tuner is present. At least this is what I gathered
from browsing through the driver code in order to get my device
table up to date. (see
http://www.linuxtv.org/wiki/index.php/Talk:DVB-T_USB_Devices#Adding_supported_devices_from_kernel_sources
) I don't actually have a clue. So don't take my word for it.
cheers
-henrik
I agree, now you spell it out.
I first thought that at least the names of the supported devices should
be readable from the code.
All supported USB IDs can be found easily from
grep -i dvb /lib/modules/`uname -r`/modules.usbmap | sed -e
's/0x0000.*$//' -e 's/ 0x0003/ /' -e 's/^.*://'
As the code lists names for each device, I would expect there would be
an utility like
lsusb -v -d xxxx:xxxx
to list the names from the .devices = sections , just like depmod scans
the device IDs.
However, I have not found such a utility.
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
