From: Alessandro Rubini <rubini-list@gnudd.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] Nand driver for Nomadik SoC
Date: Mon, 9 Feb 2009 09:40:02 +0100 [thread overview]
Message-ID: <20090209084002.GA25194@mail.gnudd.com> (raw)
In-Reply-To: <200902090834.30653.sr@denx.de>
>> cpu/arm926ejs/nomadik/nand.c | 221++++++++++++++++++++++++++++++++++++++++
> This driver should go into drivers/mtd/nand instead.
I've seen a lot of nand.c in board directories and three of them in
cpu directories (cpu/arm920t/s3c24x0/nand.c
cpu/arm926ejs/nomadik/nand.c cpu/arm926ejs/davinci/nand.c), while
drivers/mtd/nand looked like generic code to me with a few exceptions.
If you confirm that all SoC-specific code is expected to go there over
time, I'll move it and resubmit.
/alessandro
next prev parent reply other threads:[~2009-02-09 8:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 4:43 [U-Boot] [PATCH] Nand driver for Nomadik SoC Alessandro Rubini
2009-02-07 15:04 ` [U-Boot] [PATCH v2] " Alessandro Rubini
2009-02-07 21:08 ` Jean-Christophe PLAGNIOL-VILLARD
2009-02-07 23:19 ` [U-Boot] [PATCH v3] " Alessandro Rubini
2009-02-09 7:34 ` Stefan Roese
2009-02-09 8:40 ` Alessandro Rubini [this message]
2009-02-09 8:48 ` Stefan Roese
2009-02-09 17:16 ` Scott Wood
2009-02-09 17:56 ` Alessandro Rubini
2009-02-09 18:10 ` Scott Wood
-- strict thread matches above, loose matches on Subject: below --
2009-02-09 14:53 [U-Boot] [PATCH 0/3] Drivers for nomadik 8815 board Alessandro Rubini
2009-02-09 14:53 ` [U-Boot] [PATCH 2/3] Nand driver for Nomadik SoC Alessandro Rubini
2009-02-09 21:48 ` Alessandro Rubini
2009-02-09 22:28 ` Scott Wood
2009-02-09 14:53 ` [U-Boot] [PATCH 1/3] Added nomadik.h header Alessandro Rubini
2009-02-09 14:53 ` [U-Boot] [PATCH 3/3] Enable Ethernet for Nomadik 8815 Evaluation Kit Alessandro Rubini
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=20090209084002.GA25194@mail.gnudd.com \
--to=rubini-list@gnudd.com \
--cc=u-boot@lists.denx.de \
/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.