Skip to content
Snippets Groups Projects
  1. Nov 01, 2017
  2. Oct 30, 2017
    • Fabio Estevam's avatar
      net: fec_mxc: Change "error frame" message to debug level · 41b93679
      Fabio Estevam authored
      
      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: default avatarJonathan Gray <jsg@jsg.id.au>
      Suggested-by: default avatarHeinrich Schuchardt <xypron.glpk@gmx.de>
      Signed-off-by: default avatarFabio Estevam <fabio.estevam@nxp.com>
      41b93679
  3. Oct 29, 2017
  4. Oct 27, 2017
  5. Oct 26, 2017
  6. Oct 25, 2017
  7. Oct 23, 2017
  8. Oct 21, 2017
  9. Oct 20, 2017
  10. Oct 17, 2017
  11. Oct 16, 2017
  12. Oct 15, 2017
Loading