Date: Fri, 14 Dec 2001 05:54:29 +0100 From: Dimitry Andric <dim@xs4all.nl> To: David Greenman <dg@root.com> Cc: Sergey Matveychuk <sem@ciam.ru>, Jonathan Lemon <jlemon@flugsvamp.com>, freebsd-stable@FreeBSD.ORG Subject: Re: fxp half-duplex problemm Message-ID: <3656702083.20011214055429@xs4all.nl> In-Reply-To: <20011213202106.B78956@nexus.root.com> References: <local.mail.freebsd-stable/5.1.0.14.0.20011210162739.01c08a50@marble.sentex.ca> <200112122035.fBCKZBJ62726@prism.flugsvamp.com> <002901c183c9$659763d0$0a2da8c0@sem> <20011213102230.A75383@nexus.root.com> <16453339468.20011214045827@xs4all.nl> <20011213200046.A78956@nexus.root.com> <18354777165.20011214052224@xs4all.nl> <20011213202106.B78956@nexus.root.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2001-12-14 at 05:21:06 David Greenman wrote: >>It doesn't really make sense to have separate options for half and >>full duplex, because they are mutually exclusive anyway. So one of >>them was dropped. I'm not sure, but it seems to be the case with all >>NIC drivers using the common miibus code. DG> I agree that the two options are mutually exclusive, but I don't agree DG> that it doesn't make sense to have both. It's not clear if there is a default DG> or what it defaults to or when such a default is relevant. There needs to DG> be a "half-duplex" option to make this explicitly clear in the configuration. I tend to agree with that, it would seem better to have it more explicit, or at least consistent between all NIC drivers. At the moment, however, it isn't, at least on -STABLE (don't have a -CURRENT box here to check atm): dim@tensor:/usr/src/sys/dev/mii% ls *.c acphy.c exphy.c mlphy.c qsphy.c xmphy.c amphy.c inphy.c nsgphy.c rlphy.c brgphy.c lxtphy.c nsphy.c tlphy.c dcphy.c mii.c pnaphy.c ukphy.c e1000phy.c mii_physubr.c pnphy.c ukphy_subr.c dim@tensor:/usr/src/sys/dev/mii% grep -l IFM_HDX *.c amphy.c brgphy.c e1000phy.c nsgphy.c xmphy.c So in this directory, there are quite a few phy drivers which don't support the IFM_HDX option (needed for mediaopt half-duplex). I'm unsure if these inconsistencies were by design, but I guess not. :) Btw, almost all of the files which DO support IFM_HDX were written by Bill Paul, so that's probably why they share this property. Cheers, - -- Dimitry Andric <dim@xs4all.nl> PGP Key: http://www.xs4all.nl/~dim/dim.asc Fingerprint: 7AB462D2CE35FC6D42394FCDB05EA30A2E2096A3 Lbh ner abj va ivbyngvba bs gur QZPN -----BEGIN PGP SIGNATURE----- Version: PGP 6.5i Comment: http://www.gn.apc.org/duncan/stoa_cover.htm iQA/AwUBPBl3+7BeowouIJajEQKbZwCgipajGcG5iYPqox7u6fkHOtcPNqgAoKa9 F0tTOx43xzTaY7ULdtGyP+sP =0tIF -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3656702083.20011214055429>