All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Berger <gmane@reliableembeddedsystems.com>
To: poky@pokylinux.org
Subject: Re: beagleboard and latest from git
Date: Fri, 13 May 2011 22:26:54 +0300	[thread overview]
Message-ID: <iqk0lv$264$1@dough.gmane.org> (raw)
In-Reply-To: <iqjk2n$otv$1@dough.gmane.org>

Hi,

I switched a bit around between various versions in the meantime and
that's what I figured out:

1) the latest u-boot (or some configuration of it) from git does not
seem to work for the beagleboard

2) if I use U-Boot 2011.03-00038-g8d4addc-dirty (May 13 2011 - 00:01:02)
which comes with bernard-5.0.1 things look much better.

U-Boot 2010.12-00038-g8d4addc-dirty (May 13 2011 - 08:44:08) is the
suspect. Why does the latest and greatest from git use an older u-boot
version than bernard 5.0.1?

I interrupt the u-boot autoboot and do the following:

OMAP3 beagleboard.org # sete console "ttyO2,115200n8"
OMAP3 beagleboard.org # mmc rescan ${mmcdev}
OMAP3 beagleboard.org # run loaduimage
reading uImage

2632316 bytes read
OMAP3 beagleboard.org # run mmcboot

and voila:

Yocto (Built by Poky 5.0) 1.0+snapshot-20110512 beagleboard ttyO2

beagleboard login: root
root@beagleboard:~#

This time even with networking.

This means that the latest and greatest rootfs seems OK.

Regards,

Robert


..."It is NOT portable (uses 386 task switching etc), and it probably
never will support anything other than AT-harddisks, as that's all I
have :-(." - Linus Benedict Torvalds(torvalds@klaava.Helsinki.FI),
1991-08-25 23:12:08 PST -

My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1




  reply	other threads:[~2011-05-13 19:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-13 15:51 beagleboard and latest from git Robert Berger
2011-05-13 19:26 ` Robert Berger [this message]
2011-05-13 20:19   ` Darren Hart

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='iqk0lv$264$1@dough.gmane.org' \
    --to=gmane@reliableembeddedsystems.com \
    --cc=poky@pokylinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.