On Fri, Nov 13, 2009 at 11:38 AM, Jan Hoogenraad <jan-conceptronic@xxxxxxxxxxxxxx> 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 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. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- 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
