From: Sascha Hauer <s.hauer@pengutronix.de>
To: Nathan <naroyce@hotmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: UBOOT2 JMP
Date: Sun, 3 Mar 2013 14:16:32 +0100 [thread overview]
Message-ID: <20130303131632.GX1906@pengutronix.de> (raw)
In-Reply-To: <COL123-DS8D9B04B0AA3EF6F54B64BA2FD0@phx.gbl>
On Tue, Feb 26, 2013 at 09:11:53PM -0600, Nathan wrote:
> “UBOOT2 JMP ” is what displays during bootup using VirtualBox.
There may be something broken on x86 support.
> This is after compiling with:
> export ARCH=x86
> make generic_defconfig
> make
> fdisk /dev/sdb...partition...mkfs.ext2 /dev/sdb1
> ./scripts/setupmbr/setupmbr –s 32 –m ./barebox.bin –d /dev/sdb
>
> I think there may be something I’m missing after “setupmbr” or I need
> to change a config value after setting “generic_defconfig”. My end
> goal is to use barebox on my ODroid. I was “somewhat” familiar with
> syslinux but learned it doesn’t support ARM. I learned that Samsung
> Exynos in the ODroid uses UBoot and that barebox is the next evolution
> of uboot. I’m hoping it will be forward compatible (uboot in SoC calls
> barebox in MBR of SD which calls my linux kernel in SD partition).
When you want to use barebox on the ODroid, why do you build it for x86
then? You have to build for ARM. Unfortunately the Exynos is not
yet supported, so you would have to do the porting effort yourself.
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
prev parent reply other threads:[~2013-03-03 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 3:11 Nathan
2013-03-03 13:16 ` Sascha Hauer [this message]
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=20130303131632.GX1906@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=naroyce@hotmail.com \
/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