From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: <Jamie.Gibbons@microchip.com>
Cc: Conor.Dooley@microchip.com, Nicolas.Ferre@microchip.com,
Ludovic.Desroches@microchip.com, buildroot@buildroot.org,
Valentina.FernandezAlanis@microchip.com,
giulio.benetti@benettiengineering.com
Subject: Re: [Buildroot] [PATCH v3 2/2] configs/microchip_mpfs_icicle: add support for Microchip's Icicle Kit
Date: Thu, 10 Aug 2023 15:53:00 +0200 [thread overview]
Message-ID: <20230810155300.19ac971b@windsurf> (raw)
In-Reply-To: <36d1e8110955931efe354356c9b09c29f332f8fb.camel@microchip.com>
Hello Jamie,
On Thu, 10 Aug 2023 10:46:30 +0000
<Jamie.Gibbons@microchip.com> wrote:
> THe HSS code is located in eNVM of the Icicle kit for PolarFire SoC and
> built outside of Buildroot.
ACK.
> The HSS paylaod generator which is a host tool to create HSS formatted
> payloads is built by buildroot. This is covered in the microchip-hss-
> payload-generator package. This tool is released under dual MIT/GPLv2+
> licenses.
> https://github.com/polarfire-soc/hart-software-services/blob/master/tools/hss-payload-generator/LICENSE.md
>
> The HSS payload generator is the only software compnent here that is
> built inside Buildroot. The HSS code and OpenSBI are both built outside
> Buildroot, so their licences are not a concern.
>
> I hope this clears things up further.
This is all clear.
Can this HSS code + OpenSBI stored in the eNVM be updated by the user?
If it's the case, would it make sense for Buildroot to be able to build
it?
> > Does that make sense in the RISC-V world?
>
> After a discussion with colllegues we believe that the above two configs
> should be available when BR2_riscv_g is selected as suggested. This does
> make sense.
Cool, we agree!
> Would you like me to include this change in a patchset to fix the
> configs for the microchip_mpfs_icicle_defconfig or do you want to make
> this update yourself?
Feel free to send a patch set :-)
Thanks a lot!
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-08-10 13:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 12:51 [Buildroot] [PATCH v3 0/2] Add Microchip PolarFire SoC Icicle Kit Jamie Gibbons via buildroot
2023-07-12 12:51 ` [Buildroot] [PATCH v3 1/2] package/microchip-hss-payload-generator: add host package Jamie Gibbons via buildroot
2023-07-12 13:46 ` Giulio Benetti
2023-08-08 21:56 ` Thomas Petazzoni via buildroot
2023-08-09 12:55 ` Jamie.Gibbons--- via buildroot
2023-07-12 12:51 ` [Buildroot] [PATCH v3 2/2] configs/microchip_mpfs_icicle: add support for Microchip's Icicle Kit Jamie Gibbons via buildroot
2023-07-12 13:47 ` Giulio Benetti
2023-08-08 21:59 ` Thomas Petazzoni via buildroot
2023-08-09 14:43 ` Jamie.Gibbons--- via buildroot
2023-08-09 15:02 ` Thomas Petazzoni via buildroot
2023-08-10 10:46 ` Jamie.Gibbons--- via buildroot
2023-08-10 13:53 ` Thomas Petazzoni via buildroot [this message]
2023-08-11 9:09 ` Jamie.Gibbons--- via buildroot
2023-07-26 10:40 ` [Buildroot] [PATCH v3 0/2] Add Microchip PolarFire SoC " Jamie.Gibbons--- via buildroot
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=20230810155300.19ac971b@windsurf \
--to=buildroot@buildroot.org \
--cc=Conor.Dooley@microchip.com \
--cc=Jamie.Gibbons@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Valentina.FernandezAlanis@microchip.com \
--cc=giulio.benetti@benettiengineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.