openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: James Hatt <james.hatt@sanmina.com>
To: openbmc@lists.ozlabs.org
Subject: I need to build an OpenBMC image for a Portwell Neptune card ...
Date: Thu, 15 Oct 2020 08:00:14 -0500	[thread overview]
Message-ID: <CAABA6JmNH=AfzCE4aE_NuYCv126fCXOcexSq6O1C8+DdT6K1Jg@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2643 bytes --]

Dear OpenBMC,
I’ve been handed the *opportunity* of building OpenBMC for the Portwell
Neptune circuit card. Of course, Portwell is no help whatever.

I am new to OpenBMC. I’ve built Yocto Petalinux machines before. So I have
a little knowledge of Yocto. I’ve lots of experience with Linux and
embedded systems.

Where would I start?

BTW, I was able to clone the OpenBMC repository and build the phosphor
target without error. When I attempt to build meta-portwell/meta-neptune, I
get errors early with bitbake. Since the Portwell literature boasts of
Facebook OpenBMC, I tried their branch and that failed to build also.

Help!
---jjh

*James Hatt |* *Sr. Software Developer*
RF, Optical, and Microelectronics Division
A Division of Sanmina Corporation
Telephone: +1.972.512.5605
email: james.hatt@sanmina.com
1201 W. Crosby Rd., Carrollton, TX 75006
www.sanmina.com |  <http://www.twitter.com/vikinology>*t
<http://www.twitter.com/vikinology>*  <http://www.twitter.com/vikinology>|
<http://www.facebook.com/pages/Viking-Technology/106725999413927>*f
<http://www.facebook.com/pages/Viking-Technology/106725999413927>*
<http://www.facebook.com/pages/Viking-Technology/106725999413927>|
<http://www.linkedin.com/company/86313?trk=tyah>*l
<http://www.linkedin.com/company/86313?trk=tyah>*
<http://www.linkedin.com/company/86313?trk=tyah>|
<http://vimeo.com/vikingtechnology>*v* <http://vimeo.com/vikingtechnology>

-- 
CONFIDENTIALITY
This e-mail message and any attachments thereto, is 
intended only for use by the addressee(s) named herein and may contain 
legally privileged and/or confidential information. If you are not the 
intended recipient of this e-mail message, you are hereby notified that any 
dissemination, distribution or copying of this e-mail message, and any 
attachments thereto, is strictly prohibited.  If you have received this 
e-mail message in error, please immediately notify the sender and 
permanently delete the original and any copies of this email and any prints 
thereof.
ABSENT AN EXPRESS STATEMENT TO THE CONTRARY HEREINABOVE, THIS 
E-MAIL IS NOT INTENDED AS A SUBSTITUTE FOR A WRITING.  Notwithstanding the 
Uniform Electronic Transactions Act or the applicability of any other law 
of similar substance and effect, absent an express statement to the 
contrary hereinabove, this e-mail message its contents, and any attachments 
hereto are not intended to represent an offer or acceptance to enter into a 
contract and are not otherwise intended to bind the sender, Sanmina 
Corporation (or any of its subsidiaries), or any other person or entity.

[-- Attachment #1.2: Type: text/html, Size: 7000 bytes --]

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4191 bytes --]

             reply	other threads:[~2020-10-16  3:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15 13:00 James Hatt [this message]
2020-10-16 19:47 ` I need to build an OpenBMC image for a Portwell Neptune card Patrick Williams

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='CAABA6JmNH=AfzCE4aE_NuYCv126fCXOcexSq6O1C8+DdT6K1Jg@mail.gmail.com' \
    --to=james.hatt@sanmina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).