mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: ANDY KENNEDY <ANDY.KENNEDY@adtran.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: I want to use Barebox
Date: Fri, 13 Apr 2012 20:38:12 +0000	[thread overview]
Message-ID: <F9C551623D2CBB4C9488801D14F864C614BE42@ex-mb1.corp.adtran.com> (raw)
In-Reply-To: <20120413202303.GT3852@pengutronix.de>

> > 1)  I have a concern that barebox is not mainstream enough yet.
> 
> Well by using it you could make it a bit more mainstream ;)

Hmmm.  That will be an UP HILL battle for me, I'm sure.  Are there any
stats on how many folks / who all uses Barebox currently?


> others like gpio or mtd are from the kernel. Porting these over usually
> means some refactoring. For example U-Boot has no device/driver model,
> so you would have to add registration and probe functions. The
> complicated thing about drivers (at least in the bootloader world) is
> getting the hardware accesses right, and these can be copied from the
> original driver.
> 

Confused.  So, you are saying that going from U-Boot to Barebox is
not trivial (being the driver model is different), but these BSPs
often times have drivers in the Linux kernel.  Granted, these are
arch drivers and thus are probably not easily ripped out of the Linux
kernel (most platform specific drivers I've seen are so intermingled
with other Kernel calls it would be difficult to detach that).  Would
it be less painful to port from the arch directory in the kernel than
from U-Boot?

> I hope this helps with your decision

This does not sway me more to using Barebox, that is impossible ;).
Perhaps it will give me fodder for convincing others.

> 
>  Sascha

Thanks for your reply.  It was most useful.
Andy

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

  reply	other threads:[~2012-04-13 20:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 15:37 ANDY KENNEDY
2012-04-13 20:23 ` Sascha Hauer
2012-04-13 20:38   ` ANDY KENNEDY [this message]
2012-04-13 21:12     ` Eric Bénard
2012-04-14  4:18       ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-14  4:28   ` 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=F9C551623D2CBB4C9488801D14F864C614BE42@ex-mb1.corp.adtran.com \
    --to=andy.kennedy@adtran.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