From: Patrick Williams <patrick@stwcx.xyz>
To: Cheng Yang <cyang999@apple.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: Difficulty booting on Raspberry Pi 4.
Date: Wed, 23 Sep 2020 19:10:55 -0500 [thread overview]
Message-ID: <20200924001055.GW6152@heinlein> (raw)
In-Reply-To: <CDC90A55-957D-47BB-9B42-4283BB6706AF@apple.com>
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
On Wed, Sep 23, 2020 at 10:36:03AM -0700, Cheng Yang wrote:
> Hi, I’m openbmc noob here.
Welcome.
> I follow the instruction of https://github.com/openbmc/openbmc/blob/master/meta-raspberrypi/README.md <https://github.com/openbmc/openbmc/blob/master/meta-raspberrypi/README.md>
I don't think there are really many people using the meta-raspberrypi
with OpenBMC. This comes from elsewhere outside the project as one of
the Yocto community meta-layers and isn't related to OpenBMC.
What happened was that someone had an idea to use a rpi as an
easily-accessible experimental platform for running OpenBMC code and
they asked to have the meta-layer added to our tree. We keep it in
sync, but I don't think that experiment really went much farther.
See https://github.com/openbmc/openbmc/issues/399 for some of the
origin.
If you're doing just a simple rpi4 image build, without any of the
OpenBMC layers, and it won't even boot, that seems like something you
could tackle with the upstream community. The README suggests that
the general Yocto mailing list is where to go:
```
* Mailing list (yocto mailing list): <yocto@yoctoproject.org>
```
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-24 0:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 17:36 Difficulty booting on Raspberry Pi 4 Cheng Yang
2020-09-24 0:10 ` Patrick Williams [this message]
2020-09-24 0:34 ` Cheng Yang
[not found] ` <CACWQX831sTH1Mp5nZEo+_bs2pCgz9ovspXD9onqiHCgAs=vciw@mail.gmail.com>
2020-09-24 1:05 ` Ed Tanous
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=20200924001055.GW6152@heinlein \
--to=patrick@stwcx.xyz \
--cc=cyang999@apple.com \
--cc=openbmc@lists.ozlabs.org \
/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.