public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <gleixner@autronix.de>
To: Radu Corlan <rcorlan@pcnet.ro>, linux-mtd@lists.infradead.org
Cc: Joerg Zastrau <dl1bku@amsat.org>
Subject: Re: Support for parallel access in nand chips
Date: Tue, 26 Feb 2002 00:58:52 +0100	[thread overview]
Message-ID: <0202260058520I.03406@thomas> (raw)
In-Reply-To: <Pine.LNX.4.10.10202260121390.701-100000@pinot.profis.ro>

On Tuesday, 26. February 2002 07:30, Radu Corlan wrote:
> On our application (a PPC405 embedded system), we use two TC58256 NAND
> chips conected on a 16-bit bus. we designed it this way in order to
> increase the read/write speed - it would double our bandwidth. The
> problem, of course, is that nand.c only accesses the flash 8 bits at a
> time.
>
> We intend to hack nand.c to use the 16-bit access (and make a special
> entry in nand_chip with a double erase_size), but i'd like to know if
> anybody thought of supporting the parallel access.
No. 
But please don't hack nand.c. Build a nand16.c from nand.c and hack this. 
Else we get a mess in the code, which was cleaned up a few days ago :)
And a lot of overhead of 8/16bit decisions. You just have to provide the same 
functionality as nand.c. You will not need a special entry in nand_chip. The 
information there is enough. 

-- 
Thomas
__________________________________________________
Thomas Gleixner, autronix automation GmbH
auf dem berg 3, d-88690 uhldingen-muehlhofen
fon: +49 7556 919891 , fax: +49 7556 919886
mail: gleixner@autronix.de, http://www.autronix.de  

  reply	other threads:[~2002-02-25 23:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10202252006450.731-100000@pinot.profis.ro>
2002-02-25 18:44 ` problem in nand.c v 1.16 Thomas Gleixner
2002-02-26  6:21   ` Radu Corlan
2002-02-26  6:30   ` Support for parallel access in nand chips Radu Corlan
2002-02-25 23:58     ` Thomas Gleixner [this message]
2002-02-26  8:26       ` Radu Corlan
2002-02-26  1:25         ` David Woodhouse
2002-02-26 20:24           ` Radu Corlan
2002-02-26 13:45             ` Thomas Gleixner
2002-02-26 21:11               ` Radu Corlan
2002-02-27  0:46               ` nftl problem Radu Corlan
2002-02-26 18:03                 ` Thomas Gleixner
2002-02-27  1:30                   ` Radu Corlan
2002-02-26 18:37                     ` Thomas Gleixner
2002-02-27  1:42                       ` Radu Corlan
2002-02-27  2:00                       ` Radu Corlan
2002-02-26 19:10                         ` Thomas Gleixner
2002-02-26 18:12                 ` David Woodhouse
2002-02-27  1:37                   ` Radu Corlan
2002-02-26 18:57                     ` 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=0202260058520I.03406@thomas \
    --to=gleixner@autronix.de \
    --cc=dl1bku@amsat.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rcorlan@pcnet.ro \
    /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