Hi Jan,
In order to ease the maintenance work I have started to include direkt
links from the device's entry in the wiki to the source repository's
history of the driver.
E.g. In the entry for Avermedia AverTV A800 you'll
see "Supported in kernel since 2.6.13".
Now the word "kernel" is a hype
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
On Fri, Nov 13, 2009 at 11:45:07AM -0500, Devin Heitmueller wrote:
> On Fri, Nov 13, 2009 at 11:38 AM, Jan Hoogenraad
> 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 i
On Fri, Nov 13, 2009 at 11:38 AM, Jan Hoogenraad
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.
> This is hard to keep
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.
This is hard to keep synchronised.
Basic information like device IDs, vendors, demo
Hi Devin,
I'm sorry. I just realized that I was only subscribed to linux-dvb but
not to linux-media. I fixed that now but my reply to your emails will
not have the correct In-Reply-To/References headers.
> I have to wonder if maybe we are simply using the wrong tool for the
> job. Perhaps it w
