linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel.crashing.org>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: mtd maps
Date: Tue, 15 Mar 2005 13:32:31 -0700	[thread overview]
Message-ID: <20050315133231.A5861@cox.net> (raw)
In-Reply-To: <42372CF0.6040901@mvista.com>; from mgreer@mvista.com on Tue, Mar 15, 2005 at 11:44:00AM -0700

On Tue, Mar 15, 2005 at 11:44:00AM -0700, Mark A. Greer wrote:
> Greg Weeks wrote:
> 
> > Are mtd maps still in drivers/mtd/maps or has that all moved to the 
> > platform code? I have an mtd map for the mpc8560ads but it's in mtd/maps.
> 
> 
> The mtd code has changed so that platform code can get at the routines 
> to set up the maps from there.  arch/ppc/platforms/katana.c has its mtd 
> maps there and I recently posted a patch that moves it for the chestnut 
> as well.
> 
> I think its a good idea to move them to the platform code since the mtd 
> maps are platform specific anyway.  Plus its one less place to add/edit 
> a file.  But that's just my $0.02...

But keep in mind that this currently only applies in the case where
you need to map chips of the same type. Some boards have multiple
chip types and physmap doesn't yet support that.

-Matt

  reply	other threads:[~2005-03-15 20:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-15 12:22 mtd maps Greg Weeks
2005-03-15 18:44 ` Mark A. Greer
2005-03-15 20:32   ` Matt Porter [this message]
2005-03-16  1:33     ` Josh Boyer
2005-03-21 12:38       ` Jörn Engel

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=20050315133231.A5861@cox.net \
    --to=mporter@kernel.crashing.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=mgreer@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).