It seems that the BeOS port does detection with the code that's in generate_driver() from gen_driver_beos.inc.? I'll probably take a similar approach, I was kinda confused about why it was important to distinguish between regular or subsystem.
Dee -----Original Message----- From: Hannu Savolainen <ha...@opensound.com> To: Discussion mailing list for developers of OSS <oss-devel@mailman.opensound.com> Sent: Tue, 24 Feb 2009 2:40 pm Subject: Re: [oss-devel] Porting to other OS's Hannu Savolainen wrote: > demetrioussha...@netscape.net kirjoitti: > >> In the devlist files, what's the significance of some of the vendor's >> being prefixed with 'pci' while others are prefixed with 'pcs'? >> > The pci ones are used for PCI primary vendor/device ID. The pcs entries > are for the subsystem vendor/device ID. > > The idea is that pcs entries are used when it's possible to give better > identification for the sound card instead of just some generic chipset > name. If there is no matching pcs entry then the device will be > indentified as a generic one. > One more thing. The ossdetect utility (that uses the .devices info) tries first match the sub device id. If that fails then the primary PCI device ID is used. The Solaris version of ossdetect does some additional processing because Solaris identifies all PCI devices by their subsystem ID. Best regards, Hannu _______________________________________________ oss-devel mailing list oss-devel@mailman.opensound.com http://mailman.opensound.com/mailman/listinfo/oss-devel
_______________________________________________ oss-devel mailing list oss-devel@mailman.opensound.com http://mailman.opensound.com/mailman/listinfo/oss-devel
