From: Timothy Pearson <tpearson@raptorengineering.com>
To: Rick Altherr <raltherr@google.com>
Cc: Paul Menzel <paulepanter@users.sourceforge.net>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Martin Roth <gaumless@gmail.com>
Subject: Re: OT: Crowdfunding to port OpenBMC to Asus KGPE-D16
Date: Mon, 27 Feb 2017 15:32:41 -0600 [thread overview]
Message-ID: <58B49AF9.7090708@raptorengineeringinc.com> (raw)
In-Reply-To: <CAPLgG=k7ZW-vOKfE1JQxvzmzM=1__yPiY6kpL5TxET7fHV+uHg@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/27/2017 03:24 PM, Rick Altherr wrote:
> I'm assuming the core work of booting u-boot and linux on the BMC used
> on KGPE-D16 (AST2300?) is usable by both projects.
Exactly.
I'll gladly support
> bringup on a new SoC as long as the patches are headed to mainline linux
> and u-boot.
This would be part of the third stretch goal (IBM OpenBMC support). Any
of the stretch goals can be funded in any order, and you can also
earmark a contribution specifically for any of the stretch goal(s) you
may be interested in.
To keep the overall costs reasonable and to allow adapting to the needs
of the community, the base goal consists of a port of the Facebook
OpenBMC system, released as a buildable source tree, and includes
creation and upstreaming of the necessary changes to coreboot and
flashrom. More advanced features are then implemented as stretch goals,
including the work of trying to upstream the drivers into Linux and u-boot.
> AFAIK, the only limit on whether IBM OpenBMC can be used is the amount
> of RAM and flash available. My work on a Quanta Q71L has it booting on
> an AST2400 with 128MB of RAM and 32MB of flash.
The KGPE-D16 is even more limited than that. Even making Facebook's
OpenBMC function on an unmodified KGPE-D16 will be an interesting challenge.
> My concerns with contributing to the campaign are that I don't
> understand what work is planned and where those changes will end up.
I hope this has helped clarify some. If you have any other questions
please feel free to ask!
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJYtJr2AAoJEK+E3vEXDOFbbdwH/3lLbyA5NsZ1iGvej9+Vkvaj
JOjfqyxZ4+2OJgiq3laLSSNOefGn6CDOXub+TTFKv+Cb/02zqVb1NUcUauK1QCGK
IlMkQxG5o+kxA7vJ+7p3UTbpeZGPRdDVf008IBneWEmsOcI8lYnSFh7VyCvJb9eR
dE4HltGIr5z9zKaOWO8IMYQIjUcbnOucpaA2xbjGxPpwDtebwetqgY7wQ+dR6qyc
VNg6jOESZY3AsQB+AIEEwP8bGx+i7rLkNMYCnHdem837mUXrQ3M5aFpT2McoNV3a
Ut3sTUH1A9sE99qEx8Ka113CWI/myco53YyVe4xtQbXC/m+ttMhX+8+QcesXqEQ=
=rI1I
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2017-02-27 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 18:49 OT: Crowdfunding to port OpenBMC to Asus KGPE-D16 Paul Menzel
2017-02-27 21:01 ` Rick Altherr
2017-02-27 21:15 ` Timothy Pearson
2017-02-27 21:24 ` Rick Altherr
2017-02-27 21:32 ` Timothy Pearson [this message]
2017-02-28 8:49 ` Paul Menzel
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=58B49AF9.7090708@raptorengineeringinc.com \
--to=tpearson@raptorengineering.com \
--cc=gaumless@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=paulepanter@users.sourceforge.net \
--cc=raltherr@google.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.