From: Jacob Keller <jacob.e.keller@intel.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>,
Jakub Kicinski <kuba@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>, Jiri Pirko <jiri@resnulli.us>,
Michael Walle <michael@walle.cc>,
Heiner Kallweit <hkallweit1@gmail.com>, <netdev@vger.kernel.org>
Subject: Re: PHY firmware update method
Date: Mon, 3 Oct 2022 11:04:08 -0700 [thread overview]
Message-ID: <4ac5e807-c07b-ddbd-6ec9-839e80c808e9@intel.com> (raw)
In-Reply-To: <YzrTKwR/bEPJOs1P@shell.armlinux.org.uk>
On 10/3/2022 5:18 AM, Russell King (Oracle) wrote:
> On Fri, Sep 30, 2022 at 07:45:46AM -0700, Jakub Kicinski wrote:
>> Actually maybe there's something in DMTF, does PLDM have standard image
>> format? Adding Jake. Not sure if PHYs would use it tho :S
>
> DMTF? PLDM?
>
Jakub already linked to the standard we were referring to, but for
clarification:
DMTF refers to the group which was the Distributed Management Task
Force, and describes themselves as:
DMTF (formerly known as the Distributed Management Task Force) creates
open manageability standards spanning diverse emerging and traditional
IT infrastructures including cloud, virtualization, network, servers and
storage. Member companies and alliance partners worldwide collaborate on
standards to improve the interoperable management of information
technologies.
PLDM refers to "PLDM - Platform Level Data Model Including Firmware
Update, Redfish Device Enablement (RDE)"
The "PLDM for Firmware Update" is a standard which describes a file
format and associated specifications for how to interpret that file when
performing an update.
I implemented lib/pldmfw.c which is use in the ice driver as a way to
read the binary file to extract information about where each component
of firmware is in the binary, which could then be written to the device
to perform an update.
next prev parent reply other threads:[~2022-10-03 18:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 11:27 PHY firmware update method Michael Walle
2022-09-28 12:28 ` Andrew Lunn
2022-09-29 7:04 ` Jiri Pirko
2022-09-29 12:28 ` Andrew Lunn
2022-09-29 14:12 ` Jakub Kicinski
2022-09-29 14:53 ` Andrew Lunn
2022-09-30 8:25 ` Jiri Pirko
2022-09-30 12:36 ` Andrew Lunn
2022-09-30 14:45 ` Jakub Kicinski
2022-09-30 16:49 ` Keller, Jacob E
2022-10-03 12:18 ` Russell King (Oracle)
2022-10-03 14:42 ` Jakub Kicinski
2022-10-03 17:53 ` Keller, Jacob E
2022-10-03 18:04 ` Jacob Keller [this message]
2023-01-24 17:13 ` Michael Walle
2023-01-24 17:11 ` Michael Walle
2023-01-24 20:42 ` Andrew Lunn
2023-01-31 16:10 ` Michael Walle
2023-01-31 16:29 ` Russell King (Oracle)
2023-01-31 17:48 ` Michael Walle
2023-01-31 18:36 ` Jacob Keller
2023-01-31 18:41 ` Jakub Kicinski
2023-01-31 19:56 ` Jacob Keller
2023-01-31 21:07 ` Jakub Kicinski
2023-01-24 22:28 ` Jacob Keller
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=4ac5e807-c07b-ddbd-6ec9-839e80c808e9@intel.com \
--to=jacob.e.keller@intel.com \
--cc=andrew@lunn.ch \
--cc=hkallweit1@gmail.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).