From owner-freebsd-hackers Mon Mar 12 7:55:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id B479537B718 for ; Mon, 12 Mar 2001 07:55:50 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id LAA99379; Mon, 12 Mar 2001 11:08:00 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010312110505.0273eda0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Mon, 12 Mar 2001 11:10:26 -0500 To: seebs@plethora.net (Peter Seebach), hackers@FreeBSD.ORG From: Dennis Subject: Re: if_fxp - the real point In-Reply-To: <200103110337.f2B3b1210404@guild.plethora.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:37 PM 03/10/2001, Peter Seebach wrote: >If anyone has a specific part number or model information about the new >unsupported PHY, I'd be happy to look it up and tell you what, if anything, >I can find out. I can't send out copies of the source without some kind >of formal approval, but I could certainly at least answer questions like >"do we have a BSD-flavored driver that works with this". As it turns out (as usual), its not an "unsupported PHY" but an error in the assumption that the correct PHY information is where DG's logic thinks it should be in the eeprom. Reading the PHY info from the part directly allows you to correctly identify and set up the phy, at least on the SuperMicro MB that I was having problems with. For those with boards that give the "unsupported PHY" message who want a "quick fix", you might try just forcing the address to 1 and the device_type to 7, as every eepro100 that I've tested uses the 82555 PHY. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message