From: Javier Romero <xavinux@gmail.com>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: Rick Altherr <raltherr@google.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: OpenBMC on Raspberry PI 3.
Date: Fri, 6 Oct 2017 20:02:08 -0300 [thread overview]
Message-ID: <CAEX+82KLmByCXqVg1Hzi7r5-cH2=Cx-0OE_hLwx-Jr_XXfe1Wg@mail.gmail.com> (raw)
In-Reply-To: <1507325323.1545468.1130544088.6FEEF44B@webmail.messagingengine.com>
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
Rick / Andrew,
Thank you very much for your answer and suggestions.
I'm looking at that repository on Github now.
Regards,
*Javier Romero*
*E-mail: xavinux@gmail.com <xavinux@gmail.com>*
*Skype: xavinux*
2017-10-06 18:28 GMT-03:00 Andrew Jeffery <andrew@aj.id.au>:
>
>
> On Sat, 7 Oct 2017, at 03:29, Rick Altherr wrote:
> > When you run export TEMPLATECONF=meta-openbmc-machines/meta-
> > openpower/meta-ibm/meta-palmetto/conf, you are telling the build system
> > that you want to build images for the BMC processor used on the Palmetto
> > machine (Aspeed AST2400). That image won't boot on a RaspberryPi. What
> > you'll need to do is create a new layer in meta-openbmc-machines for a
> > RaspberryPi that includes the raspberrypi layer, specifies the correct
> > kernel device tree, etc.
>
> As a heads-up, some of this work has already been done:
>
> https://github.com/openbmc/openbmc/tree/master/meta-
> openbmc-machines/meta-evb/meta-evb-raspberrypi/conf
>
> It was added in this change:
>
> https://gerrit.openbmc-project.xyz/#/c/508/
>
> I don't think it was thoroughly tested and it has probably bit-rotted,
> but maybe it's existence will flatten out the learning curve a bit.
>
> Cheers,
>
> Andrew
>
[-- Attachment #2: Type: text/html, Size: 2704 bytes --]
next prev parent reply other threads:[~2017-10-06 23:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 15:38 OpenBMC on Raspberry PI 3 Javier Romero
2017-10-06 16:59 ` Rick Altherr
2017-10-06 21:28 ` Andrew Jeffery
2017-10-06 23:02 ` Javier Romero [this message]
2017-10-08 4:45 ` Javier Romero
2017-10-08 12:44 ` Andrew Jeffery
2017-10-09 2:57 ` Javier Romero
2017-10-09 6:41 ` Andrew Jeffery
2017-10-09 9:39 ` Yi TZ Li
2017-10-09 16:09 ` Javier Romero
2017-10-10 0:14 ` Andrew Jeffery
2017-10-10 14:01 ` Javier Romero
2017-10-11 3:05 ` Andrew Jeffery
2017-10-11 19:09 ` Javier Romero
2017-10-13 4:56 ` Andrew Jeffery
2017-10-13 14:02 ` Javier Romero
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='CAEX+82KLmByCXqVg1Hzi7r5-cH2=Cx-0OE_hLwx-Jr_XXfe1Wg@mail.gmail.com' \
--to=xavinux@gmail.com \
--cc=andrew@aj.id.au \
--cc=openbmc@lists.ozlabs.org \
--cc=raltherr@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.