mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: <zoltan@bendor.com.au>
To: barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] mini2440: Consider correct NAND page size for boot.
Date: Wed, 23 Feb 2011 15:00:37 +1100 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.31.1102231440230.20973-100000@susu.bendor.com.au> (raw)
In-Reply-To: <1298409650-28408-3-git-send-email-jbe@pengutronix.de>

On Tue, 22 Feb 2011, Juergen Beisert wrote:

> From: Juergen Beisert <juergen@kreuzholzen.de>
>
> When booting from NAND, its important to know the correct page size.

Isn't that info available as soon as SteppingStone sucked in the first 4K
into the internal SRAM?

As far as I can follow the s3c2440 manual, bit 0 and the read-only bits 1
to 3 of the NFCONF register convey that information and these bits are set
by sampling a few GPIO (NCON and GPG13-GPG15) pins at reset. Supposedly
these pins are pulled up/low during reset so that SteppingStone itself can
read the boot code from the NAND.

What am I missing?

Zoltan


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2011-02-23  4:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22 21:20 [RFC] Add more changes to make the mini2440 work Juergen Beisert
2011-02-22 21:20 ` [PATCH 1/2] mini2440: Add more info about possible SDRAM and flash devices Juergen Beisert
2011-02-22 21:20 ` [PATCH 2/2] mini2440: Consider correct NAND page size for boot Juergen Beisert
2011-02-23  4:00   ` zoltan [this message]
2011-02-23  7:26     ` Juergen Beisert
2011-02-23 15:20     ` Juergen Beisert
2011-02-23 22:08     ` Juergen Beisert
2011-02-24  8:47       ` Zoltán Kócsi
2011-02-24 21:10 [PATCH] S3C24xx: NAND management changes to support booting from NAND Juergen Beisert
2011-02-24 21:10 ` [PATCH 2/2] mini2440: Consider correct NAND page size for boot Juergen Beisert

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=Pine.LNX.4.31.1102231440230.20973-100000@susu.bendor.com.au \
    --to=zoltan@bendor.com.au \
    --cc=barebox@lists.infradead.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