On Mon, Nov 25, 2024 at 10:32 PM E Shattow <[email protected]> wrote: > > On Fri, Nov 22, 2024 at 6:33 AM Loic Devulder <[email protected]> wrote: > > > > Hi guys! > > > > I played with latest openSUSE TW image [1] for VisionFive2 and I also had > > an issue but not exactly > > the same Andreas had. Booting the OS from an sdcard gave me the grub cli > > but not the menu. With > > Heinrich's patch I was able to boot on grub menu as fully boot the OS as > > well. > > > > Tested-by: Loic Devulder <[email protected]> > > > > -- > > Loic Devulder <[email protected]> > > Senior QA Engineer | SUSE Software Solutions > > > > [1] - > > https://download.opensuse.org/ports/riscv/tumbleweed/images/openSUSE-Tumbleweed-RISC-V-JeOS-starfivevisionfive2.riscv64-2024.11.10-Build1.19.raw.xz > > > > On Thu, 2024-11-21 at 16:24 +0100, Andreas Schwab wrote: > > > On Nov 21 2024, Heinrich Schuchardt wrote: > > > > > > > Our MMC driver for JH7110 boards only supports reading to the low 4 GiB > > > > of > > > > memory. Booting boards with more memory requires > > > > EFI_LOADER_BOUNCE_BUFFER. > > > > > > That doesn't change the situation with the booting problem I have. > > > > > What was this series supposed to do and how to test for it properly? > I did not see any difference, still just failure on 4GB and 8GB DRAM > ... is my testing method wrong? > > -E
Postscript: After some discussion with Sughosh we find that yes I am testing this code path but "the logic of addr_aligned() needs to be changed". This series is correct but the commit description is confusing by omission of information: There is a 1GB offset in address space to DRAM, and so any board with more than 3GB DRAM are affected. If reading the commit message without knowing this information it seems like 4GB DRAM board would not be affected but such address space goes to 5GB. I was hoping for some reply from Heinrich to resolve why testing results are not consistent and to offer a clearer commit message before the pull request. With that, and my thanks to Heinrich for speedy bug fixing, Tested-by: E Shattow <[email protected]>
