From: Stefan Roese <sr@denx.de>
To: Valentine Barshak <vbarshak@ru.mvista.com>
Cc: linuxppc-dev@ozlabs.org, Thomas Gleixner <tglx@linutronix.de>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH 0/2] PowerPC: Add 44x NDFC device-tree aware support
Date: Sat, 27 Oct 2007 06:42:53 +0200 [thread overview]
Message-ID: <200710270642.54171.sr@denx.de> (raw)
In-Reply-To: <alpine.LFD.0.9999.0710262316590.3186@localhost.localdomain>
Hi Valentine,
On Friday 26 October 2007, Thomas Gleixner wrote:
> On Fri, 26 Oct 2007, Valentine Barshak wrote:
> > 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.
>
> Bamboo has 2 different nand chips.
Right. This was my first thought after seeing your mail too.
> And I'm aware of another board
> which has a 2k-page onboard NAND and sockets for SmartMedia /
> PictureXd cards, which will simply break with your design.
>
> Restricting stuff for no good reason is never a good idea.
Add my voice here too.
> mtdconcat can build you a big one if you want, so why adding
> restrictions to a driver ?
>
> > I'm adding ndfc_of as a separate file, since some other changes
> > have also been made (e.g. all i/o is made with ndfc_readl/writel inline
> > functions).
>
> This should be done in the original ndfc driver and not in a separate
> incarnation.
Right. And I always thought it would be a good idea to switch to using the
in_be32() functions and friends for IO access in this driver too.
Best regards,
Stefan
next prev parent reply other threads:[~2007-10-27 4:49 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 ` [PATCH 0/2] PowerPC: Add 44x NDFC device-tree aware support Josh Boyer
2007-10-26 21:37 ` Thomas Gleixner
2007-10-27 4:42 ` Stefan Roese [this message]
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=200710270642.54171.sr@denx.de \
--to=sr@denx.de \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--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).