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 12:03:48 +1300 [thread overview]
Message-ID: <20030106230808.9E85F439D@tiger.actrix.co.nz> (raw)
In-Reply-To: <515CABE7496FD111AA3300201829FCBE3552DD@archie.gsi.synergie-inf.com>
I believe Thomas has this on his TBD list, but - like everyone - he is rather
busy so it might take a while before this comes to the top of his priority
list.
Hey why not give it a shot? One way to get experience is to just jump in
(especially on something like this which looks relatively simple). There are
many nice people in mtd land who will provide support.
-- CHarles
On Tue, 07 Jan 2003 11:42, Marc Neiger wrote:
> Hi Charles,
>
> Of course you properly understood I forgot to type "16bits wide".
>
> I was thinking about products such as Samsung K9F5616U0B wich is a 256Mbit
> NAND flash. Page size is 512 + 16 OOB bytes. So the problem is just
> regarding the data transfer width as the page size are the same as the
> already supported chips/architectures. Moreover it is quite complicated as
> the commands and addresses are still transfered as 8 bits, only data are
> transfered as 16bits.
>
> However, as a newcomer in the embbeded linux world, and although I feel
> like it should be quite simple, I don't feel like doing the software
> modification myself...
>
> Cheers,
> Marc Neiger
>
> > -----Message d'origine-----
> > De : Charles Manning [mailto:manningc2@actrix.gen.nz]
> > Envoyé : lundi 6 janvier 2003 22:15
> > À : m.neiger@synergie-inf.com; 'linux-mtd@lists.infradead.org'
> > Objet : Re: 16 NANDS
> >
> >
> > 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/
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2003-01-06 22:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 22:42 16 NANDS Marc Neiger
2003-01-06 23:03 ` Charles Manning [this message]
2003-01-07 19:04 ` Thomas Gleixner
2003-01-08 8:14 ` David Woodhouse
2003-01-08 20:23 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2003-01-08 21:23 Marc Neiger
2003-01-08 22:03 ` Thomas Gleixner
2003-01-03 10:27 Marc Neiger
2003-01-06 21:15 ` 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=20030106230808.9E85F439D@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