From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Jamie Gibbons via buildroot <buildroot@buildroot.org>
Cc: Valentina Fernandez Alanis
<Valentina.FernandezAlanis@microchip.com>,
Jamie Gibbons <jamie.gibbons@microchip.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
Conor Dooley <Conor.Dooley@microchip.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>
Subject: Re: [Buildroot] [PATCH v2 1/2] package/microchip-hss-payload-generator: add host package
Date: Wed, 12 Jul 2023 13:49:33 +0200 [thread overview]
Message-ID: <20230712134933.58ec91c8@windsurf> (raw)
In-Reply-To: <20230712083455.2349333-2-jamie.gibbons@microchip.com>
Hello Jamie,
So very minor nits below.
On Wed, 12 Jul 2023 09:34:54 +0100
Jamie Gibbons via buildroot <buildroot@buildroot.org> wrote:
> diff --git a/package/microchip-hss-payload-generator/Config.in.host b/package/microchip-hss-payload-generator/Config.in.host
> new file mode 100644
> index 0000000000..1e21fbbb5d
> --- /dev/null
> +++ b/package/microchip-hss-payload-generator/Config.in.host
> @@ -0,0 +1,10 @@
> +config BR2_PACKAGE_HOST_MICROCHIP_HSS_PAYLOAD_GENERATOR
> + bool "HSS Payload Generator"
Should be:
bool "host microchip-hss-payload-generator"
> + help
> + Microchip PolarFire SoC Payload Generator. This tool creates a formatted
> + payload image for the HSS zero-stage bootloader on PolarFire SoC, given a
> + configuration file and a set of ELF binaries. The configuration file is
> + used to map the ELF binaries or binary blobs to the individual application
> + harts (U54s).
Is "make check-package" running fine? These lines look a bit long to
me, but "make check-package" will tell for sure.
> diff --git a/package/microchip-hss-payload-generator/microchip-hss-payload-generator.mk b/package/microchip-hss-payload-generator/microchip-hss-payload-generator.mk
> new file mode 100644
> index 0000000000..7344d208c1
> --- /dev/null
> +++ b/package/microchip-hss-payload-generator/microchip-hss-payload-generator.mk
> @@ -0,0 +1,24 @@
> +################################################################################
> +#
> +# microchip-hss-payload-generator
> +#
> +################################################################################
Missing empty line between the silly comment header above and the first
variable definition.
> +HOST_MICROCHIP_HSS_PAYLOAD_GENERATOR_VERSION = 2023.06
> +HOST_MICROCHIP_HSS_PAYLOAD_GENERATOR_SITE = $(call github,polarfire-soc,hart-software-services,v$(HOST_MICROCHIP_HSS_PAYLOAD_GENERATOR_VERSION))
> +HOST_MICROCHIP_HSS_PAYLOAD_GENERATOR_LICENSE = MIT
> +HOST_MICROCHIP_HSS_PAYLOAD_GENERATOR_LICENSE_FILES = LICENSE.md
> +HOST_MICROCHIP_HSS_PAYLOAD_GENERATOR_DEPENDENCIES = host-elfutils host-libyaml
No other comments, the rest looks fine to me, of course except the
host-openssl missing dependency pointed out by Giulio.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-07-12 11:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 8:34 [Buildroot] [PATCH v2 0/2] Add Microchip PolarFire SoC Icicle Kit Jamie Gibbons via buildroot
2023-07-12 8:34 ` [Buildroot] [PATCH v2 1/2] package/microchip-hss-payload-generator: add host package Jamie Gibbons via buildroot
2023-07-12 9:35 ` Giulio Benetti
2023-07-12 10:27 ` Jamie.Gibbons--- via buildroot
2023-07-12 11:49 ` Thomas Petazzoni via buildroot [this message]
2023-07-12 12:43 ` Jamie.Gibbons--- via buildroot
2023-07-12 8:34 ` [Buildroot] [PATCH v2 2/2] configs/microchip_mpfs_icicle: add support for Microchip's Icicle Kit Jamie Gibbons via buildroot
2023-07-12 9:41 ` Giulio Benetti
2023-07-12 11:26 ` Jamie.Gibbons--- via buildroot
2023-07-12 12:35 ` Giulio Benetti
2023-07-12 12:48 ` Jamie.Gibbons--- via buildroot
2023-07-12 13:32 ` Giulio Benetti
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=20230712134933.58ec91c8@windsurf \
--to=buildroot@buildroot.org \
--cc=Conor.Dooley@microchip.com \
--cc=Valentina.FernandezAlanis@microchip.com \
--cc=jamie.gibbons@microchip.com \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=thomas.petazzoni@bootlin.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