From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Köry Maincent via buildroot" <buildroot@buildroot.org>
Cc: "Köry Maincent" <kory.maincent@bootlin.com>
Subject: Re: [Buildroot] [PATCH 1/2] board/octavo/osd32mp1-red: update BSP components
Date: Thu, 6 Oct 2022 22:03:35 +0200 [thread overview]
Message-ID: <20221006220335.22132976@windsurf> (raw)
In-Reply-To: <20221005075815.305236-1-kory.maincent@bootlin.com>
On Wed, 5 Oct 2022 09:58:13 +0200
Köry Maincent via buildroot <buildroot@buildroot.org> wrote:
> From: Kory Maincent <kory.maincent@bootlin.com>
>
> Update description:
> TF-A to v2.4-stm32mp-r1
> U-boot to version v2020.10-stm32mp-r2.1
> Linux to v5.10-stm32mp-r2.1
>
> This patch also updates U-boot to to use FIP image.
>
> Reference:
>
> https://octavosystems.com/octavo_products/osd32mp1-red/
>
> The device tree blobs, and the U-boot patches come from Octavo System:
>
> https://github.com/octavosystems/meta-octavo-osd32mp1
>
> Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
I've applied both patches, but to be honest, I hate having these huge
Device Tree files in Buildroot...
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-10-06 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 7:58 [Buildroot] [PATCH 1/2] board/octavo/osd32mp1-red: update BSP components Köry Maincent via buildroot
2022-10-05 7:58 ` [Buildroot] [PATCH 2/2] board/octavo/osd32mp1-brk: " Köry Maincent via buildroot
2022-10-06 20:03 ` Thomas Petazzoni via buildroot [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=20221006220335.22132976@windsurf \
--to=buildroot@buildroot.org \
--cc=kory.maincent@bootlin.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.