From: Paul Menzel <paulepanter@users.sourceforge.net>
To: openbmc@lists.ozlabs.org
Cc: Timothy Pearson <tpearson@raptorengineeringinc.com>,
Martin Roth <gaumless@gmail.com>,
linux-kernel@vger.kernel.org
Subject: OT: Crowdfunding to port OpenBMC to Asus KGPE-D16
Date: Sun, 26 Feb 2017 19:49:22 +0100 [thread overview]
Message-ID: <1488134962.2850.11.camel@users.sourceforge.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 2081 bytes --]
[Please CC me, as I am not subscribed.]
Dear OpenBMC people,
If you haven’t heard yet, there is a crowdfunding campaign going on to
fund a port of OpenBMC to the Asus KGPE-D16 [1].
The free firmware coreboot [2] runs on that board, and no BLOBs have to
be used with it. Having OpenBMC run on that board, would be the last
step, to have a fully free, owner-controlled server mainboard. I am
citing a message from Timothy to the coreboot mailing list below from
February 6th, 2017 [3].
> As of today, we have $10,250 pledged out of $20,000 required to start
> work on the OpenBMC support for KGPE-D16 systems using coreboot. Raptor
> is, as before, contributing an additional $25,000+ toward development
> should the $20,000 community goal be reached.
>
> If you would like to help get this port started, please contact Martin
> Roth (gaumless@gmail.com) with information on what you would like to
> pledge. This offer is time limited; we are looking to end the offer in
> the next month or so, so if this is something you would like to see
> please step up and contribute something to this goal!
>
> As a general reminder, the KGPE-D16 is the last, most powerful
> owner-controllable X86 workstation / server class machine available. It
> is still in production along with its Opteron CPUs, so it occupies a
> unique position in coreboot's tree. Providing a libre BMC for this
> system could help adoption of coreboot in server environments,
> strengthening its position some in the market.
As of today there are still $6,000 USD missing. As the coreboot
community does not seem big enough to fund such a project, I am kindly
asking you for support. If you can’t or don’t want to spend money, it’d
be great if you could spread the word (Twitter message [4]).
Thanks,
Paul
[1] https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-offer.php
[2] https://www.coreboot.org/
[3] https://www.coreboot.org/pipermail/coreboot/2017-February/083176.html
[4] https://twitter.com/RaptorEng/status/833738989840584704
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
reply other threads:[~2017-02-26 19:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1488134962.2850.11.camel@users.sourceforge.net \
--to=paulepanter@users.sourceforge.net \
--cc=gaumless@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=tpearson@raptorengineeringinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox