Date: Mon, 9 Aug 1999 02:55:23 -0400 (EDT) From: "Matthew N. Dodd" <winter@jurai.net> To: Robert Watson <robert+freebsd@cyrus.watson.org> Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: kern/12275: Patches to add support for new chipset (fwd) Message-ID: <Pine.BSF.4.10.9908090251550.14648-100000@sasami.jurai.net> In-Reply-To: <Pine.BSF.3.96.990808223916.13826B-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 8 Aug 1999, Robert Watson wrote: > Given that the card doesn't work without the lines as I have them, I think > that the current arrangement is actually the correct one. See below. Great. Like I said, I was blindly guessing in an attmept to make sense of the bulk of the patch. > > > Any chance that we can identify the PHY used by these cards and make sure > > we're dealing with one of them before we go reading and writing to one > > blindly? What if Diamond changes PHYs? > > The AM79C979 datsheet (p178) defines bits 1 - 0 of BCR49 as follows: > > 1-0 PHY_SEL PHY Select. These bits define the active PHY as follows: > 00 10BASE-T PHY > 01 HomePNA PHY > 10 External PHY > 11 Reserved/Undefined Ah. If its an internal PHY its likely not an MII PHY. > As far as I can tell, there does not seem to be a way to probe for > available PHY's. At least on the card I have, there is only a phone-net > port, so I'm not sure why they don't auto-assign the PHY. I'll look into > this further though--perhaps this should be influenced by the interface > link state, or the like. BSD/OS has a nice feature wherein (I believe) > interfaces can generate their own lists of link types and ifconfig can be > used to dynmically list and select from among these, with custom strings. Where is the datasheet for this chip? > > Anyhow, I don't see these design issues getting in the way of adding > > functionality. > > > > Regenerate your patch and I'll commit it. (unless someone else wants to.) > > Sounds great. I'll investigate further, but I think just hard-assigning > the PHY is the best solution for the time being. Indeed. Give me a patch with your debuging stuff deleted and I'll commit to -current. We can investigate the bells and whistles later. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9908090251550.14648-100000>