Re: Openchrome Package Audit
Luc Verhaegen wrote:
> On Wed, May 28, 2008 at 12:29:19AM +0200, Brice Goglin wrote:
>> Raphael Geissert wrote:
>> >> Oh, and one thing I forgot: you may want to provide a file in
>> >> /usr/share/xserver-xorg/pci/ to get the driver automatically loaded
>> >> when the server sees a supported chip.
>> >>
>> >
>> > How are those files generated? I'd like to know so I can request
>> > upstream to generate those files too. I can see src/via_id.c has some
>> > cards information, but nothing else.
>> >
>>
>> When possible, we patch Makefile.am to sed the source and generate
>> pci.ids at build time.
>> See
>>
http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-ati.git;a=blob;f=debian/patches/01_gen_pci_ids.diff
>>
>> When it is not possible to do that, for instance for the vmware driver,
>> we hardwire the list of pci.ids
>>
http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-vmware.git;a=blob;f=debian/vmware.ids
>>
>> Brice
>
> via_id.c contains a table to match up subsystem ids. In reality there
> are only 10 unique unichrome device ids.
Could you please shed some light on this?
$ awk '/^#define.*PCI_CHIP/ {print $$3}' src/via_id.h |
sed -e 's/0x/1002/' | wc -l
9
Or is [1] also supposed to be matched?
[1]#define PCI_VIA_VENDOR_ID 0x1106
>
> Luc Verhaegen.
> http://unichrome.sf.net/
Thanks for the info :)
Cheers,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
Reply to: