François Revol wrote: >> 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.> >> > I don't really know the rationale behind ossdetect, but the BeOS code now > just probes cards both by pci IDs and subsystem IDs...Likely Solaris can't do > this automatically without updating driver metadata ? > Solaris has just bit different logic. > Now, I'm not actually sure the pcs entries are listed first in the match > table for module.inc which checks a single table sequentially though...Some > grepping tells me the pcs entries in .devices are often afterward, maybe I > should parse the table in reverse order, or split it. > The pci and pcs entries are in random order.
Best regards, Hannu _______________________________________________ oss-devel mailing list oss-devel@mailman.opensound.com http://mailman.opensound.com/mailman/listinfo/oss-devel
