mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: barebox@lists.infradead.org
Subject: i.MX25 : Ethernet link detection blocking console
Date: Fri, 21 Feb 2014 17:22:09 +0100	[thread overview]
Message-ID: <20140221172209.41962f85@e6520eb> (raw)

Hi,

while testing 2014.02 on eukrea-cpuimx25 board, I meet this problem :
- I get "Hit any key to stop autoboot:  1"
- whatever I press on the keyboard, the autoboot continues
- if I send characters through the serial port before barebox reach
  the autoboot line, then I'll get the command line but only when the
  link detection will have finished (check log below).

Any idea what could be wrong here ?

Thanks
Eric

barebox 2014.02.0-dirty #5 Fri Feb 21 16:52:37 CET 2014


Board: Eukrea CPUIMX25
netconsole: registered as cs1
mdio_bus: miibus0: probed
nand: ONFI param page 0 valid
nand: ONFI flash detected
nand: NAND device: Manufacturer ID: 0x2c, Chip ID: 0x38 (Micron
MT29F8G08ABABAWP), 1024MiB, page size: 4096, OOB size: 224
Bad block table found at page 262016, version 0x01
Bad block table found at page 261888, version 0x01
imxfb imxfb: i.MX Framebuffer driver
imx-esdhc imx-esdhc0: registered as imx-esdhc0
ehci ehci0: USB EHCI 1.00
malloc space: 0x83700000 -> 0x83efffff (size 8 MiB)
running /env/bin/init...

Hit any key to stop autoboot:  1100Mbps full duplex link detected
                                ^ it waits here until the link is
                                detected then I get the prompt (only if
                                the key was pressed before reaching the
                                autoboot line)

barebox@Eukrea CPUIMX25:/ <INTERRUPT>

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2014-02-21 16:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21 16:22 Eric Bénard [this message]
2014-02-24  8:27 ` Sascha Hauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140221172209.41962f85@e6520eb \
    --to=eric@eukrea.com \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox