U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Ibai Erkiaga <ibai.erkiaga-elorza@amd.com>, u-boot@lists.denx.de
Cc: ada@thorsis.com
Subject: Re: [U-Boot][PATCH v5 0/5] Improve fpga cmd usage information
Date: Mon, 3 Feb 2025 10:28:54 +0100	[thread overview]
Message-ID: <c0d6fa82-b448-4a47-86a8-e44914d4fdd7@amd.com> (raw)
In-Reply-To: <20250121130138.1999916-1-ibai.erkiaga-elorza@amd.com>



On 1/21/25 14:01, Ibai Erkiaga wrote:
> 
>    Current usage information is not read friendly specially when all the
>    options are selected. This series fix some of the issues in the info,
>    aligment and overlapping issues, excess of verbosity on the loads...
> 
>    Additionally Xilinx exclusive command dependencies are included to
>    remove text stating Xilinx Only
> 
>    The output looks like this now:
> 
>    fpga - loadable FPGA image support
> 
>    Usage:
>    fpga info   [dev]                  List known device information
>    fpga dump   <dev> <address> <size> Load device to memory buffer
>    fpga load   <dev> <address> <size> Load device from memory buffer
>    fpga loadb  <dev> <address> <size> Load device from bitstream buffer
>    fpga loadp  <dev> <address> <size> Load device from memory buffer
>                with partial bitstream
>    fpga loadbp <dev> <address> <size> Load device from bitstream buffer
>                 with partial bitstream
>    fpga loadfs <dev> <address> <size> <blocksize> <interface> [<dev[:part]>] <filename>
>                Load device from filesystem (FAT by default)
>    fpga loadmk <dev> <address>        Load device generated with mkimage
>                NOTE: loadmk operating on FIT must include subimage unit
>                name in the form of addr:<subimg_uname>
>    fpga loads  <dev> <address> <size> <authflag> <encflag> [Userkey address]
>                Load device from memory buffer with secure bistream
>                (authenticated/encrypted/both)
>                -authflag: 0 for OCM, 1 for DDR, 2 for no authentication
>                (specifies where to perform authentication)
>                -encflag: 0 for device key, 1 for user key, 2 for no encryption
>                -Userkey address: address where user key is stored
>                NOTE: secure bitstream has to be created using Xilinx bootgen tool
> 
> Changes in v5:
> - Reorder KConfig to ensure commands are listed in the same order as the
> code.
> - Clarify the bitstream file type for load/loadb/loadp/loadbp commands
> 
> Changes in v4:
> - Split 4th patch into two, one for existing symbol dependencies and one
> for the new symbol
> 
> Changes in v3:
> - Split 3rd patch into two, resorting commands and Kconfig changes
> 
> Changes in v2:
> - Tabs replaced by spaces
> - fpga command added on each option similar to other commands like sf
> - Dependencies to Xilinx only commands added in Kconfig
> 
> Ibai Erkiaga (5):
>    fpga: fix alignment on fpga cmd usage info
>    fpga: improve loads usage information
>    fpga: resort fpga commands
>    fpga: xilinx exclusive commands
>    fpga: add new symbol for fpga_loadb
> 
>   cmd/Kconfig | 35 ++++++++++++++++++------------
>   cmd/fpga.c  | 62 ++++++++++++++++++++++++-----------------------------
>   2 files changed, 49 insertions(+), 48 deletions(-)
> 

Applied.
M

      parent reply	other threads:[~2025-02-03  9:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21 13:01 [U-Boot][PATCH v5 0/5] Improve fpga cmd usage information Ibai Erkiaga
2025-01-21 13:01 ` [U-Boot][PATCH v5 1/5] fpga: fix alignment on fpga cmd usage info Ibai Erkiaga
2025-01-21 13:01 ` [U-Boot][PATCH v5 2/5] fpga: improve loads usage information Ibai Erkiaga
2025-01-21 13:01 ` [U-Boot][PATCH v5 3/5] fpga: resort fpga commands Ibai Erkiaga
2025-01-21 13:01 ` [U-Boot][PATCH v5 4/5] fpga: xilinx exclusive commands Ibai Erkiaga
2025-01-21 13:01 ` [U-Boot][PATCH v5 5/5] fpga: add new symbol for fpga_loadb Ibai Erkiaga
2025-02-03  9:28 ` Michal Simek [this message]

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=c0d6fa82-b448-4a47-86a8-e44914d4fdd7@amd.com \
    --to=michal.simek@amd.com \
    --cc=ada@thorsis.com \
    --cc=ibai.erkiaga-elorza@amd.com \
    --cc=u-boot@lists.denx.de \
    /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