From: Joel Stanley <joel@jms.id.au>
To: Mykola Kostenok <c_mykolak@mellanox.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Mellanox ipmi daemon discussion
Date: Wed, 6 Sep 2017 14:46:49 +0930 [thread overview]
Message-ID: <CACPK8XcBWbdKQruu5wdAP2xo6xmxQ867fP41SUU+0d38H7O-Wg@mail.gmail.com> (raw)
In-Reply-To: <DB5PR05MB1224502182F8C6EAF62E17C9EF9E0@DB5PR05MB1224.eurprd05.prod.outlook.com>
Hello Mykola,
On Tue, Aug 29, 2017 at 12:57 AM, Mykola Kostenok
<c_mykolak@mellanox.com> wrote:
>
> We'd like to add Mellanox ipmi daemon recipe to mellanox msn platform. It's based on openipmi project.
> Code review: https://gerrit.openbmc-project.xyz/#/c/5694/.
>
> We added some hooks in openipmi code and also our specific module.
> We use it for SoL, SEL, serial console redirection, console switching between the host and BMC, PET/PEF, LAN related commands, time setting,, and also a lot of OEM commands for LED, FAN control, reset signals, reset causes, BT connection with CPU, etc.
The reuse of existing code is a good achievement. Well done.
How did you find the use of OpenIPMI for your needs?
> It doesn't use DBUS interface.
This is a downside. The use of dbus as an inter-process communication
mechanism is something that defines OpenBMC at the moment.
Could you add dbus IPC to the existing codebase?
>
> We are planning transition to OpenBMC ipmi demon, after we are done with all kernel related patches. Our plan is to start transition in the following order SoL, SDR, SEL, LAN, LED and so on.
What lead to this decision? What are the up and down sides of the
phosphor ipmi daemon compared to OpenIPMI?
> At his moment we'd like to have functional image, which can be built from OpenBMC with no any patches.
> We also have one customer and it's important for us to have a functional image, which he can build by himself.
Agreed. I've +1'd your patch, and would like to see it merged.
Cheers,
Joel
next prev parent reply other threads:[~2017-09-06 5:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 15:27 Mellanox ipmi daemon discussion Mykola Kostenok
2017-09-06 5:16 ` Joel Stanley [this message]
2017-09-06 8:30 ` Mykola Kostenok
2017-09-14 13:04 ` Mykola Kostenok
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=CACPK8XcBWbdKQruu5wdAP2xo6xmxQ867fP41SUU+0d38H7O-Wg@mail.gmail.com \
--to=joel@jms.id.au \
--cc=c_mykolak@mellanox.com \
--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 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.