u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Sean Anderson <sean.anderson@seco.com>
To: Joe Hershberger <joe.hershberger@ni.com>,
	Ramon Fried <rfried.dev@gmail.com>,
	u-boot@lists.denx.de
Cc: Simon Glass <sjg@chromium.org>, York Sun <york.sun@nxp.com>,
	Priyanka Jain <priyanka.jain@nxp.com>,
	Sean Anderson <sean.anderson@seco.com>,
	Michal Simek <michal.simek@xilinx.com>,
	Patrick Delaunay <patrick.delaunay@foss.st.com>
Subject: [PATCH 0/6] net: fm: Verify Fman microcode
Date: Thu, 24 Mar 2022 14:22:59 -0400	[thread overview]
Message-ID: <20220324182306.2037094-1-sean.anderson@seco.com> (raw)

Surprisingly, Fman microcode does not seem to be verified. This series
aims to rectify this by introducing an optional FIT wrapper. This
wrapper is made mandatory if FIT_SIGNATURE is enabled. NXP boards do not
use this config, so the microcode will remain unverified for them. This
is OK, since we do not want to break existing systems.


Sean Anderson (6):
  ARMv8/sec_firmware: Remove SEC_FIRMWARE_FIT_CNF_NAME
  image: fit: Add some helpers for getting data
  misc: fs_loader: Add function to get the chosen loader
  net: fm: Add firmware name parameter
  net: fm: Support loading firmware from a filesystem
  net: fm: Add support for FIT firmware

 arch/arm/cpu/armv8/sec_firmware.c  | 52 +++------------------------
 arch/arm/mach-k3/common.c          |  2 +-
 arch/arm/mach-omap2/boot-common.c  |  2 +-
 boot/image-fit.c                   | 37 +++++++++++++++++++
 cmd/fpga.c                         | 24 ++++---------
 drivers/fpga/socfpga_arria10.c     | 24 ++-----------
 drivers/misc/fs_loader.c           | 27 ++++++++++++++
 drivers/net/fm/fm.c                | 58 +++++++++++++++++++++++++++---
 drivers/net/fm/fm.h                |  2 +-
 drivers/net/fm/init.c              |  4 +--
 drivers/net/fsl-mc/mc.c            | 30 ++--------------
 drivers/net/pfe_eth/pfe_firmware.c | 40 +--------------------
 drivers/qe/Kconfig                 |  4 +++
 include/fs_loader.h                | 12 +++++++
 include/image.h                    |  4 +++
 15 files changed, 159 insertions(+), 163 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-03-24 18:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 18:22 Sean Anderson [this message]
2022-03-24 18:23 ` [PATCH 1/6] ARMv8/sec_firmware: Remove SEC_FIRMWARE_FIT_CNF_NAME Sean Anderson
2022-03-24 18:23 ` [PATCH 2/6] image: fit: Add some helpers for getting data Sean Anderson
2022-03-28  6:35   ` Simon Glass
2022-03-28 15:33     ` Sean Anderson
2022-03-24 18:23 ` [PATCH 3/6] misc: fs_loader: Add function to get the chosen loader Sean Anderson
2022-03-28  6:35   ` Simon Glass
2022-03-24 18:23 ` [PATCH 4/6] net: fm: Add firmware name parameter Sean Anderson
2022-03-24 18:23 ` [PATCH 5/6] net: fm: Support loading firmware from a filesystem Sean Anderson
2022-03-24 18:23 ` [PATCH 6/6] net: fm: Add support for FIT firmware Sean Anderson

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=20220324182306.2037094-1-sean.anderson@seco.com \
    --to=sean.anderson@seco.com \
    --cc=joe.hershberger@ni.com \
    --cc=michal.simek@xilinx.com \
    --cc=patrick.delaunay@foss.st.com \
    --cc=priyanka.jain@nxp.com \
    --cc=rfried.dev@gmail.com \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    --cc=york.sun@nxp.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 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).