[U-Boot] [PATCH] net: fec_mxc: Change "error frame" message to debug level

Fabio Estevam festevam at gmail.com
Mon Oct 30 23:42:31 UTC 2017


Hi Joe,

On Sun, Oct 15, 2017 at 11:01 AM, Fabio Estevam <festevam at gmail.com> wrote:
> From: Fabio Estevam <fabio.estevam at nxp.com>
>
> 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 <jsg at jsg.id.au>
> Suggested-by: Heinrich Schuchardt <xypron.glpk at gmx.de>
> Signed-off-by: Fabio Estevam <fabio.estevam at nxp.com>

Do you think this one can be applied for 2017.11?

Thanks


More information about the U-Boot mailing list