LuminaSensum/barebox

Fork: 0

LuminaSensum / barebox

2019-03-18	426b4de Browse files » fs: squashfs: Remove unused function ... squashfs_lookup_next() isn't used in the tree. Remove it. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sascha Hauer committed on 18 Mar 2019
	d972277 Browse files » mfd: twl-core: Add missing prototype for twlcore_get() ... twlcore_get() has no prototype provided in header file. Add it. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sascha Hauer committed on 18 Mar 2019
	34b9e71 Browse files » bus: mvebu-mbus: Add missing whitespace ... orion5x_2win_mbus_data__maybe_unused should be two words. Fix it. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sascha Hauer committed on 18 Mar 2019
	38010c5 Browse files » ARM: PXA: Provide prototype for pxa_clear_reset_source() ... Move pxa_clear_reset_source() declaration to a header file where the file implementing it can see it. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sascha Hauer committed on 18 Mar 2019
	ff5ad81 Browse files » ARM: sha256: Remove unused header file ... sha256_glue.h is not being unsed in the tree. Remove it. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sascha Hauer committed on 18 Mar 2019
	b2d483c Browse files » ARM: sha256: Remove unused functions ... sha256_export and sha256_import are not used in the tree. remove them. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sascha Hauer committed on 18 Mar 2019
	e52a250 Browse files » ARM: boards: Harmonize barebox_arm_reset_vector() prototype ... barebox_arm_reset_vector() is a global function but we never provided a prototype anywhere. The prototypes differ for the different boards, so to provide a common prototype we must harmonize them. void barebox_arm_reset_vector(uint32_t r0, uint32_t r1, uint32_t r2) Should be suitable for all boards. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sascha Hauer committed on 18 Mar 2019
	d3945aa Browse files » ARM: i.MX: external-nand-boot: remove unused i.MX21 entry ... external nand boot on i.MX21 depends on broken for a long time no. As noone cared we remove it now. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sascha Hauer committed on 18 Mar 2019
	07b1c63 Browse files » treewide: Add missing includes ... Many files in the tree implement functions, but do not include the header files which provide the prototypes for these functions. This means conflicting prototypes remain undetected. Add the missing includes. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sascha Hauer committed on 18 Mar 2019
	27166fb Browse files » treewide: Make locally used functions static ... Many functions are only used locally but still are globally visible. Make these function static. Avoids warnings generated with -Wmissing-prototypes Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sascha Hauer committed on 18 Mar 2019
	a194fa7 Browse files » ARM: semihosting: Fix function prototype ... lsee takes a loff_t pos argument and not a off_t argument. Fix. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sascha Hauer committed on 18 Mar 2019
	5c1c2b2 Browse files » ARM: i.MX: extend kindle-mx50 defconfig ... The current defaultenv-kindle-mx50 requires MCI_STARTUP to boot the installed linux. CMD_LOADY is mentioned in the doc for barebox update purposes. FS_EXT4, FS_FAT and FS_FAT_WRITE gives users file system access. Also enable CMD_MEMTEST, CMD_CLK, CMD_REGULATOR and CMD_EDIT for interested users. The extended image will consume 195kB of available 253kB. Signed-off-by: Alexander Kurz <akurz@blala.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Alexander Kurz authored on 18 Mar 2019 Sascha Hauer committed on 18 Mar 2019
	6a8e62a Browse files » ARM Kindle3: switch on pull-ups for fiveway device ... Without the pullups enabled, the GPIO change after a button release took some hundered milliseconds. Signed-off-by: Alexander Kurz <akurz@blala.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Alexander Kurz authored on 17 Mar 2019 Sascha Hauer committed on 18 Mar 2019
	9696578 Browse files » ARM Kindle3 defconfig: enable MMU ... With the MMU enabled, a memtest runs 14 times faster. Signed-off-by: Alexander Kurz <akurz@blala.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Alexander Kurz authored on 17 Mar 2019 Sascha Hauer committed on 18 Mar 2019
	4d9d350 Browse files » ARM: Makefile: restore kindle3 imxcfg-y setting ... Commit 45f38c1a846f ("ARM: Makefile: Drop unnecessary imxcfg-y settings") dropped the imximg generation for the kindle3. This device is not covered within multiimage support and can be configured with kindle3_defconfig. Signed-off-by: Alexander Kurz <akurz@blala.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Alexander Kurz authored on 17 Mar 2019 Sascha Hauer committed on 18 Mar 2019
	f593354 Browse files » mci: imx-esdhc: resolve conflicting flags ... With commit 3354adee3920 ("mci: imx-esdhc: Add bigendian register access support") and commit 15b64fd520c2 ("mci: imx-esdhc: Add layerscape support") two ESDHC_FLAGs got assigned to already existing values. This conflict made the imx6sl usdhc appear to be big endian. Resolve this conflict by assign the new flags to the next vacant values. Signed-off-by: Alexander Kurz <akurz@blala.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Alexander Kurz authored on 15 Mar 2019 Sascha Hauer committed on 18 Mar 2019
	430cc8f Browse files » ARM: dts: mx8mq-phytec-phycore-som: Add watchdog ... Add watchdog support for imx8mq-phytec-phycore-som. Signed-off-by: Christian Hemp <c.hemp@phytec.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Christian Hemp authored on 15 Mar 2019 Sascha Hauer committed on 18 Mar 2019
	5f16ab6 Browse files » mci: imx-esdhc-pbl: initialize is_be ... Initialize is_be, otherwise the value of is_be is undefined. So it is possible that the i.MX8 will not boot because the bigendian functions are used. Signed-off-by: Christian Hemp <c.hemp@phytec.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Christian Hemp authored on 15 Mar 2019 Sascha Hauer committed on 18 Mar 2019
	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
	dc89bfe Browse files » pstore: ramoops: allow zapping invalid buffers in read-only mode ... The FS_PSTORE_RAMOOPS_RO configuration option keeps barebox from zapping (clearing and fixing header ecc) all ramoops buffers on initialization. It also stops barebox from zapping invalid buffers. This causes issues when the console writing code tries to use the uninitialized, invalid console buffer. Therefore, allow barebox to zap invalid buffers, the kernel will do so anyway if it finds broken buffers during its initialization. Signed-off-by: Philipp Zabel <p.zabel@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
	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
	da9b86e Browse files » pstore: Replace arguments for write() API ... Similar to the pstore_info read() callback, there were too many arguments. This switches to the new struct pstore_record pointer instead. This adds "reason" and "part" to the record structure as well. Signed-off-by: Kees Cook <keescook@chromium.org> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Kees Cook authored on 15 Mar 2019 Sascha Hauer committed on 18 Mar 2019
	cdce7a5 Browse files » pstore: Replace arguments for read() API ... The argument list for the pstore_read() interface is unwieldy. This changes passes the new struct pstore_record instead. The erst backend was already doing something similar internally. Signed-off-by: Kees Cook <keescook@chromium.org> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Kees Cook authored on 15 Mar 2019 Sascha Hauer committed on 18 Mar 2019
	ac960f1 Browse files » pstore: Switch pstore_mkfile to pass record ... Instead of the long list of arguments, just pass the new record struct. Signed-off-by: Kees Cook <keescook@chromium.org> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Kees Cook 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
	114d41b Browse files » pstore: Extract common arguments into structure ... The read/mkfile pair pass the same arguments and should be cleared between calls. Move to a structure and wipe it after every loop. Signed-off-by: Kees Cook <keescook@chromium.org> [p.zabel@pengutronix.de: ported to Barebox from Linux commit 9abdcccc3d5f] 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
	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
	f620bee Browse files » pstore: improve error report for failed setup ... When setting ramoops record sizes, sometimes it's not clear which parameters contributed to the allocation failure. This adds a per-zone name and expands the failure reports. Signed-off-by: Kees Cook <keescook@chromium.org> [p.zabel@pengutronix.de: ported to Barebox from Linux commit c443a5f3f1f1] 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
	9788514 Browse files » pstore/ram: Do not use stack VLA for parity workspace ... Instead of using a stack VLA for the parity workspace, preallocate a memory region. The preallocation is done to keep from needing to perform allocations during crash dump writing, etc. This also fixes a missed release of librs on free. Signed-off-by: Kees Cook <keescook@chromium.org> [p.zabel@pengutronix.de: ported to Barebox from Linux commit f2531f1976d9] 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
	478035d Browse files » pstore: Make ramoops_init_przs generic for other prz arrays ... Currently ramoops_init_przs() is hard wired only for panic dump zone array. In preparation for the ftrace zone array (one zone per-cpu) and pmsg zone array, make the function more generic to be able to handle this case. Heavily based on similar work from Joel Fernandes. Signed-off-by: Kees Cook <keescook@chromium.org> [p.zabel@pengutronix.de: ported to Barebox from Linux commit de83209249d6] 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