From owner-freebsd-stable Sun May 13 21:27:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 3F15C37B424 for ; Sun, 13 May 2001 21:27:11 -0700 (PDT) (envelope-from DougB@DougBarton.net) Received: from DougBarton.net (master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id VAA78474; Sun, 13 May 2001 21:27:00 -0700 (PDT) (envelope-from DougB@DougBarton.net) Message-ID: <3AFF5E94.CF722691@DougBarton.net> Date: Sun, 13 May 2001 21:27:00 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Dan Kogai Cc: Jonathan Lemon , stable@FreeBSD.ORG Subject: Re: fxp under miibus does not work for non-miibus fxp! References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Kogai wrote: > Maybe the move was a little bit too premature. > I just tried the new kernel (4.x-stable) with fxp on miibus and it failed > for a genuine, pci, non-miibus fxp! I think you have some misunderstandings. > Strange thing is that it pings itself fine but it never pings out. > > What I found out was that old config file works even with new sources. > > Old config that works [snippage] > > # PCI Ethernet NICs. > > device fxp # Intel EtherExpress PRO/100B (82557, 82558) > > device miibus # MII bus support > While the new configuration with fxp under miibus does not. > > > device miibus # MII bus support > > device fxp # Intel EtherExpress PRO/100B (82557, 82558) It doesn't (or shouldn't) matter which order you have them in. The new fxp code uses the miibus code either way. I'm sure Jonathan can give you more details. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message