From: Aaron Williams <awilliams@marvell.com>
To: openbmc@lists.ozlabs.org
Cc: Vijay Khemka <vijaykhemka@fb.com>,
Konstantin Klubnichkin <kitsok@yandex-team.ru>
Subject: Re: [EXT] Re: New motherboard to port OpenBMC to
Date: Thu, 24 Jan 2019 01:53:53 -0800 [thread overview]
Message-ID: <3329865.kWqfkPkNCf@flash> (raw)
In-Reply-To: <9F5DFCC3-67E6-48D8-B189-D3A4A7569451@fb.com>
I look forward to seeing this since that's what I'm currently trying to figure
out with our own board.
-Aaron
On Wednesday, January 23, 2019 9:56:43 AM PST Vijay Khemka wrote:
> External Email
>
> ----------------------------------------------------------------------
> Hi Konstantin,
> I am working on howto for sensors, temp etc. I will post it here in couple
> of days.
> Regards
> -Vijay
>
> On 1/23/19, 8:02 AM, "openbmc on behalf of Konstantin Klubnichkin"
> <openbmc-bounces+vijaykhemka=fb.com@lists.ozlabs.org on behalf of
> kitsok@yandex-team.ru> wrote:
> Hi all!
>
> I have the custom-made motherboards for Grantley CPU with Avocent-based
> BMC, and my goal is to switch to OpenBMC.
> I've read HOWTOs in the OpenBMC documentation, but usually the
> documentation is usually a bit behind the development, so are there any
> newer howtos or guides?
> Now I took Quanta MB as a reference and going to at least boot up the
> system and get the network. But it's pretty unclear for me how to add
> sensors, how to get CPUs temperatures, etc
> Could you please advise what to read to get into details?
>
> Thanks!
> --
> Best regards,
> Konstantin Klubnichkin,
> lead firmware engineer,
> server hardware R&D group,
> Yandex Moscow office.
> tel: +7-903-510-33-33
>
>
>
prev parent reply other threads:[~2019-01-24 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 15:56 New motherboard to port OpenBMC to Konstantin Klubnichkin
2019-01-23 17:56 ` Vijay Khemka
2019-01-24 2:10 ` Lei YU
2019-01-24 9:53 ` Aaron Williams [this message]
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=3329865.kWqfkPkNCf@flash \
--to=awilliams@marvell.com \
--cc=kitsok@yandex-team.ru \
--cc=openbmc@lists.ozlabs.org \
--cc=vijaykhemka@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.