From: Fabio Estevam Date: Sun, 15 Oct 2017 13:01:48 +0000 (-0200) Subject: net: fec_mxc: Change "error frame" message to debug level X-Git-Tag: v2017.11-rc4~22^2~8 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=41b93679fd69bbb8c335eb212a3f8aa6c9c662db;p=u-boot net: fec_mxc: Change "error frame" message to debug level 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 Suggested-by: Heinrich Schuchardt Signed-off-by: Fabio Estevam --- diff --git a/drivers/net/fec_mxc.c b/drivers/net/fec_mxc.c index f16b2990d7..433e19f0f8 100644 --- a/drivers/net/fec_mxc.c +++ b/drivers/net/fec_mxc.c @@ -882,7 +882,7 @@ static int fec_recv(struct eth_device *dev) len = frame_length; } else { if (bd_status & FEC_RBD_ERR) - printf("error frame: 0x%08x 0x%08x\n", + debug("error frame: 0x%08x 0x%08x\n", addr, bd_status); }