From: Joshua Wise <joshua@joshuawise.com>
To: linux-mtd@lists.infradead.org
Cc: Alice Hennessy <ahennessy@mvista.com>
Subject: Re: Different nand interface
Date: Thu, 23 Oct 2003 21:36:54 -0400 [thread overview]
Message-ID: <200310232136.58256.joshua@joshuawise.com> (raw)
In-Reply-To: <3F984931.E6409ED7@mvista.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> I need some advice on how to support a board that has a hardware state
> machine
> that creates a parallel bus style interface to the NAND chip. It is
> totally
> different from the standard 8 IO signal controls.
I'm not certain if this is what you're looking for, but the iPAQ h1910 has
NAND connected to the address pins. (Is this what you mean?) Take a look at
the NAND code in handhelds.org CVS (module linux/kernel26, I think, although
if h1910 flash is not an option there, try module linux/kernel) - it's just
standard MTD NAND, except with some changes not to do moronic caching of
IO_ADDR_R and IO_ADDR_W. (You can also look at the 1910 flash driver to see
how I change IO_ADDR_R/W based on ALE and CLE.)
/j
- --
Joshua Wise | www.joshuawise.com
GPG Key | 0xEA80E0B3
Quote | <lilo> I akilled *@* by mistake
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/mII5Pn9tWOqA4LMRAvDuAKCLJ0Oq1P9lJpvWdZFSEkR+scf0BACgkXI4
1A7evWeG40v8DYM8dsUI9nU=
=/6q9
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-10-24 1:38 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 [this message]
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
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=200310232136.58256.joshua@joshuawise.com \
--to=joshua@joshuawise.com \
--cc=ahennessy@mvista.com \
--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