From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: how easy to add extra config for NAND-less beagle?
Date: Fri, 16 Nov 2012 06:16:03 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1211160614560.4073@oneiric> (raw)
In-Reply-To: <20121115192630.GJ10369@pengutronix.de>
On Thu, 15 Nov 2012, Sascha Hauer wrote:
> On Thu, Nov 15, 2012 at 11:39:58AM -0500, Robert P. J. Day wrote:
> >
> > yup, i'm testing that shortly, but my question was more along the
> > lines of, rather than having to disable all NAND-related
> > functionality *manually*, how easy/worthwhile would it be to create an
> > additional make target that reflects a beagle *without* NAND flash?
> >
> > one significant difference between a classic beagle and a current xM
> > is the total lack of NAND flash, and that's not a minor difference.
> > it means you can remove all barebox functionality related to that --
> > NAND routines and support, MTD stuff, JFFS2(?) support, and so on.
> > this could be automated by creating a couple new configs, say:
> >
> > make dm3730_beaglexm_xload_defconfig
> > make dm3730_beaglexm_defconfig
> >
> > so that the result really matches the underlying board.
> >
> > is this worth doing? it would seem to be fairly easy, i can whip
> > something up and test it.
>
> I don't think this is worth it. We should rather keep the number of
> defconfigs low. Splitting them means we have to maintain them and
> keep them in sync. Also it means to increase the time needed to
> compile all defconfigs (which I do routinely, currently on every
> commit).
ok, that makes sense. i'll still have a couple questions later on
the proper configuration of barebox for flash-less systems like the
xM. thanks.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2012-11-16 11:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 14:36 Robert P. J. Day
2012-11-15 16:16 ` Sascha Hauer
2012-11-15 16:39 ` Robert P. J. Day
2012-11-15 19:22 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-15 19:26 ` Sascha Hauer
2012-11-16 11:16 ` Robert P. J. Day [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=alpine.DEB.2.02.1211160614560.4073@oneiric \
--to=rpjday@crashcourse.ca \
--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