From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: is barebox meant to be the next generation of u-boot?
Date: Sat, 19 Dec 2009 03:56:29 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0912190351400.32196@localhost> (raw)
i just want to clarify the direction of barebox -- is it meant to
eventually supplant u-boot? i ask since i want to know if it's not
worth investing much more time in u-boot (v1) if things are eventually
going to switch over to barebox.
specifically, i want to use it on my beagleboard, so i "git" checked
out the source for barebox, configured it for the beagle, built it
with the denx "arm-linux-" toolchain and it booted. i haven't got any
further than that so far but that's all i was after -- just getting it
to boot to the barebox prompt.
at this point, if barebox is merely *adequate* to do what i want and
supports booting my beagleboard fully, is there any reason i don't
just move to it entirely, knowing it does what i need and it's only
going to get better? thanks.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2009-12-19 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 8:56 Robert P. J. Day [this message]
2009-12-19 21:49 ` Robert Schwebel
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=alpine.LFD.2.00.0912190351400.32196@localhost \
--to=rpjday@crashcourse.ca \
--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