linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Masters <jonmasters@gmail.com>
To: grave <grave@ipno.in2p3.fr>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: uboot and ppc405
Date: Mon, 25 Oct 2004 14:57:30 +0100	[thread overview]
Message-ID: <35fb2e5904102506574d6c7470@mail.gmail.com> (raw)
In-Reply-To: <1098701468l.31592l.0l@ipnnarval>

On Mon, 25 Oct 2004 10:51:08 +0000, grave <grave@ipno.in2p3.fr> wrote:

> We re starting a disign with xilinx chip Virtex II pro and I wonder the
> typical size of an uboot binary. This is for our electronician disigner
> in order to dimension the prom and so on...

It might be worth asking your electronics people whether they're going
to use the Xilinx SysACE chip in your hardware design. If this is the
case then you can program the Virtex and load in the kernel and
bootloader from Compact Flash. I don't know whether uboot supports
this out of the box since I wrote my own Virtex II bootloader, but it
should be quite doable.

Certainly you really want to avoid PROMs in the design if at all
possible - with our design it's possible for us to swap out a CF and
in one step replace all hardware and software, upgrading is a case of
sending the customer a loopback mountable filesystem which reloads the
CF after the customer downloads the "firmware update" via a web page.

Cheers,

Jon.

  reply	other threads:[~2004-10-25 13:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-25 10:51 uboot and ppc405 grave
2004-10-25 13:57 ` Jon Masters [this message]
2004-10-25 16:35 ` Peter Ryser
2004-10-25 21:07   ` Jon Masters
2004-10-26  5:39     ` Peter Ryser
2004-10-26 15:48       ` Jon Masters
2004-10-26 16:55         ` Peter Ryser
2004-10-26 20:59       ` Stephen Williams
2004-10-25 18:12 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2004-10-25 18:40 Shamile Khan
2006-06-21  6:29 Zhang Ke

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=35fb2e5904102506574d6c7470@mail.gmail.com \
    --to=jonmasters@gmail.com \
    --cc=grave@ipno.in2p3.fr \
    --cc=jonathan@jonmasters.org \
    --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).