From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] document network driver framework
Date: Wed, 22 Jul 2009 20:16:31 -0400 [thread overview]
Message-ID: <200907222016.32332.vapier@gentoo.org> (raw)
In-Reply-To: <2acbd3e40907221600g4671b6eds1c8cb93a2dac364c@mail.gmail.com>
On Wednesday 22 July 2009 19:00:40 Andy Fleming wrote:
> On Sat, Jul 18, 2009 at 8:04 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> > +----------------
> > + CONFIG Options
> > +----------------
> > +
> > +The common config defines your device should respect (if applicable):
> > + CONFIG_MII - configure in MII mode
> > + CONFIG_RMII - configure in RMII mode
>
> That's awfully global, and inflexible. I don't think there's any
> convention here that should be encouraged. The data bus configuration is a
> per-device attribute. If some system architects choose to allow this into
> their config files, far be it from me to protest, but I'm against it.
feel free to fix it then. this is a case of me documenting existing practice
and not feeling like doing the footwork to fix drivers. you can not like it
all you want, but that doesnt change reality.
> Also, CONFIG_MII doesn't mean what you think it means. It stems from the
> obnoxious overlap in terms set forth by IEEE 802.3. The MII in this case
> refers to the MII Management bus. Defining CONFIG_MII will cause
> miiphyutil.c to be built, which is a bit-bang MII Management bus driver.
> It will also enable some MII Management features. CONFIG_MII is therefore
> a relevant CONFIG option for most drivers.
yes, that's obvious, so i'm not sure why i missed it (especially considering i
also wrote support for it in the Blackfin net driver). i'll update the doc.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090722/8996d90e/attachment.pgp
next prev parent reply other threads:[~2009-07-23 0:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 1:39 [U-Boot] eth/net driver documentation Mike Frysinger
2009-07-16 17:36 ` Ben Warren
2009-07-19 1:04 ` [U-Boot] [PATCH 1/2] net: rename NetRxPkt to NetRxPacket Mike Frysinger
2009-07-21 4:49 ` Ben Warren
2009-07-19 1:04 ` [U-Boot] [PATCH 2/2] document network driver framework Mike Frysinger
2009-07-21 5:09 ` Ben Warren
2009-07-21 6:28 ` Mike Frysinger
2009-07-21 7:32 ` Wolfgang Denk
2009-07-21 20:38 ` Mike Frysinger
2009-07-21 20:55 ` Ben Warren
2009-07-21 21:08 ` Mike Frysinger
2009-07-21 7:27 ` Wolfgang Denk
2009-07-22 23:00 ` Andy Fleming
2009-07-23 0:16 ` Mike Frysinger [this message]
2009-07-23 21:49 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-23 22:06 ` Wolfgang Denk
2009-07-23 22:14 ` Ben Warren
2009-07-23 22:24 ` Wolfgang Denk
2009-09-09 18:41 ` [U-Boot] [PATCH v2] " Mike Frysinger
2009-09-22 18:34 ` Wolfgang Denk
2009-10-04 19:12 ` Wolfgang Denk
2009-10-04 22:07 ` Ben Warren
2009-10-05 6:05 ` 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=200907222016.32332.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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