> both 1095,3112 (vendor/device id) and 1095,6112 > (subsystem vendor/subsystem device id) refer to the same card > / device node.
Yeah I know it's the same card; I just figured the chipsets were being detected independently as indicated by scanpci. Because there definitely is a sil3112 on there. > Main problem is that this a raid mass storage controller: > "CLASS 0x01 0x04 0x00" > > > These are skipped by the check in "is_pciide()", which > only cares about devices in classes PCI_MASS_IDE, > PCI_MASS_SATA and PCI_MASS_OTHER: > > PCI_MASS_IDE: CLASS 0x01 0x01 ... > PCI_MASS_SATA: CLASS 0x01 0x06 ... > PCI_MASS_OTHER: CLASS 0x01 0x80 ... > > See > http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/i86pc/io/ >pci/pci_boot.c#is_pciide Interesting. Again, I have little knowledge of hardware from the programming perspective, but should I expect the 6112 to work in a backwords compatitible way as a 3112? That would surprise me. I would have expected that one would have to "address" the 3112 somehow, ignoring the 6112. Given that scanpci is able to find the 3112, that indicates there is some standard method by which to discover these things on the PCI bus. Would a proper fix then be to have the pci-ide driver traverse the tree even though the 6112 is not a mass storage controller, in order to find and use the 3112 that is "behind it"? (Perhaps this makes no sense at all... again I have too little knowledge of how PCI works.) -- / Peter Schuller, InfiDyne Technologies HB PGP userID: 0xE9758B7D or 'Peter Schuller <[EMAIL PROTECTED]>' Key retrieval: Send an E-Mail to [EMAIL PROTECTED] E-Mail: [EMAIL PROTECTED] Web: http://www.scode.org _______________________________________________ opensolaris-discuss mailing list [email protected]
