From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] Allow PHY addresses on kirkwood egiga to be non continuous.
Date: Mon, 28 Jun 2010 14:02:07 +0200 [thread overview]
Message-ID: <20100628120207.CE13B14EBF7@gemini.denx.de> (raw)
In-Reply-To: <1277716302.2221.37.camel@tor-desktop>
Dear Tor Krill,
In message <1277716302.2221.37.camel@tor-desktop> you wrote:
>
> > 2. For the boards using single port will also need to configure PHY address
> > for other port, which is meaningless, unnecessary and confusing.
>
> Sure you had to put something there to be on the safe side. But is that
> really that confusing, the SOC really have two ports, them being used or
> not?
It is indeed confusing and should be avoided if one has to configurwe
hardware ports that are not actually present or used on a specific
board.
If needed, provide sane defaults internally in the code.
But keep in mind that U-Boot requires that only used peripherals
should be initialized - we should not initisalize any unused ports.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Let's say the docs present a simplified view of reality... :-)
- Larry Wall in <6940@jpl-devvax.JPL.NASA.GOV>
next prev parent reply other threads:[~2010-06-28 12:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F766E4F80769BD478052FB6533FA745D19A4A02082@SC-VEXCH4.marvell.com>
2010-06-28 9:11 ` [U-Boot] [PATCH V2] Allow PHY addresses on kirkwood egiga to be non continuous Tor Krill
2010-06-28 12:02 ` Wolfgang Denk [this message]
2010-06-28 17:44 ` Prafulla Wadaskar
2010-06-24 9:31 Tor Krill
2010-06-24 11:22 ` Prafulla Wadaskar
2010-06-24 11:34 ` Tor Krill
2010-06-24 16:37 ` Mike Frysinger
2010-06-24 16:48 ` Albert ARIBAUD
2010-06-24 16:53 ` Mike Frysinger
2010-06-28 9:20 ` Tor Krill
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=20100628120207.CE13B14EBF7@gemini.denx.de \
--to=wd@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