All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Romero <xavinux@gmail.com>
To: Yi TZ Li <shliyi@cn.ibm.com>
Cc: Andrew Jeffery <andrew@aj.id.au>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: OpenBMC on Raspberry PI 3.
Date: Mon, 9 Oct 2017 13:09:10 -0300	[thread overview]
Message-ID: <CAEX+82LFjvc4=Ai6p4k66EBfE-45jrYUwvmPFGdgSb4OdzQVFA@mail.gmail.com> (raw)
In-Reply-To: <OF72E5748D.A94F82AF-ON482581B4.0033C44D-482581B4.003504C9@notes.na.collabserv.com>

[-- Attachment #1: Type: text/plain, Size: 4384 bytes --]

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!


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?

Thanks for your answers and kind attention.

Regards,




*Javier Romero*

*E-mail: xavinux@gmail.com <xavinux@gmail.com>*

*Skype: xavinux*


2017-10-09 6:39 GMT-03:00 Yi TZ Li <shliyi@cn.ibm.com>:

> Javier,
>
> Andrew has mentioned the cause of the bug.
>
> When I added the RaspberryPi configure to OpenBMC, I referred to
> configuration of other boards, like:
> "meta-openbmc-machines/meta-evb/meta-evb-aspeed/meta-evb-ast2500/conf",
> you might also refer to other working machines.
>
> The original target was to build an OpenBMC image for RaspberryPi, but I
> never tested 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.
>
> Thanks,
> -Yi
>
> > From: Andrew Jeffery <andrew@aj.id.au>
> > To: Javier Romero <xavinux@gmail.com>
> > Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
> > Date: 09/10/2017 02:41 PM
> > Subject: Re: OpenBMC on Raspberry PI 3.
> > Sent by: "openbmc" <openbmc-bounces+shliyi=cn.ibm.com@lists.ozlabs.org>
> >
> > On Sun, 2017-10-08 at 23:57 -0300, Javier Romero wrote:
> > > Andrew,
> > >
> > > Thans for your answer.
> > >
> > > Bug reported: https://github.com/openbmc/openbmc/issues/2434
> > >
> > > I`d like to try to cook up a patch, but do I need to know a specific
> > > language programming to do this ?
> >
> > Hmm, good question. This is probably a bug in how a bitbake
> > configuration/recipe configures the kernel. As such I'd suggest getting a
> > handle on Yocto, which is the build and configuration system we
> use.Here's the
>
> > quick start guide:
> >
> > http://www.yoctoproject.org/docs/2.1/yocto-project-qs/
> yocto-project-qs.html
> >
> > There's also a rather daunting Mega Manual, which is useful as a
> reference
> > (rather than reading the whole thing):
> >
> > http://www.yoctoproject.org/docs/2.1/mega-manual/mega-manual.html
> >
> > Back to the bug itself, from the output that you gave I expect it's some
> issue
> > with the following directive:
> >
> > https://github.com/openbmc/openbmc/blob/master/meta-phosphor/conf/
> > distro/openbmc-phosphor.conf#L57
> >
> > i.e. the issue is that that linux-raspberrypi (the kernel recipe used
> for the
> > raspberry pi[1][2]) doesn't have a 'phosphor-gpio-keys' feature. The
> implicit
> > assumption is that the configuration will be using the linux-obmc
> > tree[3][4][5], which
> > is our fork of the kernel (primarily for Aspeed SoC support).
> >
> > 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.
> >
> > Hope that helps.
> >
> > Andrew
> >
> > [1] https://github.com/openbmc/openbmc/blob/
> > 4f2d85233d23eedaf1d4846d3d861ba28bc49b00/import-layers/meta-
> > raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> > [2] https://github.com/openbmc/openbmc/blob/
> > 4f2d85233d23eedaf1d4846d3d861ba28bc49b00/import-layers/meta-
> > raspberrypi/recipes-kernel/linux/linux-raspberrypi.inc
> > [3] https://github.com/openbmc/openbmc/blob/
> > 4f2cddf103aaca6df26ddb766655fdf49c56a6ae/meta-phosphor/common/
> > recipes-kernel/linux/linux-obmc_4.10.bb
> > [4] https://github.com/openbmc/openbmc/blob/
> > 4f2cddf103aaca6df26ddb766655fdf49c56a6ae/meta-phosphor/common/
> > recipes-kernel/linux/linux-obmc.inc[attachment "signature.asc"
> > deleted by Yi TZ Li/China/IBM]
>
>

[-- Attachment #2: Type: text/html, Size: 8013 bytes --]

  reply	other threads:[~2017-10-09 16:09 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
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 [this message]
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+82LFjvc4=Ai6p4k66EBfE-45jrYUwvmPFGdgSb4OdzQVFA@mail.gmail.com' \
    --to=xavinux@gmail.com \
    --cc=andrew@aj.id.au \
    --cc=openbmc@lists.ozlabs.org \
    --cc=shliyi@cn.ibm.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.