On 25.11.25 10:45, Sune Brian wrote: >> That's because it never used that (intentionally). We always booted from >> a partition ID, but the old versions had all methods enabled, and that >> papered over the fact that they were mangled into something that was >> supposed to use partition ID but used bits from the other paths as well >> to compensate mistakes. > > Are you using the mainstream or Altera U-Boot trunk from the beginning?
We never used downstream. > Why does it sound like we are not on the same page? Different boards. > > It is not even allowed to select two settings since early 2025 major > changes on the detection of the boot method. > > [*] Use raw reads to locate the next boot phase > │ │ > │ │ Method for > locating next phase of boot (e.g. U-Boot) (MMC raw mode: by partition > type) ---> │ │ > │ │ (0xa2) Partition Type > on the MMC to load U-Boot from > > How can you select two at a time? I was referred to the time before the cleanup attempts. > >> >> Just study my series to see all the breakages. It was never clean, >> though, and that may explain working setups by luck. > > I am using a custom board na socfpga on Cyclone V SoC. There are > no such things about luck. Either it works or fails. > > Completely lost on your case and the patch. Your defconfig may compensate the bugs then. I was not lucky in finding a reasonable way to adjust the de0 config to make things work again. Jan -- Siemens AG, Foundational Technologies Linux Expert Center
