From: Ben Dooks <ben@fluff.org.uk>
To: Deepak Saxena <dsaxena@plexity.net>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [RFC] Make physmap into a platform device driver...
Date: Tue, 3 Jan 2006 10:34:36 +0000 [thread overview]
Message-ID: <20060103103436.GA2152@home.fluff.org> (raw)
In-Reply-To: <20051229232138.GA32463@plexity.net>
On Thu, Dec 29, 2005 at 03:21:38PM -0800, Deepak Saxena wrote:
>
> I'm working on a system where I want to use the physmap driver
> but the size or buswidth of the flash device might change depending
> on the specific board layout. I want to be able to build a single kernel
> that boots on all boards using this NPU (IXP2350) and with the hardcoded
> approach to buswidth and such, it makes it rather impossible. On ARM
> platforms, we've been using the following data structure to pass
> board-specific flash information to the SOC-specific drivers and I
> am wondering if it makes sense to move it out of ARM into the generic
> MTD layer and have the physmap driver use it. The physmap driver
> could register itself as a platform driver for "phys-mtd" devices
> and boards would just fill in platform_device structure with the
> appropriate resource window and the needed fields below as the
> platform_data. We may want to trim down the structure to remove
> ARM-specific fields and let ARM have it's own structure that contains
> the generic structure as a member. Thoughts?
Several people have said they where going to modify the
plat-ram driver I wrote a while ago to support flash...
I think a number of the flash drivers currently in the
mtd system could be rolled into a generic mtd flash driver
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
next prev parent reply other threads:[~2006-01-03 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-29 23:21 [RFC] Make physmap into a platform device driver Deepak Saxena
2005-12-31 12:33 ` Mark Brown
2006-01-03 10:34 ` Ben Dooks [this message]
2006-01-05 21:09 ` Mark Brown
2006-01-11 17:36 ` Jared Hulbert
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=20060103103436.GA2152@home.fluff.org \
--to=ben@fluff.org.uk \
--cc=dsaxena@plexity.net \
--cc=linux-mtd@lists.infradead.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