summaryrefslogtreecommitdiffstats
path: root/common/Makefile
diff options
context:
space:
mode:
authorSascha Hauer <s.hauer@pengutronix.de>2012-10-15 12:28:53 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2012-10-17 20:23:41 +0200
commitbed8fb6de1a1a98d25f3a8289b35395227a652e1 (patch)
tree6a651a5e154527b8785df70020a14e93d88ee9bd /common/Makefile
parent73e56c348954246a1f633d10335d10fe605f586f (diff)
downloadbarebox-bed8fb6de1a1a98d25f3a8289b35395227a652e1.tar.gz
barebox-bed8fb6de1a1a98d25f3a8289b35395227a652e1.tar.xz
Add in-system barebox update infrastructure
Currently in-system update means to write an arbitrary file to an arbitrary device. There is no sanity check if the flashed image is of the right type or will fit onto the device. Furthermore some SoCs need a special preparation step for their images before flashing them. This adds a barebox in-system update infrastructure. Boards can register update handlers which know how to make the board bootable. The available handlers can be listed to be able to select one, different force levels give the user the chance to know it better. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'common/Makefile')
-rw-r--r--common/Makefile1
1 files changed, 1 insertions, 0 deletions
diff --git a/common/Makefile b/common/Makefile
index 132bd06068..d82fc998bc 100644
--- a/common/Makefile
+++ b/common/Makefile
@@ -38,6 +38,7 @@ obj-$(CONFIG_MENU) += menu.o
obj-$(CONFIG_PASSWORD) += password.o
obj-$(CONFIG_MODULES) += module.o
obj-$(CONFIG_FLEXIBLE_BOOTARGS) += bootargs.o
+obj-$(CONFIG_BAREBOX_UPDATE) += bbu.o
extra-$(CONFIG_MODULES) += module.lds
extra-y += barebox_default_env barebox_default_env.h