From owner-freebsd-hackers Thu Mar 9 14:34:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 0772B37B87C; Thu, 9 Mar 2000 14:34:10 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA00573; Thu, 9 Mar 2000 14:33:51 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003092233.OAA00573@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: dg@root.com Cc: Roger Hardiman , Mike Smith , hackers@FreeBSD.ORG Subject: Re: Onboard Intel fxp network chip, unknown PHY 17 type 2 In-reply-to: Your message of "Thu, 09 Mar 2000 12:17:34 PST." <200003092017.MAA22562@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Mar 2000 14:33:51 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> > However, it reports PHY Unknown type 17 addr 2. > > > >> Mike wrote: > >> This is just a diagnostic message; the interface ought to work > >> regardless. Have you tried it? > > > >Oops. > > > >It works. > >I can ping the machine next to me. > > > >Pass me the pointy hat. > > Actually, it doesn't completely work. Full-duplex won't work for example, > since the driver has to know the PHY type in order to set the proper mode. Hmm. I wouldn't have seen that, being on a hub. The part on the board here is: GD82559 L942SH98 There's what might be the PHY next to it (assuming it's not internal). MVT203011 CW 722490-001 I don't recognise the logo on this, unless it's a new/changed International Rectifier logo (looks like two diodes pointing at each other inside a circle and square). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message