From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Cyril Bur <cyrilbur@gmail.com>, Joel Stanley <joel@jms.id.au>,
Xo Wang <xow@google.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: libflash questions mostly relating to P9 bringup
Date: Tue, 11 Oct 2016 19:10:48 +1100 [thread overview]
Message-ID: <1476173448.2654.7.camel@kernel.crashing.org> (raw)
In-Reply-To: <1476171942.720.16.camel@gmail.com>
On Tue, 2016-10-11 at 18:45 +1100, Cyril Bur wrote:
> > Hacky. Not really supported.
>
> I should apologise, if we're talking about https://github.com/open-powe
> r/skiboot/blob/master/external/pflash/powerpc_io.c, we shouldn't. That
> code isn't used anymore and I doubt it will work. I'll send patches to
> remove it!
>
> Currently updating PNOR from the host, Joel is correct, it isn't really
> supported by openbmc. Of course it can be done through /dev/mtd exposed
> by host linux (https://github.com/open-power/linux/blob/master/drivers/
> mtd/devices/powernv_flash.c) and backed by a driver in skiboot. I
> really hope that all pflash binaries around today know how to do this.
I dont know if that was mentioned earlier in the thread but we are
working on a mailbox based protocol for flash access to avoid accessing
the flash controller registers from any other entity than the BMC, in
order to be able to cut off the iLPC->AHB backdoor completely.
This should support having the flash either access directly for reads
or via an in-memory image in the BMC (aka memboot) and writes will be
done to an in-memory window on the LPC and "committed" to flash via
mbox commands.
We can get you details when we have a bit more sorted out on our side,
hopefully in a few days.
Cheers,
Ben.
next prev parent reply other threads:[~2016-10-11 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 1:41 libflash questions mostly relating to P9 bringup Xo Wang
2016-10-11 6:55 ` Joel Stanley
2016-10-11 7:45 ` Cyril Bur
2016-10-11 8:10 ` Benjamin Herrenschmidt [this message]
[not found] ` <1476910490-21190-1-git-send-email-brendanhiggins@google.com>
2016-10-20 18:53 ` Fwd: " Brendan Higgins
[not found] ` <1476922514.2654.182.camel@kernel.crashing.org>
[not found] ` <CAFd5g47a99CP9750y4PLs3WsURRrBLHwfOCVKU_iM3yBomCk=Q@mail.gmail.com>
[not found] ` <1476997560.2654.208.camel@kernel.crashing.org>
2016-10-25 22:32 ` Brendan Higgins
2016-10-11 23:50 ` Cyril Bur
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=1476173448.2654.7.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=cyrilbur@gmail.com \
--cc=joel@jms.id.au \
--cc=openbmc@lists.ozlabs.org \
--cc=xow@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.