public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Charles Manning <manningc2@actrix.gen.nz>
To: m.neiger@synergie-inf.com,
	"'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: 16 NANDS
Date: Tue, 7 Jan 2003 10:15:29 +1300	[thread overview]
Message-ID: <20030106211949.6211B45AF@tiger.actrix.co.nz> (raw)
In-Reply-To: <515CABE7496FD111AA3300201829FCBE2FFC48@archie.gsi.synergie-inf.com>

By this I expect you mean the NAND chips with a 16-bit wide interface.

There are really two sub-issues:
* Hook-up to the chips themselves (ie. doing x16 instead of x8 trasfers).
* The 16-bit wide chips have larger pages and blocks (2kB pages, 128kB 
blocks) than the previous generation stuff. This needs to be handled too at 
both the mtd and file system level. I believe (but don't quote me) that JFFS2 
will work as it is now. YAFFS is currently undergoing extensions/mods to 
support the larger pages/blocks.

-- Charles


On Fri, 03 Jan 2003 23:27, Marc Neiger wrote:
> Hi,
>
> what are the current status/plan regarding the use of 16 NAND Flash,
> including with JFFS2
>
> Cheers and happy new year,
> Marc Neiger
>
> Marc Neiger
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2003-01-06 20:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03 10:27 16 NANDS Marc Neiger
2003-01-06 21:15 ` Charles Manning [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-06 22:42 Marc Neiger
2003-01-06 23:03 ` Charles Manning
2003-01-07 19:04   ` Thomas Gleixner
2003-01-08  8:14     ` David Woodhouse
2003-01-08 20:23       ` Thomas Gleixner
2003-01-08 21:23 Marc Neiger
2003-01-08 22:03 ` Thomas Gleixner

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=20030106211949.6211B45AF@tiger.actrix.co.nz \
    --to=manningc2@actrix.gen.nz \
    --cc=linux-mtd@lists.infradead.org \
    --cc=m.neiger@synergie-inf.com \
    /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