public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb•de>
To: linuxppc-dev@ozlabs•org
Cc: Martyn Welch <martyn.welch@gefanuc•com>,
	Murali N Iyer <mniyer@us•ibm.com>,
	Milton Miller <miltonm@bga•com>
Subject: Re: [PATCH] powerpc: Add support to access the flash on SLOF based systems
Date: Mon, 12 Jan 2009 18:29:57 +0100	[thread overview]
Message-ID: <200901121829.58489.arnd@arndb.de> (raw)
In-Reply-To: <496B784C.5010800@gefanuc.com>

On Monday 12 January 2009, Martyn Welch wrote:
> Adrian Reber wrote:
> > The reason why I did not use mtd is that part of the flash is used by
> > the firmware image and I do not know if that works with mtd, if only a
> > part of the flash can be used. SLOF does also a "CRC" check over the
> > firmware image, so that image must have valid SLOF "CRC". The flash is
> > a direct mapped flash, but the size of the firmware can vary.
>
> It can. MTD can create "partitions" within the flash, for an example
> see lines 84-110 of arch/powerpc/bootdts/sbc8641d.dts (http://tinyurl.com/7k2kym) 
> 
> Partitions can also be labeled as read-only, I guess the CRC could be
> checked from userspace as necessary. 

Murali has also done a modified firmware for experiments in the past where
he added the device tree entry for the flash on a PxCAB. As I recall, he did
not see any problems with that.

	Arnd <><

      reply	other threads:[~2009-01-12 17:30 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
2009-01-12 17:05     ` Martyn Welch
2009-01-12 17:29       ` Arnd Bergmann [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=200901121829.58489.arnd@arndb.de \
    --to=arnd@arndb$(echo .)de \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=martyn.welch@gefanuc$(echo .)com \
    --cc=miltonm@bga$(echo .)com \
    --cc=mniyer@us$(echo .)ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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