From: Andrew Jeffery <andrew@aj.id.au>
To: Tiju Jacob <Tiju.Jacob@flextronics.com>,
Patrick Williams <patrick@stwcx.xyz>,
Brad Bishop <bradleyb@fuzziesquirrel.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Add new machine
Date: Fri, 11 Nov 2016 09:05:55 +1030 [thread overview]
Message-ID: <1478817355.12438.3.camel@aj.id.au> (raw)
In-Reply-To: <MWHPR08MB2431CF1685C470069330770495B80@MWHPR08MB2431.namprd08.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1657 bytes --]
Hi Tiju,
On Thu, 2016-11-10 at 21:08 +0000, Tiju Jacob wrote:
> Hi,
>
> We have a new machine made and most of the code is leveraged from
> Wedge100.
> I would like to submit code back to Openbmc git hub.
Great!
We have been working with Facebook to try consolidate efforts, as
this OpenBMC project (https://github.com/openbmc/openbmc/) is not quite
the same* as Facebook's OpenBMC (https://github.com/facebook/openbmc/)
where Wedge100 can be found.
Regarding submitting code, OpenBMC's presence on github is primarily
for distribution and issue tracking. We're using Gerrit to manage
patches for OpenBMC-owned projects:
https://gerrit.openbmc-project.xyz/#/q/status:open
> I would like to create a new machine like ‘meta-wedge100’ with most
> of the references back to wedge100 and keep only the changes in the
> new machine directory.
>
> Could someone please suggest how to go about it? Also, is there a
> standard step by step method by which we can achieve this?
I'm one of the kernel/qemu hackers on the project so Yocto and its
layers aren't really my area of knowledge, but I expect we would have
to pull Facebook's layers into our openbmc/openbmc repo for you to
build on. I don't know if that's something we would do: Patrick and
Brad (now in To:) might be able to help you out here.
Cheers,
Andrew
>
> Thanks and Regards,
> Tiju
>
* We're working primarily on enabling OpenPOWER machines with an open
source BMC. We happen to use the same SoC series (AST2400/AST2500) as
Facebook, so there's a lot of cross-over in u-boot/Linux but the
userspace is fairly different.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-11-10 22:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 21:08 Add new machine Tiju Jacob
2016-11-10 22:35 ` Andrew Jeffery [this message]
2016-11-11 16:07 ` Tiju Jacob
2016-11-11 16:23 ` 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=1478817355.12438.3.camel@aj.id.au \
--to=andrew@aj.id.au \
--cc=Tiju.Jacob@flextronics.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
/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.