From: "H. Langos" <henrik-dvb@prak.org>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Jan Hoogenraad <jan-conceptronic@hoogenraad.net>,
linux-media@vger.kernel.org, linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Organizing ALL device data in linuxtv wiki
Date: Fri, 13 Nov 2009 19:10:23 +0100 [thread overview]
Message-ID: <20091113181023.GA31295@www.viadmin.org> (raw)
In-Reply-To: <829197380911130845y7a18ca25k266159c3af031a3e@mail.gmail.com>
On Fri, Nov 13, 2009 at 11:45:07AM -0500, Devin Heitmueller wrote:
> On Fri, Nov 13, 2009 at 11:38 AM, Jan Hoogenraad
> <jan-conceptronic@hoogenraad.net> wrote:
> > Would it be possible to store this information in the CODE archives, and
> > extract it from there ?
> > Right now, I end up putting essentially the same information into structures
> > in the driver and into documentation.
It would be possible. But that would require the driver developers
to agree on a machine readable format. Either in the code or in the
documentation. (BTW Which documentation would that be? I thought the code
was the only Documentation :-) )
> > This is hard to keep synchronised.
> >
> > Basic information like device IDs, vendors, demod types, tuners, etc is
> > already in place in the driver codes.
> >
> > Getting data from the hg archives (including development branches) sounds
> > like a cleaner solution.
>
> 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
next prev parent reply other threads:[~2009-11-13 18:10 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 [this message]
2009-11-13 20:28 ` Jan Hoogenraad
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=20091113181023.GA31295@www.viadmin.org \
--to=henrik-dvb@prak.org \
--cc=dheitmueller@kernellabs.com \
--cc=jan-conceptronic@hoogenraad.net \
--cc=linux-dvb@linuxtv.org \
--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.