From: Sean MacLennan <smaclennan@pikatech.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] MTD for Taco
Date: Wed, 16 Jan 2008 18:51:06 -0500 [thread overview]
Message-ID: <478E986A.1090405@pikatech.com> (raw)
In-Reply-To: <20080116173421.4c886514@zod.rchland.ibm.com>
Josh Boyer wrote:
> On Wed, 16 Jan 2008 16:25:23 -0500
> Sean MacLennan <smaclennan@pikatech.com> wrote:
>
>
>> Sean MacLennan wrote:
>>
>>> How about adding a config option that lets you specify 8 bit access?
>>> Something like CONFIG_NDFC_8BIT_ACCESS. We could default it to no and
>>> put a little blurb that says something like:
>>>
>>> On some platforms the 32bit read/writes cause a machine access
>>> exception. If you get a machine access exception while reading the NAND
>>> bad block table, try turning on 8 bit access.
>>>
>>>
>> I know it would be better if 32 bit access just worked, but nobody
>> actively objected to this idea, so here is a patch ;)
>>
>
> I'm objecting, but not on the bit access reasons :).
>
> 1) Needs to go to the linux-mtd@lists.infradead.org list with the
> maintainer CC'd (Thomas Gleixner)
>
Ok.
> 2) I don't want this driver enabled in mainline for boards in
> arch/powerpc until it fully understands how to parse device trees.
>
Fair enough. I thought it would be better to have a driver that compiles
and is usable for arch/powerpc, even if not quite correct. We (PIKA) are
going to be using a NAND flash, so we need the ndfc driver working. But
I can understand wanting it "right" before you put it in the kernel.
Cheers,
Sean
prev parent reply other threads:[~2008-01-16 23:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 5:17 [PATCH] MTD for Taco Sean MacLennan
2008-01-05 9:41 ` Stefan Roese
2008-01-05 12:25 ` David Gibson
2008-01-06 3:20 ` Sean MacLennan
2008-01-06 3:44 ` David Gibson
2008-01-05 18:20 ` Sean MacLennan
2008-01-05 19:19 ` Arnd Bergmann
2008-01-09 18:05 ` Sean MacLennan
2008-01-09 18:42 ` Josh Boyer
2008-01-09 18:50 ` Sean MacLennan
2008-01-09 19:04 ` Josh Boyer
2008-01-14 4:55 ` Sean MacLennan
2008-01-14 8:44 ` Josh Boyer
2008-01-14 17:32 ` Sean MacLennan
2008-01-14 19:42 ` Stefan Roese
2008-01-14 20:04 ` Sean MacLennan
2008-01-15 5:15 ` Stefan Roese
2008-01-15 6:30 ` Sean MacLennan
2008-01-15 6:39 ` Stefan Roese
2008-01-15 18:22 ` Sean MacLennan
2008-01-16 21:25 ` Sean MacLennan
2008-01-16 23:34 ` Josh Boyer
2008-01-16 23:51 ` Sean MacLennan [this message]
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=478E986A.1090405@pikatech.com \
--to=smaclennan@pikatech.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
/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).