netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Jakub Kicinski <kuba@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
	Jacob Keller <jacob.e.keller@intel.com>,
	Jiri Pirko <jiri@resnulli.us>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	netdev@vger.kernel.org
Subject: Re: PHY firmware update method
Date: Tue, 24 Jan 2023 18:13:25 +0100	[thread overview]
Message-ID: <59c5af5bd238e6ccd5cbccc58766643e@walle.cc> (raw)
In-Reply-To: <YzrTKwR/bEPJOs1P@shell.armlinux.org.uk>

Am 2022-10-03 14:18, schrieb Russell King (Oracle):
> 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?
> 
>> What's the interface that the PHY FW exposes? Ben H was of the opinion
>> that we should just expose the raw mtd devices.. just saying..
> 
> Not all PHYs provide raw access to the firmware memory to the host; in
> some cases, firmware memory access needs the PHY to be shutdown, and
> programs loaded into the PHY to provide a "bridge" to program the
> external firmware memory. I'm thinking about 88x3310 here - effectively
> there it's write-only access via an intermediate program on the PHY,
> and there's things like checksums etc.
> 
> So, exposing everything as a MTD sounds like a solution, but not all
> PHYs provide such access. IMHO, if we say "everything must provide a
> MTD" then we're boxing ourselves into a corner.

I agree, the PHY I'm looking at right now, can't read back the
firmware binary. And there is also no random access, you basically
have to stream the whole binary in one go to the PHY.

-michael

  parent reply	other threads:[~2023-01-24 17:13 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
2023-01-24 17:13                   ` Michael Walle [this message]
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=59c5af5bd238e6ccd5cbccc58766643e@walle.cc \
    --to=michael@walle.cc \
    --cc=andrew@lunn.ch \
    --cc=hkallweit1@gmail.com \
    --cc=jacob.e.keller@intel.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --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).