All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Cc: linuxppc-dev@ozlabs.org,
	Norbert van Bolhuis <nvbolhuis@aimvalley.nl>,
	Sean MacLennan <smaclennan@pikatech.com>
Subject: Re: [U-Boot] NAND only (no NOR)
Date: Wed, 3 Dec 2008 06:48:57 +0100	[thread overview]
Message-ID: <200812030648.57618.sr@denx.de> (raw)
In-Reply-To: <20081202215033.501f3403@lappy.seanm.ca>

On Wednesday 03 December 2008, Sean MacLennan wrote:
> We use a 256M NAND on the PIKA Warp appliance and where unable to boot
> u-boot from the NAND. It worked on a smaller 64M NAND.

Currently you need to define the page-size of the NAND used for booting (512 
bytes vs. 2k). The 2k 4xx NAND booting support is was done about 1/2 a year 
ago. So perhaps you tested this when this 2k support was not available yet.

> So we put our FPGA and u-boot in a small NOR. The kernel, rootfs and
> other files are on the NAND.

Yes, I would recommend to do it this way if possible. A small NOR for U-Boot 
and environment and everything else in NAND. This makes things much easier. 
But I understand that this is sometimes a problem with space (2 FLASH chips) 
and costs.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office@denx.de
=====================================================================

  reply	other threads:[~2008-12-03  5:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02  8:55 NAND only (no NOR) Norbert van Bolhuis
2008-12-02  9:31 ` [U-Boot] " Alessandro Rubini
2008-12-03  2:50 ` Sean MacLennan
2008-12-03  5:48   ` Stefan Roese [this message]
2008-12-03  6:38     ` [U-Boot] " Sean MacLennan
2008-12-03  7:40       ` Trent Piepho
2008-12-03 13:57         ` Leon Woestenberg

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=200812030648.57618.sr@denx.de \
    --to=sr@denx.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=nvbolhuis@aimvalley.nl \
    --cc=smaclennan@pikatech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.