From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Roese Date: Tue, 8 Jan 2008 05:43:17 +0100 Subject: [U-Boot-Users] MII / RMII In-Reply-To: <2acbd3e40801071735r374fbdfdt3797e207fe54976b@mail.gmail.com> References: <1196375148.13652.156.camel@elrond.atmel.sweden> <2acbd3e40801071735r374fbdfdt3797e207fe54976b@mail.gmail.com> Message-ID: <200801080543.18095.sr@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Tuesday 08 January 2008, Andy Fleming wrote: > > I think that if you use an Ethernet and need to differentiate > > between MII and RMII they should be mutually exclusive. > > You either define CONFIG_RMII OR CONFIG_MII but not both. > > If you have a PHY on the chip, then you do not define any of the two. > > MII uses more pins and maybe different pins, so a port for a CPU > > should differentiate. > > I'm a little late to this, but I feel I should make sure people are aware > that CONFIG_MII and CONFIG_RMII are not, in this case, two different > options for the same concept. CONFIG_MII is the option you enable to allow > MII Management operations to be done. It should *probably* be called > CONFIG_MDIO. Yes, this would be good. Anyone interested in fixing up a patch for this? Thanks. Best regards, Stefan ===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de =====================================================================