Hi > when secure boot is involed, I'd think the whole device will be sufficiently > locked down to also disallow custom kernels. Otherwise that wouldn't be > a secure boot. (bootloader verifying kernel image + rootfs) If you look at the Android boot chain this is the case when in "locked mode", uboot (or whatever 2nd stage you have) validates the boot / kernel image either via public key or symmetric key. However in unlocked mode using something like the "unlock" fastboot command this check is disabled but the signature validation of the uboot / second stage is still enforced. AFAIK this process is part of the Android device validation suite. Yes Android is only one OS vendor, however it is probably the largest use case for this SoC. > So we're in a pickle here. As Peter said, _if_ we wanted to change the ids > one more time, to allow those vendor uboot hacks, now would be the time. > > But then als Mark said, the current bindings are used already in a number > of different places and aren't broken per se. I agree, its a bit messy, I was just raising the patch now just in case it was something that could be changed with relative ease, if thats not the case the patch can be ignored Thanks In Advance On Mon, Mar 27, 2023 at 10:07 AM Heiko Stübner <heiko@xxxxxxxxx> wrote: > > Am Montag, 27. März 2023, 01:40:34 CEST schrieb Shane Francis: > > Hi Mark > > > > > That code makes absolutely no sense. This tries to transplant > > > phandles from one DTB into another DTB? Mainline U-Boot has no code > > > like that. I think this is just broken beyond repair. > > > > Yeah its a dumb bit of code, my concern when looking at the R6S is that > > when devices look to get mainline support that are unable to change to > > another uboot build (such as when secure boot is involved) > > when secure boot is involed, I'd think the whole device will be sufficiently > locked down to also disallow custom kernels. Otherwise that wouldn't be > a secure boot. (bootloader verifying kernel image + rootfs) > > > > those will > > have a hard time as this ABI breakage ship would have departed long > > ago. And the RK3588 support is very new..... I thought about raising it > > now. > > > > The question for me is how (in the future) will devices with this SoC > > and cannot modify their uboot make use of the mainline kernel ? > > > > I have looked into undoing this clock configuration during early kernel > > boot but the SoC seems to hard lock. > > > > I apologise if raising this patch was a bad idea but like I stated to > > Krzysztof I am just onboarding this device as a hobby. However > > from an outside standpoint having a potential breakage like this > > because starting from 0 looked cleaner than 1 seems a bit odd to > > me. > > In general we can't be on the "whim" of SoC vendors. > > I.e. dt-bindings are supposed to be reviewed _first_ and not invented in > some SoC vendor's dark basement. That did work in the past with Rockchip > but in recent years they did loose most of their upstream momentum it > seems. > > Because vendors often invent unpractical or even conflicting bindings on > their own. > > So we're in a pickle here. As Peter said, _if_ we wanted to change the ids > one more time, to allow those vendor uboot hacks, now would be the time. > > But then als Mark said, the current bindings are used already in a number > of different places and aren't broken per se. > > So I guess either decision possibility is bad ;-) > > > Heiko > > > > On Sun, Mar 26, 2023 at 10:42 PM Mark Kettenis <mark.kettenis@xxxxxxxxx> wrote: > > > > > > > Date: Sun, 26 Mar 2023 22:02:39 +0200 > > > > From: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx> > > > > > > > > On 26/03/2023 19:51, Shane Francis wrote: > > > > >> Bootloader also does not use mainline DTS, so where is exactly the problem? > > > > > > > > > > In this case uboot does load the target DTB, and it seems a common > > > > > function in rockchips > > > > > downstream boot process, see : > > > > > > > > > > https://github.com/rockchip-linux/u-boot/blob/ef1dd650042f61915c4859ecc94623a09a3529fa/arch/arm/mach-rockchip/kernel_dtb.c#L70 > > > > > > > > > > > That code makes absolutely no sense. This tries to transplant > > > phandles from one DTB into another DTB? Mainline U-Boot has no code > > > like that. I think this is just broken beyond repair. > > > > > > > U-Boot comes with its own DTB, so what does it means "loads the target > > > > DTB"? From where? The one appended to the kernel zImage? No, it cannot... > > > > > > > > Any component which operates on mainline DTB must conform to the > > > > bindings (with respect to the ABI), thus your arguments here mean you > > > > are not allowed to change ABI in the future. Never. This change, > > > > assuming original binding was broken, could be warranted. > > > > > > The current mainline binding isn't broken; 0 is a perfectly fine clock > > > index. The RK3588 clock bindings are already used by U-Boot (too late > > > to fix for the 2023.4 release happening in a few days) and OpenBSD > > > (too late to fix for the 7.3 release that will happen a few weeks). > > > Changing the clock binding will just create more chaos. > > > > > > <rant> > > > > > > What is broken here is the development process. Rockchip shouldn't be > > > maintaining these heavily modified forks of U-Boot and the Linux > > > kernel. But at the same time mainline Linux developers should not be > > > asking for arbitrary changes to the device tree bindings just to > > > satisfy some unwritten rules. The clock bindings were originaly > > > submitted with clock numbers identical to those that Rockchip uses: > > > > > > https://lore.kernel.org/all/20220623160329.239501-2-sebastian.reichel@xxxxxxxxxxxxx/ > > > > > > but then changed because a reviewer wanted them to start at 0 and > > > didn't want any holes: > > > > > > https://lore.kernel.org/all/0841741a-22f6-40f6-c745-6065dfdbcb1d@xxxxxxxxxx/ > > > > > > This isn't the first example where this happened. And it invariably > > > leads to confusion and breakage in projects that try to follow the > > > mainline Linux device tree bindings. > > > > > > </rant> > > > > > >
