re: Pegasos dmesg
matthew green <[email protected]>
| Newsgroups | gmane.os.netbsd.ports.ofppc |
|---|---|
| Message-ID | <[email protected]> |
> sip0 at pci0 dev 5 function 0: NatSemi DP83815 10/100 Ethernet, rev 00 > sip0: interrupting at irq 9 > sip0: Ethernet address 00:0f:b5:06:38:02 > nsphyter0 at sip0 phy 0: DP83815 10/100 media interface, rev. 1 > nsphyter0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ex0 at pci0 dev 6 function 0: 3Com 3c905B-TX 10/100 Ethernet (rev. > 0x64) > ex0: interrupting at irq 9 > ex0: MAC address 00:50:04:4b:24:d5 > bmtphy0 at ex0 phy 24: Broadcom 3c905B internal PHY, rev. 0 > bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ex0: WARNING: powerhook_establish is deprecated > > > BTW, i meant to say that these are two PCI cards i was testing > out and they both work, but are not present on normal pegasos. That's great! So SmartFirmware configured everything correctly. nope! the onboard ethernet and both of these cards failed without my changes to enable pci_configure_bus(9) support. the onboard ethernet only worked in netboot case prioer. smartfirmware is infact not very smart. it would hang hard if i typed ".properties" in the ex(4) node, trying to display the "rom" property... But maybe this is because network cards may be used directly by OFW. The on-board AC97 audio was not configured, so it might be interesting to put other cards, like audio-, video-, etc. into it, which might be ignored. this should already be done. i've removed the pegasos pci_attach_hook() that set up a couple of devices and put a couple of "special this device" cases in the pci_conf_hook(). .mrg.