From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Brugger Date: Wed, 6 Nov 2019 20:40:08 +0100 Subject: [U-Boot] [PATCH] ARM: defconfig: add unified config for RPi3 and RPi4 In-Reply-To: <10ddcf72-d4ba-ec8a-4fc7-72626500811a@gmx.de> References: <20191106144104.28177-1-matthias.bgg@kernel.org> <10ddcf72-d4ba-ec8a-4fc7-72626500811a@gmx.de> Message-ID: <372fbe15-a0bc-b4a5-6f4f-180c6580146a@suse.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 06/11/2019 19:06, Heinrich Schuchardt wrote: > On 11/6/19 3:41 PM, matthias.bgg at kernel.org wrote: >> From: Matthias Brugger >> >> Provide a defconfig which allows us to boot Raspberrry Pi 4 >> and Raspberry Pi 3 Model B/B+ >> Instead of using the embedded DTB as done in RPi3 we use the >> devicetree provided by the firmware. > > How different are the DTBs provided by different firmware releases? > > Could we run into problems because some elder or newer firmware releases > are not supported by U-Boot? - This prospect is what makes your patch a > bit scary to me. That could happen, but I suppose especially for older releases. Newer releases tend to change in the direction of upstream. > > Which different firmware releases did you test against? > > Do you plan to keep the existing defconfigs and dtbs? > I didn't do any extensive testing to be honest. We are using the DTB from the firmware on RPi4 already, and I expect that newer firmwares won't break U-Boot. My idea is to keep the existing defconfigs. Apart from being a good fallback option if really something breaks, there might be some distros use U-Boot with this config files and I don't want to break the setup for them. Regards, Matthias