From owner-freebsd-hackers Thu Oct 12 17:22:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 02ABB37B502 for ; Thu, 12 Oct 2000 17:22:13 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id RAA09044; Thu, 12 Oct 2000 17:21:45 -0700 (PDT) Message-Id: <200010130021.RAA09044@implode.root.com> To: Dennis Cc: hackers@freebsd.org Subject: Re: yet another unsupported PHY in fxp driver In-reply-to: Your message of "Wed, 12 Oct 1988 10:58:34 EDT." <5.0.0.25.0.19881012105604.029b4160@mail.etinc.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 12 Oct 2000 17:21:45 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >It seems that the NetBSD folks have eliminated this ongoing pain in the >butt by using the mii interface for the intel cards. Is freebsd also moving >in this direction? Every few months there seems to be a problem, and its >difficult to fix it without docs The primary problems that have resulted in the "unsupported PHY" messages in the past year or so have been related to either the format or size of the SEEPROM changing. Using generic MII code doesn't fix the problem; the fxp's would still not work due to the MAC address being wrong, among other things, which is also read from the SEEPROM. This said, I think it is generally the right approach to use a generic MII PHY software interface and at some point the driver will likely be updated for that. It is low priority, however, since it doesn't solve any problems. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message