linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Reber <adrian@lisas.de>
To: Milton Miller <miltonm@bga.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] powerpc: Add support to access the flash on SLOF based systems
Date: Wed, 14 Jan 2009 16:56:02 +0100	[thread overview]
Message-ID: <20090114155602.GA19277@lisas.de> (raw)
In-Reply-To: <6550a303b71331432a805ad98ca38103@bga.com>

On Mon, Jan 12, 2009 at 09:51:23AM -0600, Milton Miller wrote:
> Is SLOF just exposing the user image part of the flash device?  Or is it 
> the raw flash device?

SLOF is exposing the raw flash device.

> I need to keep this quick, but am intrested in a few more details.  My  
> first reaction is its yet another random misc-device, but I confess to  
> having written one for internal consumption.  But as a misc device it  
> will need to go through lkml review to be merged.

I had a look at mtd and it was pretty easy to get it to do the same
thing as my misc-device was doing with only 5 lines changed in
drivers/mtd/maps/physmap_of.c

So thanks for pointing me in that direction. What would be now the best
way to include the SLOF flash properly into the mtd driver?

Should I add additional code to physmap_of.c to detect the flash and
then use a hardcoded layout for the partition? Because SLOF is missing
all the necessary properties in the flash device node. Or should I add
the missing properties in prom_init.c in a fixup_device_tree_slof()
function? Both versions would lead to the same result but I am unsure
about which approach is the better one.

		Adrian

  reply	other threads:[~2009-01-14 15:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-10 15:31 [PATCH] powerpc: Add support to access the flash on SLOF based systems Adrian Reber
2009-01-10 17:52 ` Milton Miller
2009-01-10 19:50   ` Adrian Reber
2009-01-12 15:51     ` Milton Miller
2009-01-14 15:56       ` Adrian Reber [this message]
2009-01-12 17:05     ` Martyn Welch
2009-01-12 17:29       ` Arnd Bergmann

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=20090114155602.GA19277@lisas.de \
    --to=adrian@lisas.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=miltonm@bga.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).