barebox - barebox master repository

	Commit message (Collapse)	Author	Age	Files	Lines
*	Merge branch 'for-next/imx-bbu-nand-fcb'	Sascha Hauer	2016-04-08	1	-0/+1
\|\
\| *	bbu: Allow to refresh/repair images	Sascha Hauer	2016-04-08	1	-0/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Some SoCs allow to store multiple boot images on a device in order to improve robustness. This adds a -r option to barebox_update to indicate we do not want to make an update but instead repair/refresh an existing image. Handlers which want to support this feature must set the BBU_HANDLER_CAN_REFRESH flag during registration. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* \|	bbu: print and evaluate image Metadata	Sascha Hauer	2016-04-06	1	-0/+1
\|/ \| \| \| \| \| \| \| \| \| \|	With imd we can store metadata in barebox images. Let's use this information to further verify that the image that is to be flashed is the correct one. This patch extracts the device tree compatible from the image and compares it with the one from the currently running barebox. If it doesn't match the update is aborted with a warning. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
*	bbu: Add function to check if an update handler exists	Markus Pargmann	2016-02-18	1	-0/+2
\| \| \| \| \| \| \| \|	This adds a function to check for the existence of an update handler based on the supplied bbu_data. Signed-off-by: Markus Pargmann <mpa@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
*	Merge branch 'for-next/imx-bbu-nand-fcb'	Sascha Hauer	2015-07-03	1	-0/+14
\|\ \| \| \| \| \| \| \| \|	Conflicts: common/Kconfig
\| *	imx-bbu-nand-fcb: make available for i.MX28 aswell	Sascha Hauer	2015-06-12	1	-0/+5
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The code can be used with slight modifications on i.MX28 aswell. Add a i.MX28 registration function and move the differences to function callbacks. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
\| *	ARM: i.MX6: bbu nand: Move to common place	Sascha Hauer	2015-06-12	1	-0/+9
\| \| \| \| \| \| \| \| \| \| \| \|	The code can be used on i.MX28 aswell, so move it to a common place. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* \|	bbu: Add a standard file-to-device-copy handler	Sascha Hauer	2015-07-01	1	-0/+9
\|/ \| \| \| \| \| \| \|	The most standard update handler will simply copy a file to a device. This can be shared across several users, so add a standard handler for this operation. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
*	bbu: include necessary headers	Lucas Stach	2015-03-04	1	-0/+2
\| \| \| \| \| \| \|	Fixes compile errors due to undefined symbols. Signed-off-by: Lucas Stach <dev@lynxeye.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
*	include/bbu: Add missing include errno.h	Markus Pargmann	2014-07-29	1	-0/+2
\| \| \| \| \|	Signed-off-by: Markus Pargmann <mpa@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
*	Add in-system barebox update infrastructure	Sascha Hauer	2012-10-17	1	-0/+49
	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>