LuminaSensum/barebox

Fork: 0

LuminaSensum / barebox

History for barebox / Documentation

2019-05-23	07c8602 Browse files » Documentation: imx8mq-evk: collapse BMOD switch superposition ... Table 3. Boot mode setting in the user's guide[1] lists 0010 as 'Boot from EMMC'. Adjust diagram accordingly. [1]: https://www.mouser.com/ds/2/302/IMX8MDQLQEVKHUG-1280333.pdf Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Ahmad Fatoum authored on 22 May 2019 Sascha Hauer committed on 23 May 2019
2019-05-21	3da7b10 Browse files » ARM: boards: kindle mx50: adapt MCI name to DTS ... The MCI instances got aliases in the DTS from linux upstream which changed the eMMC devicename e.g. from disk0 to mmc2. Adapt to this. Signed-off-by: Alexander Kurz <akurz@blala.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Alexander Kurz authored on 20 May 2019 Sascha Hauer committed on 21 May 2019
2019-05-10	bac0183 Browse files » Merge branch 'for-next/misc' Sascha Hauer committed on 10 May 2019
2019-05-06	4647cb6 Browse files » Documentation: imx: add documentation for RioTboard ... Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Oleksij Rempel authored on 30 Apr 2019 Sascha Hauer committed on 6 May 2019
2019-04-26	17ab169 Browse files » doc: clarify state framework driver requirement Moritz Augsburger authored on 23 Apr 2019 Sascha Hauer committed on 26 Apr 2019
2019-04-23	6fcf89d Browse files » doc: variables: nv vars are saved automatically. ... In recent barebox versions, nv variables are saved automatically upon reset or kernel start (console message "nv variable modified, will save nv variables on shutdown" warns about that). There is no need to explicitly call saveenv. This change was introduced in 3fadbdae. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Tomaz Solc authored on 16 Apr 2019 Sascha Hauer committed on 23 Apr 2019
2019-03-18	3342ba8 Browse files » pstore/doc: fix layout ... Emphasise keywords and paths. Signed-off-by: Juergen Borleis <jbe@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Juergen Borleis authored on 15 Mar 2019 Sascha Hauer committed on 18 Mar 2019
	af85a0f Browse files » pstore: pass ramoops configuration to kernel via device tree ... Instead of setting ramoops module parameters on the kernel command line, add a /reserved-memory/ramoops node to the device tree via of_fixup. Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de> Documentation-added-by: Juergen Borleis <jbe@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Philipp Zabel authored on 15 Mar 2019 Sascha Hauer committed on 18 Mar 2019
	6906ffb Browse files » pstore: add console support ... Add support for writing console messages to pstore. Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de> Documentation-added-by: Juergen Borleis <jbe@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Philipp Zabel authored on 15 Mar 2019 Sascha Hauer committed on 18 Mar 2019
	34e46e5 Browse files » pstore/ram: Clarify resource reservation labels ... When ramoops reserved a memory region in the kernel, it had an unhelpful label of "persistent ram". When reading iomem, it would be repeated many times, did not hint that it was ramoops in particular, and didn't clarify very much about what each was used for: 0x4fdd4000 - 0x4fdf3fff (size 0x00020000) persistent ram 0x4fdf4000 - 0x4fe13fff (size 0x00020000) persistent ram ... 0x4ff74000 - 0x4ff93fff (size 0x00020000) persistent ram 0x4ff94000 - 0x4ffb3fff (size 0x00020000) persistent ram 0x4ffb4000 - 0x4ffd3fff (size 0x00020000) persistent ram Instead, this adds meaningful labels for how the various regions are being used: 0x4fdd4000 - 0x4fdf3fff (size 0x00020000) ramoops:dump(0/12) 0x4fdf4000 - 0x4fe13fff (size 0x00020000) ramoops:dump(1/12) ... 0x4ff74000 - 0x4ff93fff (size 0x00020000) ramoops:console 0x4ff94000 - 0x4ffb3fff (size 0x00020000) ramoops:ftrace 0x4ffb4000 - 0x4ffd3fff (size 0x00020000) ramoops:pmsg Signed-off-by: Kees Cook <keescook@chromium.org> Reviewed-by: Joel Fernandes (Google) <joel@joelfernandes.org> [p.zabel@pengutronix.de: ported to Barebox from Linux commit 1227daa43bce] Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Kees Cook authored on 15 Mar 2019 Sascha Hauer committed on 18 Mar 2019
2019-03-07	8f397a4 Browse files » Merge branch 'for-next/rpi' Sascha Hauer committed on 7 Mar 2019
2019-03-07	5c126a1 Browse files » Merge branch 'for-next/efi' Sascha Hauer committed on 7 Mar 2019
2019-03-04	67e38cd Browse files » ARM: rpi: save bootargs from VC FDT to vc.bootargs ... When booting a Raspberry Pi, it is useful to extract bootargs from the device tree that was created by the VideoCore firmware. These bootargs contain for example settings for the framebuffer that the kernel needs to properly set the video output. This commit extracts the bootargs in the board initialization code and saves them to the vc.bootargs global variable. For example, a bootloader environment can then add the contents of this variable to linux.bootargs.vc, which then gets included into the final bootargs for the kernel using CONFIG_FLEXIBLE_BOOTARGS. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Tomaz Solc authored on 27 Feb 2019 Sascha Hauer committed on 4 Mar 2019
2019-03-04	e390c87 Browse files » ARM: rpi: save fdt that was passed from VideoCore ... On Raspberry Pi, VideoCore firmware creates a device tree that contains information about peripherals that were initialized by VideoCore based on settings in config.txt. Normally this device tree is passed to the Linux kernel via a pointer in the r2 register. A bootloader needs to pass this device tree to the kernel, or some peripherals will not work correctly. Since the VideoCore device tree is not compatible with barebox, we can't just pass it to barebox_arm_entry() as the internal barebox device tree. This commit makes the prebootloader code copy the device tree from VideoCore into a scrap RAM area just above the area reserved for the bootloader. Board initialization code in the bootloader proper then copies it into a file /vc.dtb. The bootloader environment is then free to pass this file to the kernel at boot (e.g. via bootm -o). Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Tomaz Solc authored on 27 Feb 2019 Sascha Hauer committed on 4 Mar 2019
2019-02-27	9d9b87e Browse files » Documentation: imx8mq-evk: fix firmware path ... Since commit: "da985aac8 firmware: drop the imx subdir" the firmware is not longer placed in imx subdir. So the subdir can be removed from the documentation. Signed-off-by: Christian Hemp <christian.hemp@posteo.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Christian Hemp authored on 26 Feb 2019 Sascha Hauer committed on 27 Feb 2019
2019-02-18	3c2dee2 Browse files » doc: bootchooser: add retry handling to algorithm description ... Signed-off-by: Enrico Jorns <ejo@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Enrico Jorns authored on 15 Feb 2019 Sascha Hauer committed on 18 Feb 2019
	fd51d78 Browse files » doc: bootchooser: add details about bootchooser.reset_attempts handling ... For understanding and correctly using the algorith it is useful to know when the values are evaluated. Signed-off-by: Enrico Jorns <ejo@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Enrico Jorns authored on 15 Feb 2019 Sascha Hauer committed on 18 Feb 2019
	2b21c97 Browse files » doc: bootchooser: be more explicit about when the bootchooser terminates ... Signed-off-by: Enrico Jorns <ejo@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Enrico Jorns authored on 15 Feb 2019 Sascha Hauer committed on 18 Feb 2019
	463610e Browse files » doc: bootchooser: note how to actually start the bootchooser ... Signed-off-by: Enrico Jorns <ejo@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Enrico Jorns authored on 15 Feb 2019 Sascha Hauer committed on 18 Feb 2019
	bb655eb Browse files » doc: bootchooser: be more explicit about attempts reset on successful boot ... From the current description of how the bootchooser algorithm works it is not that easy to figure out how to actually use it in a full (redundancy) boot chain. Signed-off-by: Enrico Jorns <ejo@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Enrico Jorns authored on 15 Feb 2019 Sascha Hauer committed on 18 Feb 2019
	c0da3bd Browse files » doc: bootchooser: be more explicit what bootchooser.state_prefix is for ... Signed-off-by: Enrico Jorns <ejo@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Enrico Jorns authored on 15 Feb 2019 Sascha Hauer committed on 18 Feb 2019
	5d5d0a6 Browse files » doc: bootchooser: explicitly note configuration vs. storage backend ... It is quite confusing for some users sometimes where to set what. Signed-off-by: Enrico Jorns <ejo@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Enrico Jorns authored on 15 Feb 2019 Sascha Hauer committed on 18 Feb 2019
	4209e81 Browse files » doc: bootchooser: fix typos etc. ... Signed-off-by: Enrico Jorns <ejo@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Enrico Jorns authored on 15 Feb 2019 Sascha Hauer committed on 18 Feb 2019
	ec1ab41 Browse files » Documentation: efi: provide (U)EFI watchdog documentation ... Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Oleksij Rempel authored on 15 Feb 2019 Sascha Hauer committed on 18 Feb 2019
2019-02-13	d1bebc0 Browse files » Merge branch 'for-next/rpi' Sascha Hauer committed on 13 Feb 2019
2019-02-13	2a17e75 Browse files » Merge branch 'for-next/misc' Sascha Hauer committed on 13 Feb 2019
2019-02-11	ecff6c2 Browse files » ARM: i.MX: Add support for ZII i.MX8MQ based devices ... Add support for the following ZII i.MX8MQ based boards: - ZII i.MX8MQ RMB3 - ZII i.MX8MQ Zest Most of the basic peripherals are supported by this patch. More advanced features such as PCIe, display support, etc, are planned to be added later. Signed-off-by: Andrey Smirnov <andrew.smirnov@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Andrey Smirnov authored on 30 Jan 2019 Sascha Hauer committed on 11 Feb 2019
2019-02-11	d3a979d Browse files » Documentation: i.MX: Increase :maxdepth: for board documentation ... A number of board documentation file have subsections. Increase :maxdepth:, so we'd get proper TOC and numbering. Signed-off-by: Andrey Smirnov <andrew.smirnov@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Andrey Smirnov authored on 30 Jan 2019 Sascha Hauer committed on 11 Feb 2019
2019-02-07	6e3b4ec Browse files » state: Documentation: fix typo ... Signed-off-by: Ulrich Ölmann <u.oelmann@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Ulrich Ölmann authored on 6 Feb 2019 Sascha Hauer committed on 7 Feb 2019
2019-02-05	f133053 Browse files » doc: bcm283x: remove miniuart overlay instruction ... Since we now use the miniuart on the raspberry pi 3, the miniuart overlay is no longer needed. Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Rouven Czerwinski authored on 15 Jan 2019 Sascha Hauer committed on 5 Feb 2019