mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Joel Stanley <joel@jms.id.au>
Cc: openbmc@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Gunnar Mills <gmills@us.ibm.com>
Subject: Status of aspeed-bmc-opp-firestone (IBM S822LC)
Date: Tue, 29 May 2018 16:53:04 +0200	[thread overview]
Message-ID: <287c6a85-65ba-5782-e532-d17d517614f5@molgen.mpg.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]

Dear Joel, dear Linux folks,


We have an IBM S822LC system (Firestone(?)). Building of OpenBMC 
currently fails, as the not everything was ported from dev-4.10 to 
dev-4.13 [1], and therefore a file cannot be found.

Looking at upstream Linux, there are BMCs for Power 8 systems, like 
Palmetto, included.

```
$ ls arch/arm/boot/dts/aspeed-bmc-opp-*
arch/arm/boot/dts/aspeed-bmc-opp-palmetto.dts
arch/arm/boot/dts/aspeed-bmc-opp-romulus.dts
arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts
arch/arm/boot/dts/aspeed-bmc-opp-zaius.dts
```

Does somebody know, why Firestone was not upstreamed? Is somebody 
working on upstreaming it? If not, do you have scripts to port such 
work? Manually cherry-picking stuff in this case is hard, as there are a 
lot of conflicts.


Kind regards,

Paul


[1]: https://github.com/openbmc/openbmc/issues/3206


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5174 bytes --]

             reply	other threads:[~2018-05-29 14:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29 14:53 Paul Menzel [this message]
2018-05-30  4:06 ` Andrew Jeffery

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=287c6a85-65ba-5782-e532-d17d517614f5@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=gmills@us.ibm.com \
    --cc=joel@jms.id.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    /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
all inboxes | Powered by JetHome®