OT: Crowdfunding to port OpenBMC to Asus KGPE-D16

[Rick Altherr]

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.  I'll gladly support bringup on a
new SoC as long as the patches are headed to mainline 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.

My concerns with contributing to the campaign are that I don't understand
what work is planned and where those changes will end up.

Rick

On Mon, Feb 27, 2017 at 1:15 PM, Timothy Pearson <
tpearson at raptorengineering.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 02/27/2017 03:01 PM, Rick Altherr wrote:
> > I replied to Raptor's tweet asking why they preferred Facebook's OpenBMC
> > over the IBM one. I find it odd that you are asking developers on the
> > latter to fund development for the former.
> >
> > Rick
>
> Perhaps I should clarify a bit.
>
> The KGPE-D16 uses an older ASpeed device not supported by either version
> of OpenBMC.  This ASpeed device is not only limited in computational
> power, but ASUS limited the device further in the board design to the
> point where we are not sure that the IBM OpenBMC will actually fit or
> work without hardware modifications (in fact, I am fairly certain
> hardware modifications would be required).  Given our past experience
> with crowdfunding efforts we prioritized the total project cost over the
> more expansive feature set of IBM's OpenBMC in order to get something
> functional into the community's hands.  We hope that once the larger
> community has had a chance to experience software freedom on the BMC
> level using lower-cost commercially available hardware that they will
> support the manufacturers (such as IBM) that are selling hardware with
> OpenBMC available.
>
> We have also added a stretch goal to the project to initiate a port of
> IBM's OpenBMC, built on the common code and reverse engineering efforts
> from the base Facebook port.  This process is expected to involve
> creating new hardware to replace the limited firmware module of the
> KGPE-D16, as well as integrating new x86-specific drivers into the
> upstream IBM OpenBMC tree.  Perhaps this stretch goal is more
> interesting to the members on this list?
>
> Thanks!
>
> - --
> 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/
>
> iQEcBAEBAgAGBQJYtJbaAAoJEK+E3vEXDOFbRJoIALLUZzWr7zmZCKivjaS32BA4
> nAPRVTfImuEuh1AD6zmFL6WlHjv3NNyMEuBdaZRv7xoizlhHL/ua0XeCFws8Qtyw
> 3VUHsRMB5THvzcie+ooDPv3GoBQPc4MW70ZuDs5VV0pzp2HcHSeoaiTgDpA6z0ga
> GyP4cbFvBwgid7pvMAA4I+LujpgQLdui19o8QhO26GA13KUQhEDoSzKWg5C7xJFz
> vgTCwrF1u1avuA5RIth9+aGzOOJxgeRwT8tDzEAuwS+cC7dZGP6KXGVGfPPb8Qir
> b9ZRU/4Q0Ig7QnLaDp/zeua9MWXLyCaUMaaCAhmmbMFbCdzQ75e5Z2R7JFSDj9E=
> =rGB+
> -----END PGP SIGNATURE-----
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20170227/8482e6d9/attachment-0001.html>