From owner-freebsd-sparc Thu Nov 21 10:15:35 2002 Delivered-To: freebsd-sparc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D58037B401; Thu, 21 Nov 2002 10:15:34 -0800 (PST) Received: from alpha.de.tiscali.com (alpha.de.tiscali.com [62.27.91.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C53B43E8A; Thu, 21 Nov 2002 10:15:33 -0800 (PST) (envelope-from oliver.blasnik@de.tiscali.com) Received: from TECHNIK47 (unknown [10.49.10.29]) by alpha.de.tiscali.com (Postfix) with SMTP id D5B4764C69; Thu, 21 Nov 2002 19:15:25 +0100 (CET) Message-ID: <00d401c29189$f707b620$1d0a310a@de.tiscali.com> From: "Oliver Blasnik" To: Cc: , "Mike Smith" References: <007601c29168$dfdaa5f0$1d0a310a@de.tiscali.com> <20021121154405.GB30274@newtrinity.zeist.de> Subject: Re: Fw: [PATCH] HME (Happy Meal Ethernet) and T1/105... Date: Thu, 21 Nov 2002 19:13:28 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-sparc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi Marius, > i doubt your mii-patch is correct, the lucent mii-transceiver that sun > puts to the hme-chips is the lu6612 which is a 64pin lqfp, this also > matches the oui and model you put into miidevs. [...] I'm going to investigate that, but it looks that you're right: The chip itself has "1216F" printed on, nothing like "6612". As I found no datasheet for it I asked a friend of mine for register compatibility. He told me "like 83840". The OUI and Model numbers are the same for both the 1216F probed and the 6612 specs. Should be the same chip, then. > moreover, the lu6612 also isn't driver-compatible to the dp83840, > at least the linux hme-driver distinguishes between the two (look for > is_lucent_phy() in linux/drivers/net/sunhme.c; I did, and I love that comments in this source ;) And again, it seems you're right, as there's no use of extended registers if the Lucent is detected. Possibly unneeded, as the 83840 has its special registers from 0x12-0x19, whereas the Lucent ranges 0x1c-0x1e. I thank you a lot for that information (and going to kick someone for his...) Now, after I inspected the 6612 datasheet, there is nothing special to support (possibly the 10mbit-mode: "extended line length"), so someone can live with the default support and ukphy. Somewhat like a "genphy" device would be nice instead the uk (its more a generic driver in my opinion), at least for printing out KNOWN device information (which can't come from a ukphy = unknown phy driver). Cu, Oliver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message