From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: Willy Tu <wltu@google.com>
Cc: vernon.mauery@linux.intel.com, openbmc@lists.ozlabs.org,
apparao.puli@linux.intel.com, vijaykhemka@fb.com,
chunhui.jia@linux.intel.com
Subject: Re: Intel-ipmi-oem repo
Date: Thu, 14 Jan 2021 08:39:09 -0600 [thread overview]
Message-ID: <20210114143909.jf3vbk7zhxp3iguv@thinkpad.fuzziesquirrel.com> (raw)
In-Reply-To: <CAHwn2XkNiz7rZzn9RbpZCaUM8HD0HO+mJTD9D2ENc_p+SsmXHg@mail.gmail.com>
On Tue, Jan 12, 2021 at 06:54:14PM -0800, Willy Tu wrote:
>> Team,
>> Intel-ipmi-oem should be broken and 2 parts, genric and oem specific. I
>see several functionality in this repo like sensors and storage commands
>are generic enough to be used by other platform who is using entity
>manager. So I feel that we should have these functionalities to be moved to
>a separate common repo which can be used by everyone and this repo can only
>contain Intel OEM specific IPMI command support.
>>
>> My 2 cents 😊
>
>Hi All,
>
>I guess I'll start working on this if no one has any objection to it.
Awesome!
>As mentioned in the beginning of the thread. The plan is to break down the
>intel-ipmi-oem repo into two parts.
>- True OEM at Intel
>- Dynamic Sensor stacks (new repo)
Why is dynamic sensor stacks a new repo? I would like to see this done
in the existing ipmid repo. If the default implementations there today
are undesired, I'd be fine with seeing those moved to the
openpower-ipmi-oem repository.
FWIW I would like to make use of dynamic SDR on my new systems (I work
for IBM) but I still have to maintain support for Witherspoon, which
relies on the old fixed & hardcoded sensor identifiers.
-brad
next prev parent reply other threads:[~2021-01-14 14:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 2:54 Intel-ipmi-oem repo Willy Tu
2021-01-14 14:39 ` Brad Bishop [this message]
2021-01-14 16:38 ` Ed Tanous
2021-01-14 17:38 ` Vernon Mauery
2021-01-14 19:40 ` Brad Bishop
2021-01-14 20:06 ` Ed Tanous
2021-01-14 21:46 ` Willy Tu
2021-01-15 2:23 ` Lei Yu
2021-01-15 4:20 ` chunhui.jia
2021-01-15 5:59 ` Lei Yu
2021-01-14 18:53 ` Brad Bishop
2021-01-14 20:00 ` Ed Tanous
-- strict thread matches above, loose matches on Subject: below --
2019-01-22 18:16 Vijay Khemka
2019-01-22 20:53 ` Brad Bishop
2019-01-22 21:02 ` Patrick Venture
2019-01-22 21:31 ` Vijay Khemka
2019-01-22 22:05 ` Ed Tanous
2019-01-22 22:22 ` Vijay Khemka
2019-01-22 23:25 ` Ed Tanous
2019-01-22 23:58 ` Vijay Khemka
2019-01-24 0:42 ` Bills, Jason M
2019-01-23 6:13 ` Tom Joseph
2019-01-23 16:34 ` Ed Tanous
2019-01-23 16:59 ` Brad Bishop
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=20210114143909.jf3vbk7zhxp3iguv@thinkpad.fuzziesquirrel.com \
--to=bradleyb@fuzziesquirrel.com \
--cc=apparao.puli@linux.intel.com \
--cc=chunhui.jia@linux.intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=vernon.mauery@linux.intel.com \
--cc=vijaykhemka@fb.com \
--cc=wltu@google.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.