From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] MII / RMII
Date: Tue, 8 Jan 2008 05:43:17 +0100 [thread overview]
Message-ID: <200801080543.18095.sr@denx.de> (raw)
In-Reply-To: <2acbd3e40801071735r374fbdfdt3797e207fe54976b@mail.gmail.com>
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
=====================================================================
next prev parent reply other threads:[~2008-01-08 4:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 18:51 [U-Boot-Users] MII / RMII Guennadi Liakhovetski
2007-11-29 20:31 ` Ben Warren
2007-11-29 22:25 ` Haavard Skinnemoen
2007-11-29 22:25 ` Ulf Samuelsson
2007-11-29 22:55 ` Ben Warren
2007-11-29 23:45 ` Ulf Samuelsson
2008-01-08 1:35 ` Andy Fleming
2008-01-08 4:43 ` Stefan Roese [this message]
2008-01-08 16:27 ` Ben Warren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200801080543.18095.sr@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox