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

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?

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.



>   - There are various hacks to get things like x86-power-control and
>     host-error-monitor compiling and working reasonably, and I'm sort of
>     skeptical that the approach I took there would be considered
>     desirable.
>   - The directory naming is currently meta-equinix/meta-e3c246d4i;
>     starting out I was a bit unsure whether to name based on the
>     maintainer/developer of the layer or the maker of the hardware and we
>     ended up with the former, though I see Ed's in-progress x570d4u port
>     has things under meta-asrock, so perhaps that should be renamed?
>   - There are some relatively generic patches for dbus-sensors and
>     entity-manager that should probably be merged independently.
> If anyone can give it a look and let me know what the best way forward
> would be for this we'd certainly appreciate it.
> Thanks,
> Zev Weiss

  reply	other threads:[~2021-03-24  1:50 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 [this message]
2021-03-24 22:15   ` Zev Weiss
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='' \ \ \ \
    --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).