Eric Lowe wrote:
> Garrett D'Amore wrote:
>> about them if one is known. I _think_ it will also work for Cardbus
>> devices, but I can't verify that easily right now.
>
> It does.
>
> /pci at 0,0/pci8086,2448 at 1e/pci104d,81e6 at 4 (pci104d,81e6)
> class-code: PCI/CardBus Bridge (60700)
> vendor-id: Texas Instruments (104c)
> device-id: Unknown (8039)
> subsystem-vendor-id: Unknown (ffffffff)
> subsystem-device-id: Unknown (ffffffff)
> revision: 0
>
> /pci at 0,0/pci8086,2448 at 1e/pci104d,81e6 at 4/ethernet at 0 (ethernet)
> class-code: Ethernet Controller (20000)
> vendor-id: Atheros Communications (168c)
> device-id: AR5212 Wireless LAN (13)
> subsystem-vendor-id: Netgear (1385)
> subsystem-device-id: Unknown (5b00)
> revision: 1
>
> - Eric
Ah. Good to know. Can you use prtconf and let me know whether the
cardbus bridge has a device_type (property) value of either "pci" or
"cardbus"? I'm checking both right now, but maybe the test for
"cardbus" is redundant. (If it is type "pci" though, it will probably
be a little less "clean" for me to prune cardbus from the tree, or only
display cardbus nodes, if ever I wanted to do that.)
-- Garrett
--
Garrett D'Amore, Principal Software Engineer
Tadpole Computer / Computing Technologies Division,
General Dynamics C4 Systems
http://www.tadpolecomputer.com/
Phone: 951 325-2134 Fax: 951 325-2191
