mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Porting barebox to Novena: misc questions
Date: Fri, 14 Mar 2014 04:03:56 +0100	[thread overview]
Message-ID: <20140314030356.GC6478@ns203013.ovh.net> (raw)
In-Reply-To: <20140313203009.GT17250@pengutronix.de>

On 21:30 Thu 13 Mar     , Sascha Hauer wrote:
> On Thu, Mar 13, 2014 at 08:42:52PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On 08:38 Thu 13 Mar     , Sascha Hauer wrote:
> > > Hi Sean,
> > > 
> > > On Thu, Mar 13, 2014 at 10:04:35AM +0800, Sean Cross wrote:
> > > > Hi,
> > > > 
> > > > I've finally managed to get U-Boot's SPL to configure DDR3 and load
> > > > barebox off of a FAT partition on an i.MX6DL.  I also have a barebox
> > > > build with most features turned on, and I'm running into a number of
> > > > problems.  barebox is able to load a zImage off of the FAT partition,
> > > > set up ATAGs, and jump to it.  So I have the basics done.  But there are
> > > > lots of little things that aren't working.
> > > > 
> > > > When I boot without an Ethernet cable plugged in, the "timeout" command
> > > > takes a very long time to complete.  It generally freezes at "Hit any
> > > > key to stop autoboot:  3" and tends to ignore input for around ten
> > > > seconds.  How can I prevent this from happening, short of compiling out
> > > > FEC support?
> > > 
> > > Are you trying to start from network without a cable plugged in? When I
> > > start from network without a cable I get:
> > > 
> > > running /env/bin/init...
> > > 
> > > Hit m for menu or any other key to stop autoboot:  1
> > > blspec: blspec_scan_directory: net loader/entries
> > > booting net
> > > dhcp failed: Network is down
> > > dhcp: Network is down
> > > 
> > 
> > I get the same issue on Calao USB keys
> > 
> > this is quite anoying
> > 
> > can we fix it
> 
> Well if we try booting from network then we have to wait until it's
> clear that there's no link.
> 
> It may be that I don't understand the actual problem or issue.

I do agree if you try to boot on the network we have to wait the xs of timeout

The problem is that you have now a timeout even beofre the autoboot timeout
and even before to try to boot

I did not investigate further but the problem is there

Best Regards,
J.
> 
> Sascha
> 
> -- 
> Pengutronix e.K.                           |                             |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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

  reply	other threads:[~2014-03-14  3:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13  2:04 Sean Cross
2014-03-13  7:38 ` Sascha Hauer
2014-03-13 10:18   ` Sean Cross
2014-03-13 20:27     ` Sascha Hauer
2014-03-14  3:35       ` Sean Cross
2014-03-14  8:22         ` Sascha Hauer
2014-03-17  4:28           ` Sean Cross
2014-03-17  7:18             ` Sascha Hauer
2014-03-17  7:31               ` Alexander Aring
2014-03-17  7:44               ` Sean Cross
2014-03-17 10:53                 ` Sascha Hauer
2014-03-18  3:35                   ` Sean Cross
2014-03-18  8:36                     ` Sascha Hauer
2014-03-18  8:43                       ` Sean Cross
2014-03-18  8:58                         ` Sascha Hauer
2014-03-18  9:04                           ` Sean Cross
2014-03-13 19:42   ` Jean-Christophe PLAGNIOL-VILLARD
2014-03-13 20:30     ` Sascha Hauer
2014-03-14  3:03       ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2014-03-13 20:43 ` Eric Bénard
2014-03-13 21:26   ` Sascha Hauer
2014-03-14  3:13     ` Jean-Christophe PLAGNIOL-VILLARD

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=20140314030356.GC6478@ns203013.ovh.net \
    --to=plagnioj@jcrosoft.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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