From owner-freebsd-hackers Mon Mar 13 12:18:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1x.pvt.net (ns.pvt.net [194.149.105.18]) by hub.freebsd.org (Postfix) with ESMTP id 3FCED37BBF3; Mon, 13 Mar 2000 12:17:47 -0800 (PST) (envelope-from milon.papezik@oskarmobil.cz) Received: from oskarmobil.cz (nat.ceskymobil.cz [194.149.122.193]) by ns1x.pvt.net (8.9.3/8.9.3) with ESMTP id VAA02531; Mon, 13 Mar 2000 21:16:42 +0100 Message-ID: <38CD4BDF.760C85AE@oskarmobil.cz> Date: Mon, 13 Mar 2000 21:13:19 +0100 From: Milon Papezik X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: cz, cs, en MIME-Version: 1.0 To: dg@root.com Cc: Jim Shankland , msmith@FreeBSD.ORG, hackers@FreeBSD.ORG, roger@cs.strath.ac.uk Subject: Re: Onboard Intel fxp network chip, unknown PHY 17 type 2 References: <200003101922.LAA25494@implode.root.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Greenman wrote: > > >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 > ^^^^^ > > Don't know what that is, but's not a part that is supported by the fxp > driver. It would help if you could find out the part number (8255X isn't > sufficient since it isn't really just one series - some of the parts are > similar, and others are completely different). I've run into similar problem with Compaq branded card under 3.4R. Chip number GD82559, series(?) L933SB2. The PCI chip ID was set to 82558, but I was able to distinguish between 8255[89] by reading PHY revision code directly from PHY's registers and the PHY revision code was the same as in Intel's docs for 82559. I can test the patch. Hope this helps. Milon Papezik -- milon.papezik@oskarmobil.cz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message