- Nov 14, 2018
-
-
Tom Rini authored
This brings in the u-boot-net PR from Joe.
-
Tom Rini authored
Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Commit fb01e07a accidentally broke initialisation of GPIO descriptor flags from device tree: currently the active low flag from gpio-specifier is always ignored. Fix it. Signed-off-by:
Anatolij Gustschin <agust@denx.de> Cc: Mario Six <mario.six@gdsys.cc>
-
Tom Rini authored
Now that CMD_UBI does not select CMD_MTDPARTS we need to make platforms that had been enabling it turn it on by hand. This exposed that we had not yet migrated CMD_MTDPARTS fully, so do so now. Fixes: 86dfa556 ("cmd: ubi: Remove useless call to mtdparts_init()") Signed-off-by:
Tom Rini <trini@konsulko.com>
-
git://git.denx.de/u-boot-spiTom Rini authored
-
Tom Rini authored
Rsync all defconfig files using moveconfig.py Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Nov 13, 2018
-
-
Commit 9c5b0097 ("Convert CONFIG_MTD_PARTITIONS et al to Kconfig") introduced a publicly visible Kconfig entry for the CONFIG_MTD_PARTITIONS option, while the rework on MTD partitioning was in progress, and we somehow did not notice that the same Kconfig entry was added by commit 4048a5c5 ("mtd: declare MTD_PARTITIONS symbol in Kconfig"), but this time as an invisible entry (this can only be selected by other options). Keep the non-visible version of this symbol, since MTD_PARTITIONS is not something the user should be able to enable/disable directly. Fixes: 4048a5c5 ("mtd: declare MTD_PARTITIONS symbol in Kconfig") Signed-off-by:
Boris Brezillon <boris.brezillon@bootlin.com> Reviewed-by:
Lukasz Majewski <lukma@denx.de> Reviewed-by:
Jagan Teki <jagan@openedev.com>
-
Commit c58fb2cd ("cmd: ubi: clean the partition handling") introduced a call to mtd_probe_devices() in the ubi_attach() path and this function takes care of parsing mtdparts/mtdids and creating/registering the associated mtd partitions. The mtdparts_init() call in the ubi_detach() path is not only unnecessary but can sometimes print error messages even when things work properly (that's the case with SPI NAND devices that have not been probed with 'mtd list'), which is misleading. Remove this call to mtdparts_init() and drop the dependency on CMD_MTDPARTS. Fixes: c58fb2cd ("cmd: ubi: clean the partition handling") Reported-by:
Stefan Roese <sr@denx.de> Signed-off-by:
Boris Brezillon <boris.brezillon@bootlin.com> Tested-by:
Stefan Roese <sr@denx.de> Reviewed-by:
Lukasz Majewski <lukma@denx.de> Reviewed-by:
Jagan Teki <jagan@openedev.com>
-
gwventana configs are relying on CMD_UBI to select CMD_MTDPARTS, which is then making {MTDIDS,MTDPARTS}_DEFAULT options available. We are about to remove the 'select CMD_MTDPARTS' statement in the CMD_UBI entry, but if we do that without first making sure {MTDIDS,MTDPARTS}_DEFAULT are visible, we end up with a build failure when building gwventana configs. Address that by adding a depends on MTD_PARTITIONS to {MTDIDS,MTDPARTS}_DEFAULT which does the trick since CMD_UBI selects MTD_UBI which in turn selects MTD_PARTITIONS. We also get rid of the depends on CMD_MTD, since CMD_MTD also selects MTD_PARTITIONS. Reported-by:
Jagan Teki <jagan@amarulasolutions.com> Signed-off-by:
Boris Brezillon <boris.brezillon@bootlin.com> Reviewed-by:
Lukasz Majewski <lukma@denx.de> Reviewed-by:
Jagan Teki <jagan@openedev.com>
-
dfu_fill_entity_nand() uses find_dev_and_part() and mtdparts_init() which are provided by cmd/mtdparts.c. Add the dependency to avoid build failures when CMD_MTDPARTS is not selected. Reported-by:
Jagan Teki <jagan@amarulasolutions.com> Fixes: 6828e602 ("dfu: Migrate to Kconfig") Signed-off-by:
Boris Brezillon <boris.brezillon@bootlin.com> Reviewed-by:
Lukasz Majewski <lukma@denx.de> Reviewed-by:
Jagan Teki <jagan@openedev.com>
-
U-boot provides a mean to define default values for mtdids and mtdparts when they're not defined in the environment. Patch mtd_probe_devices() to use those default values when env_get("mtdparts") or env_get("mtdids") return NULL. This implementation is based on the logic found in cmd/mtdparts.c. Fixes: 5db66b3a ("cmd: mtd: add 'mtd' command") Reported-by:
Stefan Roese <sr@denx.de> Signed-off-by:
Boris Brezillon <boris.brezillon@bootlin.com> Tested-by:
Stefan Roese <sr@denx.de> Reviewed-by:
Lukasz Majewski <lukma@denx.de> Reviewed-by:
Jagan Teki <jagan@openedev.com>
-
- Nov 12, 2018
-
-
-
The make macro to check if the binary exceeds the board size limit is taken straight from the root Makefile. Without this and e.g. enabled EFI Vybrid fails booting as the regular size limit check does not take the final u-boot.imx binary size into account which is bigger due to alignment as well as IMX header stuff. Signed-off-by:
Marcel Ziswiler <marcel.ziswiler@toradex.com> Reviewed-by:
Fabio Estevam <festevam@gmail.com>
-
Drop SPI support saving precious 4 Kb on boards with tough size restrictions. Signed-off-by:
Marcel Ziswiler <marcel.ziswiler@toradex.com> Signed-off-by:
Marcel Ziswiler <marcel@ziswiler.com>
-
Unset CONFIG_CMDLINE_EDITING saving precious 4 Kb on boards with tough size restrictions. Signed-off-by:
Marcel Ziswiler <marcel.ziswiler@toradex.com>
-
Unset CONFIG_EFI_UNICODE_CAPITALIZATION on boards with tough size restrictions. This is analogous to commit a90bf07a ("efi_loader: unset CONFIG_EFI_UNICODE_CAPITALIZATION"). Signed-off-by:
Marcel Ziswiler <marcel.ziswiler@toradex.com> Reviewed-by:
Alexander Graf <agraf@suse.de>
-
- Nov 10, 2018
-
-
This patch adds check for command response CRC failure. The driver is currently ignoring CRC check failure on command resposes which have CRC atteched to it, which can be potentially dangerous. Even more grueling problem happens when the command response is followed by data transfer though, as in that case, the dwmci_data_transfer() function will spin until it reaches the 240s timeout. Signed-off-by:
Marek Vasut <marex@denx.de> Cc: Heiko Stuebner <heiko@sntech.de> Cc: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
- Nov 09, 2018
-
-
Build ymodem only on need to shrink spl image size. Signed-off-by:
Jun Nie <jun.nie@linaro.org>
-
common/common_fit.c is including <spl.h>, but not actually using it. The inclusion will cuase compile error on platforms using CONFIG_OF_SEPARATE and not SPL. Signed-off-by:
Lars Povlsen <lars.povlsen@microsemi.com> Reviewed-by:
Jean-Jacques Hiblot <jjhiblot@ti.com>
-
The commit 484fdf5b ("dm: Add support for all targets which requires MANUAL_RELOC") introduces subtle typo, i.e. missed semicolon. Fixes: 484fdf5b ("dm: Add support for all targets which requires MANUAL_RELOC") Cc: Michal Simek <michal.simek@xilinx.com> Signed-off-by:
Andy Shevchenko <andriy.shevchenko@linux.intel.com> Reviewed-by:
Michal Simek <michal.simek@xilinx.com>
-
Tiny printf does not support %.*s and %lX. Since tiny printf should be very common in SPL, replace these by %32s (for printing image name) and %lx. Signed-off-by:
Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Add mailing list for stm32mp architecture and board. Signed-off-by:
Patrick Delaunay <patrick.delaunay@st.com>
-
Testing has shown that a line-break is missing in one debug line in fit_find_config_node(). Signed-off-by:
Stefan Roese <sr@denx.de>
-
- Nov 08, 2018
-
-
If the function gpr_init is used in a common MX6 spl implementation we have to ensure that it is only called for suitable cpu types, otherwise it breaks hardware parts like enet1, can1, can2, etc. Signed-off-by:
Christoph Niedermaier <cniedermaier@dh-electronics.de>
-
git://git.denx.de/u-boot-ubiTom Rini authored
-
- Nov 07, 2018
-
-
Due to revert of commit c0434407, this board does not build any more. Disable CONFIG_DISPLAY_CPUINFO for v2018.11 release. This commit should be reverted after v2018.11 release. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Acked-by:
Peng Fan <peng.fan@nxp.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
This reverts commit c0434407. It turns out commit c0434407 broke some boards which have DM CPU driver with CONFIG_DISPLAY_CPUINFO option on. These boards just fail to boot when print_cpuinfo() is called during boot. Fixes are already sent to ML and in u-boot-dm/next, however since we are getting close to the v2018.11 release, it's safer we revert the original commit. This commit should be reverted after v2018.11 release. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Acked-by:
Peng Fan <peng.fan@nxp.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
git://git.denx.de/u-boot-microblazeTom Rini authored
Xilinx fixes for v2018.11-rc3 - Fix fit loading address for Zynq
-
Michal Simek authored
Default setup is 0 which is incorrect place because it points to OCM which is allocated for SPL only in our case. Use address in DDR. Signed-off-by:
Michal Simek <michal.simek@xilinx.com>
-
Add local size_t variable to crypto_comp_decompress as intermediate storage for destination length to avoid memory corruption and incorrect results on 64 bit targets. This is what linux does for the various lz compression implementations. Signed-off-by:
Paul Davey <paul.davey@alliedtelesis.co.nz> Cc: Heiko Schocher <hs@denx.de> Tested-by:
Heiko Schocher <hs@denx.de>
-
- Nov 06, 2018
-
-
-
git://git.denx.de/u-boot-marvellTom Rini authored
-
git://git.denx.de/u-boot-x86Tom Rini authored
-
Stefan Roese authored
The new board version has the 2nd FPGA connected via CS# 0 instead of 2 on SPI bus 1. Change this setup in the DT accordingly. Please note that this change does still work on the old board version because the CS signal is not used on this board. Signed-off-by:
Stefan Roese <sr@denx.de>
-
Stefan Roese authored
Add the "spi-flash" compatible string so that the generic sf_probe driver can probe the SPI flash on the theadorable Armada-XP board. Signed-off-by:
Stefan Roese <sr@denx.de>
-
Stefan Roese authored
With patch 49b23e03 (pci: mvebu: Increase size of PCIe default mapping) the mapping size for each PCI(e) controller was increased from 32MiB to 128MiB. This leads to problems on boards with multiple PCIe slots / ports which are unable to map all PCIe ports, e.g. the Armada-XP theadorable: DRAM: 2 GiB (667 MHz, 64-bit, ECC not enabled) SF: Detected m25p128 with page size 256 Bytes, erase size 256 KiB, total 16 MiB Cannot add window '4:f8', conflicts with another window PCIe unable to add mbus window for mem at f0000000+08000000 Model: Marvell Armada XP theadorable This patch moves the base address for the PCI(e) memory spaces from 0xe8000000 to the end of SDRAM (clipped to a max of 0xc0000000 right now). This gives move room and flexibility for PCI(e) mappings. Signed-off-by:
Stefan Roese <sr@denx.de> Cc: VlaoMao <vlaomao@gmail.com> Tested-by: VlaoMao <vlaomao at gmail.com>
-
Add NXP linux team upstream maillist as reviewer Signed-off-by:
Peng Fan <peng.fan@nxp.com>
-
Commit 3c28576b ("arm: dts: imx8qxp: fix build warining") fixed the dts warning by removing the unnecessary #address-cells/#size-cells, but the recommendation for regulators is not to place them under "simple-bus", so move the reg_usdhc2_vmmc regulator accordingly. Signed-off-by:
Fabio Estevam <festevam@gmail.com>
-
board/freescale/mx8mq_evk/README has been introduced by mistake in commit d0dd7397 ("imx: add i.MX8QXP MEK board support") Remove it for now as this should be introduced when mx8mq_evk support is in place. Reported-by:
Tim Harvey <tharvey@gateworks.com> Signed-off-by:
Fabio Estevam <festevam@gmail.com> Reviewed-by:
Peng Fan <peng.fan@nxp.com>
-
If there is no CONTAINER entry, there is no need to flatten container header. Signed-off-by:
Peng Fan <peng.fan@nxp.com>
-