From: Paul Fertser <fercerpav@gmail.com>
To: Jiaqing Zhao <jiaqing.zhao@linux.intel.com>
Cc: Samuel Mendoza-Jonas <sam@mendozajonas.com>,
netdev@vger.kernel.org, openbmc@lists.ozlabs.org,
linux-kernel@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] net/ncsi: Add Intel OS2BMC OEM command
Date: Fri, 9 Sep 2022 10:43:27 +0300 [thread overview]
Message-ID: <Yxrun9LRcFv2QntR@home.paul.comp> (raw)
In-Reply-To: <8eabb29b-7302-d0a2-5949-d7aa6bc59809@linux.intel.com>
Hello,
On Fri, Sep 09, 2022 at 03:34:53PM +0800, Jiaqing Zhao wrote:
> > Can you please outline some particular use cases for this feature?
> >
> It enables access between host and BMC when BMC shares the network connection
> with host using NCSI, like accessing BMC via HTTP or SSH from host.
Why having a compile time kernel option here more appropriate than
just running something like "/usr/bin/ncsi-netlink --package 0
--channel 0 --index 3 --oem-payload 00000157200001" (this example uses
another OEM command) on BMC userspace startup?
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com
WARNING: multiple messages have this Message-ID (diff)
From: Paul Fertser <fercerpav@gmail.com>
To: Jiaqing Zhao <jiaqing.zhao@linux.intel.com>
Cc: Samuel Mendoza-Jonas <sam@mendozajonas.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, openbmc@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/ncsi: Add Intel OS2BMC OEM command
Date: Fri, 9 Sep 2022 10:43:27 +0300 [thread overview]
Message-ID: <Yxrun9LRcFv2QntR@home.paul.comp> (raw)
In-Reply-To: <8eabb29b-7302-d0a2-5949-d7aa6bc59809@linux.intel.com>
Hello,
On Fri, Sep 09, 2022 at 03:34:53PM +0800, Jiaqing Zhao wrote:
> > Can you please outline some particular use cases for this feature?
> >
> It enables access between host and BMC when BMC shares the network connection
> with host using NCSI, like accessing BMC via HTTP or SSH from host.
Why having a compile time kernel option here more appropriate than
just running something like "/usr/bin/ncsi-netlink --package 0
--channel 0 --index 3 --oem-payload 00000157200001" (this example uses
another OEM command) on BMC userspace startup?
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com
next prev parent reply other threads:[~2022-09-09 7:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 2:57 [PATCH] net/ncsi: Add Intel OS2BMC OEM command Jiaqing Zhao
2022-09-09 2:57 ` Jiaqing Zhao
2022-09-09 5:59 ` Paul Fertser
2022-09-09 5:59 ` Paul Fertser
2022-09-09 7:34 ` Jiaqing Zhao
2022-09-09 7:34 ` Jiaqing Zhao
2022-09-09 7:43 ` Paul Fertser [this message]
2022-09-09 7:43 ` Paul Fertser
2022-09-13 2:12 ` Jiaqing Zhao
2022-09-13 2:12 ` Jiaqing Zhao
2022-09-13 13:35 ` Sam Mendoza-Jonas
2022-09-13 13:35 ` Sam Mendoza-Jonas
2022-09-14 1:10 ` Jiaqing Zhao
2022-09-14 1:10 ` Jiaqing Zhao
2022-09-15 15:43 ` Paul Fertser
2022-09-15 15:43 ` Paul Fertser
2022-09-19 8:06 ` Jiaqing Zhao
2022-09-19 8:06 ` Jiaqing Zhao
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=Yxrun9LRcFv2QntR@home.paul.comp \
--to=fercerpav@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiaqing.zhao@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=pabeni@redhat.com \
--cc=sam@mendozajonas.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.