[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPDEroWUeR3iUFnjVr6WFLg3=dkML+5cbRPph9bj64F=zc1UWA@mail.gmail.com>
Date: Thu, 4 Jul 2024 09:34:02 +1000
From: Leith Bade <leith@...e.nz>
To: frank-w@...lic-files.de
Cc: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
Matthias Brugger <matthias.bgg@...il.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org,
devicetree@...r.kernel.org, Daniel Golle <daniel@...rotopia.org>,
Rob Herring <robh+dt@...nel.org>, Frank Wunderlich <linux@...web.de>
Subject: Re: Aw: [PATCH v3 1/2] arm64: dts: mt7986: add dtbs with applied
overlays for bpi-r3
> Yes, 1st reason is to check if overlay can be applied to base dts (the part rob was requested). The second thing that was solved is that some users wanting a "full" dtb without the need to handle overlays in bootloader. Due to hardware design of the board there are 4 "full" dtb's.
I have been looking at using the "u-boot-update" package in Debian to
generate an extlinux.conf file so I can use the U-boot standard/distro
boot. This script seems to currently assume that you pick a single
.dtb file for the board, and then the user can put additional .dtbo
files in /boot/dtbo/ for any additional hardware the user has plugged
in.
So having a series of "merged" base files would be useful for this use case.
Thanks,
Leith Bade
Powered by blists - more mailing lists