From: Marcus Mikolaiczyk <m.mikolaiczyk@rac.de>
To: linux-mtd@lists.infradead.org
Subject: Patching only NAND specific stuff possible?
Date: Wed, 11 May 2005 10:25:58 +0200 [thread overview]
Message-ID: <4281C196.2010806@rac.de> (raw)
So again me with my SAMSUNG NAND.
Is it a possibility to patch only the NAND related stuff
driver/mtd/nand/*
include/linux/mtd/nand*
??*
to support new NAND features...
Considering the four Layers (jffs2,mtd,nand,hardware-drivers) it should
be possible onloy to 'update' the nand and hardware-drivers stuff.
Any objections to this?
A secondary short question, if you don't mind.
Where takes the 'addressing' of the NAND takes place (write Col,Row to ALE)?
On the Samsung K9F2G08... there are 5 Cycles for the address resolution
nescessary. And two for the command. Example Read page..
Command=0x00
Address=Col_addr(BIT 0-7)
Address=Col_addr(BIT 8-11)
Address=Row_addr(BIT 0-7)
Address=Row_addr(BIT 8-15)
Address=Row_addr(BIT 16)
CLE=0x30
Then read Data...
I saw some NAND chips which only have 4 Address Cycles.
Kind Regards Marcus
next reply other threads:[~2005-05-11 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 8:25 Marcus Mikolaiczyk [this message]
2005-05-11 21:46 ` Patching only NAND specific stuff possible? Thomas Gleixner
2005-05-12 5:13 ` Marcus Mikolaiczyk
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=4281C196.2010806@rac.de \
--to=m.mikolaiczyk@rac.de \
--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