From: Lennert Buytenhek <buytenh@wantstofly.org>
To: "Ruslan V. Sushko" <rsushko@ru.mvista.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] NAND Flash support for Intel IXP4xx platform
Date: Tue, 24 Apr 2007 12:49:30 +0200 [thread overview]
Message-ID: <20070424104930.GD1748@xi.wantstofly.org> (raw)
In-Reply-To: <462DDFEF.4070604@ru.mvista.com>
On Tue, Apr 24, 2007 at 02:46:07PM +0400, Ruslan V. Sushko wrote:
> >>The patch adds glue logic to support MTD for NAND flash devices on
> >>Intel IXP4xx based platform
> >
> >Hmm, the IXP4xx doesn't have an on-chip NAND controller, does it?
> >Is this for NAND flashes connected to the expansion bus? Maybe we
> >need something a la physmap for NAND flashes..
>
> Yes, It's true the NAND flash is connected to expansion bus. The driver
> has two parts: The common glue logic submitted here and the platform
> specific (evaluation board) definition submitted to
> http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=4323/2
> All maps defined in last patch
I wonder how much sense it makes to call this mtd driver "the
ixp4xx NAND flash driver" if there's hardly anything ixp4xx-specific
in it.
For that matter, I wonder how much sense it makes to submit a
separate NAND driver for every ARM SoC. For NOR flashes we have
physmap, we should have something similar for NAND.
next prev parent reply other threads:[~2007-04-24 10:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 10:29 [PATCH] NAND Flash support for Intel IXP4xx platform Ruslan V. Sushko
2007-04-20 8:25 ` Vitaly Wool
2007-04-20 14:16 ` Ruslan V. Sushko
2007-04-24 7:21 ` Vitaly Wool
2007-04-24 8:29 ` Ruslan V. Sushko
2007-04-24 8:34 ` Vitaly Wool
2007-04-24 10:33 ` Ruslan V. Sushko
2007-04-24 10:38 ` Lennert Buytenhek
2007-04-24 10:46 ` Ruslan V. Sushko
2007-04-24 10:49 ` Lennert Buytenhek [this message]
2007-04-24 10:53 ` Vitaly Wool
2007-04-24 11:01 ` Lennert Buytenhek
2007-04-24 11:10 ` Ruslan V. Sushko
2007-04-24 11:21 ` Vitaly Wool
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=20070424104930.GD1748@xi.wantstofly.org \
--to=buytenh@wantstofly.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rsushko@ru.mvista.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