From: Mason <slash.tmp@free.fr>
To: linux-mtd <linux-mtd@lists.infradead.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Sebastian Frias <sf84@laposte.net>
Subject: Using a generic upstream driver with a custom NAND controller
Date: Tue, 19 Jan 2016 20:30:50 +0100 [thread overview]
Message-ID: <569E8EEA.6060106@free.fr> (raw)
Hello,
I'm porting a 3.4 kernel to a 4.4 kernel, and I'm having a hard time
with the NAND driver, because it made changes to "core" files, and
these core files have possibly changed a lot between the 20 releases.
drivers/mtd/Kconfig | 3 +-
drivers/mtd/chips/cfi_cmdset_0002.c | 127 ++-
drivers/mtd/devices/m25p80.c | 100 +-
drivers/mtd/maps/Kconfig | 11 +-
drivers/mtd/maps/physmap.c | 195 ++++
drivers/mtd/mtdchar.c | 54 ++
drivers/mtd/nand/Kconfig | 8 +
drivers/mtd/nand/Makefile | 1 +
drivers/mtd/nand/nand_base.c | 6 +-
drivers/mtd/nand/nand_ids.c | 18 +
drivers/mtd/nand/foobar_nand.c | 1903 ++++++++++++++++++++
I assume a regular driver is not supposed to make changes to
(some of) these core files?
As far as I understand, the NAND controller is custom (it's not a
hardware IP block sold to SoC manufacturers) but I think there is
some kind of standard (ONFI?) that all controllers adhere to?
(Kind of like USB has generic EHCI.)
Is there some generic driver upstream that I could try to see if
it works with this controller?
Note: the SoC is using these chips:
nand: Micron NAND 512MiB 3,3V 8-bit
nand: 512MiB, SLC, page size: 2048, OOB size: 64
Regards.
next reply other threads:[~2016-01-19 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 19:30 Mason [this message]
2016-01-19 21:15 ` Using a generic upstream driver with a custom NAND controller Steve deRosier
2016-01-21 14:05 ` Mason
2016-01-21 14:12 ` David Woodhouse
2016-01-21 14:44 ` Mason
2016-01-22 9:29 ` Ricard Wanderlof
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=569E8EEA.6060106@free.fr \
--to=slash.tmp@free.fr \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=sf84@laposte.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.