Hmm. That reminds me: I've also got a box with an onboard
8255X that isn't recognized. The relevant parts of "boot -v"
output are:
found-> vendor=0x8086, dev=0x1209, revid=0x09
class=02-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0 secondarybus=0
intpin=a, irq=11
map[10]: type 1, range 32, base ffaff000, size 12
map[14]: type 1, range 32, base 0000ef00, size 6
map[18]: type 1, range 32, base ffac0000, size 17
[...]
pci0: unknown card (vendor=0x8086, dev=0x1209) at 14.0 irq 11
This is on 4.0-20000214-CURRENT.
I'm happy to provide further information, test patches, etc.,
if it's helpful.
Jim Shankland
NLynx Systems, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
- Onboard Intel fxp network chip, unknown PHY 17 type 2 Roger Hardiman
- Re: Onboard Intel fxp network chip, unknown PHY 17 t... David Greenman
- Re: Onboard Intel fxp network chip, unknown PHY ... Roger Hardiman
- Re: Onboard Intel fxp network chip, unknown ... Kenneth D. Merry
- Re: Onboard Intel fxp network chip, unknown PHY 17 t... Mike Smith
- Re: Onboard Intel fxp network chip, unknown PHY ... Roger Hardiman
- Re: Onboard Intel fxp network chip, unknown ... David Greenman
- Re: Onboard Intel fxp network chip, unkn... Mike Smith
- Re: Onboard Intel fxp network chip,... David Greenman
- Re: Onboard Intel fxp network c... Mike Smith
- Re: Onboard Intel fxp netwo... Jim Shankland
- Re: Onboard Intel fxp netwo... David Greenman
- Re: Onboard Intel fxp netwo... Jim Shankland
- Re: Onboard Intel fxp netwo... Milon Papezik

