From: David Woodhouse <dwmw2@infradead.org>
To: "J.D. Bakker" <bakker@thorgal.et.tudelft.nl>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Handling multiple NAND chips
Date: Fri, 25 Jul 2003 11:56:09 -0400 [thread overview]
Message-ID: <1059148567.28255.47.camel@lapdancer.baythorne.internal> (raw)
In-Reply-To: <a05200f01bb4700e6ff94@[130.161.115.44]>
On Fri, 2003-07-25 at 11:51, J.D. Bakker wrote:
> I have a two-hour old CVS; where should I look ?
The fact that select_chip() now takes a 'chip_number' argument, that
nand_scan() now takes a 'max_chips' argument and probes for up to that
many... next is to fix the read/write/erase functions to select the
_correct_ chip according to the address, etc.
> Does it *help* to have separate data/CLE/ALE ?
Probably not. What may help, and to be honest I won't be 100% sure till
we actually come to implement it, is having separate FR/B# so you can
happily poll for completion and leave multiple chips _busy_
independently.
--
dwmw2
next prev parent reply other threads:[~2003-07-25 15:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 15:12 Handling multiple NAND chips J.D. Bakker
2003-07-25 15:36 ` David Woodhouse
2003-07-25 15:51 ` J.D. Bakker
2003-07-25 15:56 ` David Woodhouse [this message]
2003-07-26 10:22 ` J.D. Bakker
2003-07-26 11:39 ` Thomas Gleixner
2003-07-26 15:08 ` David Woodhouse
2003-07-26 17:20 ` Thomas Gleixner
2003-07-26 15:06 ` David Woodhouse
2003-07-26 18:20 ` J.D. Bakker
2003-07-26 19:05 ` David Woodhouse
2003-07-27 12:54 ` J.D. Bakker
2003-07-27 13:42 ` David Woodhouse
2003-07-27 13:58 ` J.D. Bakker
2003-07-27 16:28 ` David Woodhouse
2003-07-25 15:51 ` David Woodhouse
2003-07-26 0:27 ` Charles Manning
2003-07-26 10:32 ` J.D. Bakker
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=1059148567.28255.47.camel@lapdancer.baythorne.internal \
--to=dwmw2@infradead.org \
--cc=bakker@thorgal.et.tudelft.nl \
--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 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.