From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: how easy to add extra config for NAND-less beagle?
Date: Thu, 15 Nov 2012 17:16:15 +0100 [thread overview]
Message-ID: <20121115161615.GI10369@pengutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1211150924030.1247@oneiric>
Hi Robert,
On Thu, Nov 15, 2012 at 09:36:37AM -0500, Robert P. J. Day wrote:
>
> returning to playing with barebox after lengthy hiatus and i asked
> an equivalent question on the u-boot list, let's see if it's relevant
> here.
>
> i did a regular configure and build for my beagle xM (rev C) which,
> unlike the beagle classic, has no NAND flash:
>
> $ make omap3530_beagle_xload_defconfig ; make
> $ make omap3530_beagle_defconfig ; make
>
> then copied MLO and barebox.bin to an appropriate card and, lo, it
> booted nicely and i'm currently sitting in barebox:
>
> barebox@Texas Instrument's Beagle:/ version
>
> barebox 2012.10.0-00283-gd65d9df #2 Thu Nov 15 06:45:21 EST 2012
>
> thing is, this build has a good deal of NAND-related functionality
> that is of no use whatsoever on the current beagle xMs, so i'm
> interested in how little work it would take to add an extra config
> that would deselect everything related to NAND. (obviously, having
> that functionality there doesn't *hurt*, but i'm planning to use
> barebox in my new embedded linux courses and it would be nice to be
> able to build for an xM and have it *totally* correspond to the actual
> hardware.) it shouldn't be hard -- simply deselecting anything
> related to NAND, MTD or JFFS2 should do the trick.
Disable MTD support and if you want also the protect/erase commands:
make menuconfig
Drivers --->
[ ] Memory Technology Device (MTD) support --->
commands --->
flash --->
[ ] protect/erase
Saves you around 35Kb of binary space
>
> rday
>
> p.s. when i run "devinfo", i see a couple NAND-related entries:
>
> devices:
> ... snip ...
> `---- gpmc_nand0
The nand device, probably present even when you disable nand support.
However, no driver will bind to it if you disable it.
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
next prev parent reply other threads:[~2012-11-15 16: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 [this message]
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
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=20121115161615.GI10369@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=rpjday@crashcourse.ca \
/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