public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RTC required for network support on OCOTEA?
Date: Wed, 10 Nov 2004 22:41:10 +0100	[thread overview]
Message-ID: <20041110214115.F3E08C14AD@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 10 Nov 2004 11:30:52 EST." <4192423C.3010908@mc.com>

In message <4192423C.3010908@mc.com> you wrote:
> 
> We are in the process of porting ocotea-based U-Boot 1.1.1 to custom
> ppc440gx hardware. Everything is pretty much working except for the
> network interface.  We can send out a ping but never process the reply.
> Ethereal does see both the ping and reply packets!
> 
> 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?

Neither U-Boot nor Linux does need any RTC for network operation.

Best regards,

Wolfgang Denk

-- 
See us @ Embedded/Electronica Munich, Nov 09 - 12, Hall A.6 Booth 513
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Any sufficiently advanced technology is indistinguishable from magic.
Clarke's Third Law       - _Profiles of the Future_ (1962; rev. 1973)
                  ``Hazards of Prophecy: The Failure of Imagination''

      parent reply	other threads:[~2004-11-10 21:41 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
2004-11-10 18:49   ` Andrew Wozniak
2004-11-10 21:41 ` Wolfgang Denk [this message]

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=20041110214115.F3E08C14AD@atlas.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