[PATCH 0/2] configs: JH7110: enable EFI_LOADER_BOUNCE_BUFFER

[E Shattow]

On Thu, Nov 21, 2024 at 8:05 AM Heinrich Schuchardt
<heinrich.schuchardt at canonical.com> wrote:
>
> On 21.11.24 16:24, 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.
> >
>
> Do you relate to
> https://lore.kernel.org/u-boot/mvm8qtnv310.fsf@suse.de/
> where you had some problem reading the FAT file system and which was for
> as system with only 4 GiB of memory?
>
> In E Shattow's case on a board with 8 GiB the file was read without
> error but then reported as not being an EFI binary.
>
> Best regards
>
> Heinrich
>
>

Hi,

Test failed for both boards here with origin/master then applying this
series, then starfive_visionfive2_defconfig target and set
CONFIG_BOOTSTD=n following with oldconfig target.

Testing failed on 4GB Star64:

Hit any key to stop autoboot:  0
Unknown command 'bootflow' - try 'help'
StarFive # bootefi bootmgr
Card did not respond to voltage select! : -110
Not a PE-COFF file
Loading Boot0000 'mmc 0' failed
Booting: nvme 0
error: no such partition.
grub rescue>

The grub EFI loader from EFI System Partition on eMMC fails to load.
The same EFI System Partition data on NVMe is successful.

Testing failed on 8GB Mars CM Lite:

Hit any key to stop autoboot:  0
Unknown command 'bootflow' - try 'help'
StarFive # bootefi bootmgr
Card did not respond to voltage select! : -110
Failed to load EFI variables
Error reading cluster
Loading Boot0000 'mmc 0' failed
EFI boot manager: Cannot load any image

We see that the grub EFI loader from this EFI System Partition fails
to load from MMC (SD Card).

Procedure that was used to update SPI NOR flash on either board
includes sanitizing the environment variable storages:
env erase; env default -a -f; sf probe; dhcp; env set serverip <ip
address of tftp server>
tftpboot $loadaddr u-boot-spl.bin.normal.out; sf update $loadaddr 0 $filesize
tftpboot $loadaddr u-boot.itb; sf update $loadaddr 100000 $filesize
fatrm mmc 0:1 ubootefi.var

This does not say anything for or against the validity of the patch
series as the root cause is a limitation of the dw mmc driver on
JH7110 not resolved here.

-E