OpenBMC on Raspberry PI 3.

[Andrew Jeffery]

Hi Javier,

A few notes on how to make best use of the mailing list:

First, mail to the list is best sent plain-text. I see you use gmail -
if you're using the web interface there's a drop-down menu at the
bottom right of the composer where you can select the plain-text
option.

Secondly, I notice you quote both Yi and I below in your reply, and
appear to have constructed the reply yourself: the best way to deal
with multiple people in a conversation is to reply to their emails
individually and directly, rather than consolidating your thoughts in
one reply. This keeps the threads of conversation easy to follow
(though gmail's conversation interface is linear rather than tree view,
so this might not be obvious but it does affect others reading the
list).

Third: You have the knack of replying to quotes from the sender, but
this is best served by making use of the reply-indentation that your
composer should already provide (e.g. '> some quoted text'). For
example what I'm doing below:

On Mon, 2017-10-09 at 13:09 -0300, Javier Romero wrote:
> Andrew,
> 
> "More generally, knowledge of Python (Yocto/bitbake, some OpenBMC
> userspace), C (u-boot, kernel, qemu, also requires a some comfort
> with assembler) and C++ (most of the phosphor reference userspace
> applications) is useful."
> 
> I see, but I'm not a programmer, have start by building an image of
> Yocto for the Raspberry PI to learn more about Yocto, Poky and
> bitbake. Links you provided are very welcome and useful!

Ah - so I don't think you've outlined why you picked OpenBMC for the
job. Can you give us a quick run-down?

Without further information and assuming you just want to get an image
you've built with Yocto onto a Raspberry Pi, there appears to be a good
unofficial how-to here:

http://www.jumpnowtek.com/rpi/Raspberry-Pi-Systems-with-Yocto.html

This should get you something that works without having to deal with
any of the broken assumptions currently baked into the OpenBMC code-
base with respect to the Raspberry Pi.

> 
> 
> Yi,
> 
> "The original target was to build an OpenBMC image for RaspberryPi,
> but I never tested on a real hardware.
> 
> I've the Raspberry PI 3 at disposal for testing on a real hardware.
> 
> More work is required to run OpenBMC on a Raspberry Pi. The "meta-
> phosphor" layer has been changed since that time, we need to update
> RaspberryPi configurations accordingly."
> 
> Something I can help and with this although Im not a programmer? 

Not already having programming experience is going to make it harder,
and I wouldn't necessarily take queues from how we use Yocto (I'm no
expert but I feel that we don't do some things quite by the book).

Yocto borrows lots of ideas from shell scripting and is implemented in
python. Further, it allows you to pretty freely mix the two in recipes
thus it would be helpful to get a grasp of these environments (and
Yocto itself). Without some experience it leaves us with high latency
interactions between you and Yi if Yi is to continue developing the
Raspberry Pi support. I expect this will end up frustrating both of
you, but it's up to you both to decide.

There are going to be easier projects out there than OpenBMC to cut
your teeth with, but if you are keen to learn to program, feel you have
the drive to do so and Yi is happy to help out with your interest in
the Raspberry Pi then by all means stick around :)

Andrew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20171010/5a052e45/attachment.sig>