From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Valentine Barshak <vbarshak@ru.mvista.com>
Cc: linuxppc-dev@ozlabs.org, tglx@linutronix.de, sr@denx.de,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH 0/2] PowerPC: Add 44x NDFC device-tree aware support
Date: Fri, 26 Oct 2007 13:50:03 -0500 [thread overview]
Message-ID: <20071026135003.257b82bd@weaponx.rchland.ibm.com> (raw)
In-Reply-To: <20071026163058.GA11354@ru.mvista.com>
On Fri, 26 Oct 2007 20:30:58 +0400
Valentine Barshak <vbarshak@ru.mvista.com> wrote:
> I've worked in parallel with Stefan Roese on the new OF NDFC support.
> This version (as well as Stefan's) is based on the original NDFC driver by Thomas Gleixner.
> The major difference is that the original implements each chip connected NDFC banks as a
> separate MTD device. Here I try to have one MTD device spread on all chips found.
> However, the chips should have equal ID's and sizes, but I've never seen several different
> chips attached to single ndfc.
Hm. Why did you do that? It adds restrictions to the driver that
really don't need to be present. If people want a single MTD device
across multiple chips, they can use mtdconcat.
Remember, just because you've never seen something, doesn't mean it
doesn't exist. Bamboo even has two different sized NAND chips
hooked to the NDFC, IIRC.
josh
next prev parent reply other threads:[~2007-10-26 18:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 16:30 [PATCH 0/2] PowerPC: Add 44x NDFC device-tree aware support Valentine Barshak
2007-10-26 16:39 ` [PATCH 1/2] " Valentine Barshak
2007-10-27 3:37 ` Stephen Rothwell
2007-10-27 4:53 ` Stefan Roese
2007-10-27 8:46 ` Thomas Gleixner
2007-10-26 16:41 ` [PATCH 2/2] PowerPC: NDFC entry for PowerPC 440EPx Sequoia DTS Valentine Barshak
2007-10-26 16:54 ` Sergei Shtylyov
2007-10-26 17:47 ` [PATCH] PowerPC: 44x device-tree aware NDFC bindings Valentine Barshak
2007-10-26 18:50 ` Josh Boyer [this message]
2007-10-26 21:37 ` [PATCH 0/2] PowerPC: Add 44x NDFC device-tree aware support Thomas Gleixner
2007-10-27 4:42 ` Stefan Roese
2007-10-29 15:19 ` Valentine Barshak
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=20071026135003.257b82bd@weaponx.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sr@denx.de \
--cc=tglx@linutronix.de \
--cc=vbarshak@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;
as well as URLs for NNTP newsgroup(s).