Hi Joe, On Sun, Oct 15, 2017 at 11:01 AM, Fabio Estevam <[email protected]> wrote: > From: Fabio Estevam <[email protected]> > > As reported by Jonathan Gray: > > "After the recent changes to add SimpleNetworkProtocol to efi_loader > when booting off mmc via an efi payload that doesn't use > SimpleNetworkProtocol U-Boot's fec_mxc driver will now display > various "error frame" messages. > .... > MMC Device 1 not found > MMC Device 2 not found > MMC Device 3 not found > Scanning disks on sata... > Found 6 disks > reading efi/boot/bootarm.efi > 67372 bytes read in 32 ms (2 MiB/s) > ## Starting EFI application at 12000000 ... >>> OpenBSD/armv7 BOOTARM 1.0 > error frame: 0x8f57ec40 0x00003d74 > error frame: 0x8f57ec40 0x00007079 > error frame: 0x8f57ec40 0x00006964 > error frame: 0x8f57ec40 0x00006f6f > error frame: 0x8f57ec40 0x0000726f > error frame: 0x8f57ec40 0x00002074 > error frame: 0x8f57ec40 0x00006f6f" > > Heinrich Schuchardt explains: > > "A receive FIFO overrun can be expected if network packages are not > processed. > With the network patches we check if a package is available quite often." > > Move the "error frame" messages to debug level so that a clean output > log can be seen. > > Reported-by: Jonathan Gray <[email protected]> > Suggested-by: Heinrich Schuchardt <[email protected]> > Signed-off-by: Fabio Estevam <[email protected]>
Do you think this one can be applied for 2017.11? Thanks _______________________________________________ U-Boot mailing list [email protected] https://lists.denx.de/listinfo/u-boot
