All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Hoogenraad <jan-conceptronic@hoogenraad.net>
To: Devin Heitmueller <dheitmueller@kernellabs.com>,
	Jan Hoogenraad <jan-conceptronic@hoogenraad.net>,
	linux-media@vger.kernel.org
Subject: Re: [linux-dvb] Organizing ALL device data in linuxtv wiki
Date: Fri, 13 Nov 2009 21:28:30 +0100	[thread overview]
Message-ID: <4AFDC16E.3040103@hoogenraad.net> (raw)
In-Reply-To: <20091113181023.GA31295@www.viadmin.org>

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.

  reply	other threads:[~2009-11-13 20:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12 17:31 Organizing ALL device data in linuxtv wiki H. Langos
2009-11-12 19:27 ` Devin Heitmueller
2009-11-12 19:29   ` Devin Heitmueller
2009-11-13 16:08 ` [linux-dvb] " H. Langos
2009-11-13 16:38   ` Jan Hoogenraad
2009-11-13 16:45     ` Devin Heitmueller
2009-11-13 18:10       ` H. Langos
2009-11-13 20:28         ` Jan Hoogenraad [this message]
2009-11-19 16:48     ` H. Langos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AFDC16E.3040103@hoogenraad.net \
    --to=jan-conceptronic@hoogenraad.net \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.