From: Wolfgang Denk <wd@denx.de>
To: "Klatt, Fred" <fred.klatt@windriver.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: boot failure on lite5200b board
Date: Sat, 18 Nov 2006 00:13:27 +0100 [thread overview]
Message-ID: <20061117231327.106843525AB@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 17 Nov 2006 04:58:31 PST." <F6AE8F99CFBB884E9681D609D859BAD339FF0E@ala-mail02.corp.ad.wrs.com>
In message <F6AE8F99CFBB884E9681D609D859BAD339FF0E@ala-mail02.corp.ad.wrs.com> you wrote:
>
> Was there ever a fix for the Lite5200B boot up problem where uboot keeps
> rebooting?
Installing a recent version of U-Boot?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
A secure program has to be robust: it must be able to deal with
conditions that "can't happen", whether user input, program error or
library/etc. This is basic damage control. Buffer overflow errors
have nothing to do with security, but everything with stupidity.
-- Wietse Venema in <5cnqm3$8r9@spike.porcupine.org>
next prev parent reply other threads:[~2006-11-17 23:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 12:58 boot failure on lite5200b board Klatt, Fred
2006-11-17 23:13 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-23 17:10 Marty @ GMail
2006-02-22 7:53 TXEMA LOPEZ
2006-02-22 4:04 #LI JIANGGAN#
2006-02-22 8:24 ` Andrey Volkov
2006-02-23 7:38 ` Sylvain Munaut
2006-02-23 10:13 ` #LI JIANGGAN#
[not found] ` <84A109BF918D934CB46ACF33BCE187C002D54D7A@mail02.student.main.ntu.edu. sg>
2006-02-23 10:08 ` tnt
[not found] ` <4b73d43f0602230818w63423513n817d9ec7eb580d2c@mail.gmail.com>
2006-02-24 3:31 ` #LI JIANGGAN#
2006-02-24 16:48 ` Dale Farnsworth
2006-02-24 17:17 ` John Rigby
2006-03-01 17:16 ` #LI JIANGGAN#
2006-03-02 0:52 ` John Rigby
2006-03-03 8:06 ` #LI JIANGGAN#
2006-03-03 15:01 ` White
2006-03-04 9:17 ` Sylvain Munaut
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=20061117231327.106843525AB@atlas.denx.de \
--to=wd@denx.de \
--cc=fred.klatt@windriver.com \
--cc=linuxppc-embedded@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).