public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: jasmine@linuxgrrls.org
To: linux-mtd@lists.infradead.org
Subject: Re: Handling multiple NAND chips -- take 2
Date: Wed, 25 Feb 2004 18:29:33 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0402251827300.29757@hex> (raw)
In-Reply-To: <1077731948.7826.792.camel@hades.cambridge.redhat.com>


On Wed, 25 Feb 2004, David Woodhouse wrote:

> On Wed, 2004-02-25 at 18:44 +0100, J.D. Bakker wrote:
> > This is the plan; fire at will.
> 
> Why? What'd poor Will do wrong? 

He's a no-good commie.

> I think that's acceptable. It's _definitely_ OK on NOR. On NAND we may
> be sharing some control lines between different chips, but I still think
> it's OK and we can deal with that in the board-level driver.

What if you have a board with an onboard NAND (for the OS) and a 
SmartMedia slot?  That's surprisingly common.  It's very difficult to buy 
consistent Smartmedia cards, too-  they often have different parts in 
them during a run.

> > chip = global_page_addr / pages_per_chip;
> > page = global_page_addr % pages_per_chip;
> 
> I think so. I prefer it to the other.

divide not shift?

-J.

  parent reply	other threads:[~2004-02-25 18:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25 17:44 Handling multiple NAND chips -- take 2 J.D. Bakker
2004-02-25 17:59 ` David Woodhouse
2004-02-25 18:06   ` Derek Jones
2004-02-25 18:29   ` jasmine [this message]
2004-02-25 19:35     ` J.D. Bakker
2004-02-25 20:46       ` Thomas Gleixner
2004-02-25 19:19   ` J.D. Bakker
2004-02-25 20:22 ` Thomas Gleixner
2004-02-26  7:54   ` David Woodhouse

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.58.0402251827300.29757@hex \
    --to=jasmine@linuxgrrls.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