From: Travis Sawyer <tsawyer+u-boot@sandburst.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RTC required for network support on OCOTEA?
Date: Wed, 10 Nov 2004 13:03:28 -0500 [thread overview]
Message-ID: <1100109808.30650.6.camel@pavement.sandburst.com> (raw)
In-Reply-To: <4192423C.3010908@mc.com>
On Wed, 2004-11-10 at 11:30, Andrew Wozniak wrote:
> Hello everyone,
> In debugging the network component of U-Boot, someone mentioned that a
> RTC might be required for proper operation. Unlike the OCOTEA board, we
> do NOT have a RTC. After examining all the READMEs and looking at
> source code, I don't see any dependency on a RTC. Can anyone confirm this?
>
Hunh???
Are you using the Cicada/Vitesse phy that is on the ocotea?
There is a gotcha with that phy. IIRC, our in house board doesn't have
the 13" of trace, so I had to set a bit.
From 440gx_enet.c /* Note: slightly hacked for use with our metrobox
system */
#if defined(CONFIG_440_GX)
#if defined(CONFIG_CIS8201_PHY)
/*
* Cicada 8201 PHY needs to have an extended register whacked
* for RGMII mode.
*/
if ( ((devnum == 2) || (devnum ==3)) && (4 == ethgroup) ) {
#if defined(CONFIG_METROBOX)
miiphy_write (reg, 23, 0x1300);
#else
miiphy_write (reg, 23, 0x1200);
#endif
This is just above the vsc8201/cis8201 errata code.
Specifically, bit 8 enables RGMII skew timing compensation.
As for requiring an RTC, I _*REALLY*_ don't see how one has to do with
the other.
Good luck,
Travis
next prev parent reply other threads:[~2004-11-10 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-10 16:30 [U-Boot-Users] RTC required for network support on OCOTEA? Andrew Wozniak
2004-11-10 18:03 ` Travis Sawyer [this message]
2004-11-10 18:49 ` Andrew Wozniak
2004-11-10 21:41 ` Wolfgang Denk
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=1100109808.30650.6.camel@pavement.sandburst.com \
--to=tsawyer+u-boot@sandburst.com \
--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