archive mirror
 help / color / mirror / Atom feed
From: Zev Weiss <>
To: Joel Stanley <>
Cc: "" <>
Subject: Re: RFC: ASRockRack E3C246D4I port
Date: Wed, 24 Mar 2021 22:15:06 +0000	[thread overview]
Message-ID: <YFu56TGJQyKRSOt2@packtop> (raw)
In-Reply-To: <>

On Tue, Mar 23, 2021 at 08:50:07PM CDT, Joel Stanley wrote:
>On Tue, 23 Mar 2021 at 22:25, Zev Weiss <> wrote:
>> Hello all,
>> We (Equinix Metal, formerly known as Packet) having been working on a
>> port of OpenBMC to the ASRockRack E3C246D4I board
>> (,
>> an AST2500-equipped Xeon E-2100 mini-ITX board), and we're now looking to
>> get some feedback from the community and hopefully start the process of
>> getting it merged upstream.
>> It's currently sitting in a Github branch, since at the moment I'm
>> mostly seeking fairly broad guidance on what sorts of things will need
>> to happen to get it into a mergeable form (not sure if gerrit is the
>> right tool for that).  Anyone who'd like to can take a look at:
>> Known issues, in approximate descending order of significance (by my
>> estimate):
>>   - The kernel situation is...kind of messy.  This mostly stems from
>>     having a dependency on the PECI code, which is why the branch is
>>     based on the 2.9.0 tag (the last one before the PECI patchset was
>>     dropped from the openbmc kernel) instead of something more recent.
>>     We've got some additional PECI patches on top of that to work around
>>     some limitations in the PECI support on the particular CPU we're
>>     working with, some of which is fairly gross hardcoding for that
>>     specific SKU.  There are also a few non-PECI-related kernel patches
>>     that I've posted upstream but not yet incorporated the resulting
>>     review feedback on.
>As you point out, it would be great if someone could take on the PECI
>maintainership and get the code merged to mainline.
>Out of interest, can you still boot the host without PECI support?

Yes, we're using PECI for monitoring CPU thermals but that's about it;
we can boot the host without it.

>I recommend submitting your device tree now, and getting some level of
>support in the openbmc tree. From there you can work to get the other
>fixes into the tree.

Alright, I'll start out with getting some baseline bits and pieces in
place and see about the trickier parts when I get to them.


  reply	other threads:[~2021-03-24 22:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12  2:45 Zev Weiss
2021-03-24  1:50 ` Joel Stanley
2021-03-24 22:15   ` Zev Weiss [this message]
2021-03-17 22:46 Zev Weiss

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YFu56TGJQyKRSOt2@packtop \ \ \ \
    --subject='Re: RFC: ASRockRack E3C246D4I port' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).