From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: linux-mtd@lists.infradead.org
Cc: "Jörn Engel" <joern@logfs.org>, "Jamie Lokier" <jamie@shareable.org>
Subject: Re: CFI-0002 NOR flash blocking CPU on status register reads
Date: Tue, 10 Jun 2008 15:48:40 +0200 [thread overview]
Message-ID: <200806101548.40059.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <20080610130945.GB28565@shareable.org>
> Won't the CPU read the initial boot instructions from this
> flash, get programming status bytes instead of CPU
> instructions, and thus get confused?
The bootloader could/should make sure that every block is in the
correct state for Linux.
next prev parent reply other threads:[~2008-06-10 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 13:09 CFI-0002 NOR flash blocking CPU on status register reads Jamie Lokier
2008-06-10 13:48 ` Holger Schurig [this message]
2008-06-10 13:59 ` Jamie Lokier
2008-06-10 13:52 ` Jamie Lokier
2008-06-10 17:18 ` Trent Piepho
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=200806101548.40059.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=jamie@shareable.org \
--cc=joern@logfs.org \
--cc=linux-mtd@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