From: Alice Hennessy <ahennessy@mvista.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Different nand interface
Date: Mon, 27 Oct 2003 12:43:48 -0800 [thread overview]
Message-ID: <3F9D8384.ABC9FD4@mvista.com> (raw)
In-Reply-To: 1067284806.16241.2.camel@imladris.demon.co.uk
David Woodhouse wrote:
> On Mon, 2003-10-27 at 10:25 -0800, Alice Hennessy wrote (modulo newlines):
> > Yes, I am looking at the current code which is more modular so it
> > gives me hope.
> > There are 2 nand chips on the board. If you want to read from the
> > 0x100th byte on chip 1 you need to do readb(chip1_base + 0x100); if
> > you want to write the 0x10000th byte on chip 2 you need to do
> > writeb(chip2_base + 0x10000,bytedata).
> > The chips are 16M X 8 bit and are mapped in a contiguous 32 M byte
> > memory space with 0-16M for chip1 and 16-32M for chip2.
>
> That's weird. How are the out-of-band areas accessed? How do you send
> commands like READ_ID and ERASE?
>
> --
> dwmw2
The hardware logic uses register access for special commands. Readid,
status does
2 writes to a register, one for address (to distinquish which flash), one for
command and one more
to read. Erase takes 2 writes to a register, address then command. The
out-of-band access
uses a register to give a command and then the out-of-band data is read using
readb with offset.
Alice
next prev parent reply other threads:[~2003-10-27 20:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 21:33 Different nand interface Alice Hennessy
2003-10-24 1:36 ` Joshua Wise
2003-10-24 7:39 ` David Woodhouse
2003-10-24 7:41 ` David Woodhouse
2003-10-27 18:25 ` Alice Hennessy
2003-10-27 20:00 ` David Woodhouse
2003-10-27 20:43 ` Alice Hennessy [this message]
2003-10-27 20:55 ` David Woodhouse
2003-10-27 21:17 ` Alice Hennessy
2003-10-27 22:29 ` David Woodhouse
2003-11-12 0:49 ` Alice Hennessy
2003-11-18 22:26 ` Alice Hennessy
2003-10-25 7:29 ` Charles Manning
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=3F9D8384.ABC9FD4@mvista.com \
--to=ahennessy@mvista.com \
--cc=dwmw2@infradead.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