- 23 7月, 2017 6 次提交
-
-
由 Emmanuel Vadot 提交于
FreeBSD recently switch to it's BSDL dtc. While it support most of the features of the GPL one it still lacks the incbin directive. Add the possibility to specify which dtc we want to use for compiling dts and generating fit image. Signed-off-by: NEmmanuel Vadot <manu@bidouilliste.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 xypron.glpk@gmx.de 提交于
The Odroid C2 has two GiB of memory with two reserved regions. reg = <0x0 0x0 0x0 0x1000000>; reg = <0x0 0x10000000 0x0 0x200000>; Patch bfcef28a (arm: add initial support for Amlogic Meson and ODROID-C2) provided function dram_init_banksize to reserve the first 16 MiB of RAM for firmware in function dram_init_banksize in arch/arm/mach-meson/board.c and defined CONFIG_NR_DRAM_BANKS = 1. With this patch dram_init_banksize is changed to additionally reserve the 2MiB region for the ARM Trusted Firmware (BL31). CONFIG_NR_DRAM_BANKS is set to 2. Cc: Andreas Färber <afaerber@suse.de> Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Fiach Antaw 提交于
The env_nand, env_mmc and env_ubi implementations all implement redundancy using an identical serial-number scheme. This commit migrates them to use the implementation in env_common, which is functionally identical. Signed-off-by: NFiach Antaw <fiach.antaw@uqconnect.edu.au> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Fiach Antaw 提交于
All current environments that implement redundancy use almost identical implementations. This patch implements the env_nand implementation as a function in env_common, and updates the env_export function to export an env_nand-style 'flags' field by default. Signed-off-by: NFiach Antaw <fiach.antaw@uqconnect.edu.au> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Tom Rini 提交于
If one does not already have a rule to create a custom device node when a given device enumerates it can be useful to have udev create a bus path based node to the entry in /dev/bus/usb that was just enumerated. Given that DFU itself does not require a /dev entry it is a good idea to provide a rule that will generate one. Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Michael Heimpold 提交于
Closing a file descriptor does not guarantee that the data has been successfully saved to disk, as the kernel might defer the write. Signed-off-by: NMichael Heimpold <mhei@heimpold.de>
-
- 19 7月, 2017 17 次提交
-
-
由 Masahiro Yamada 提交于
DTB is encoded in big endian. When we retrieve property values, we need to use fdt32_to_cpu (aka be32_to_cpu) for endian conversion. This is a bit error-prone, but sparse is useful to detect endian mismatch. We need to use (fdt32_t *) instead of (u32 *) for a pointer of a property value. Otherwise sparse warns "cast to restricted __be32". Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Masahiro Yamada 提交于
This function is only used in common/spl/spl_mmc.c[ Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com> Reviewed-by: NBin Meng <bmeng.cn@gmail.com> Signed-off-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Keerthy 提交于
get_enable should be able to return error values. Hence change the return type to integer. Signed-off-by: NKeerthy <j-keerthy@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Keerthy 提交于
get_enable should be able to return error values. Hence change the return type to integer. Signed-off-by: NKeerthy <j-keerthy@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Keerthy 提交于
get_enable should be able to return error values. Hence change the return type to integer. Signed-off-by: NKeerthy <j-keerthy@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Keerthy 提交于
get_enable should be able to return error values. Hence change the return type to integer. Signed-off-by: NKeerthy <j-keerthy@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Keerthy 提交于
get_enable should be able to return error values. Hence change the return type to integer. Signed-off-by: NKeerthy <j-keerthy@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Keerthy 提交于
get_enable should be able to return error values. Hence change the return type to integer. Signed-off-by: NKeerthy <j-keerthy@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Keerthy 提交于
get_enable should be able to return error values. Hence change the return type to integer. Signed-off-by: NKeerthy <j-keerthy@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Keerthy 提交于
get_enable should be able to return error values. Hence change the return type to integer. Signed-off-by: NKeerthy <j-keerthy@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Keerthy 提交于
get_enable should be able to return error values. Hence change the return type to integer. Signed-off-by: NKeerthy <j-keerthy@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Keerthy 提交于
get_enable should be able to return error values. Hence change the return type to integer. Signed-off-by: NKeerthy <j-keerthy@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Keerthy 提交于
get_enable should be able to return error values. Hence change the return type to integer. Signed-off-by: NKeerthy <j-keerthy@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Keerthy 提交于
Change get_enable return type to int so errors can be returned. Signed-off-by: NKeerthy <j-keerthy@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Kever Yang 提交于
According to MMC spec, the write_counter is 4-byte length, use 'int' instead of 'long' type for the 'long' is not 4-byte in 64 bit CPU. Signed-off-by: NJason Zhu <jason.zhu@rock-chips.com> Signed-off-by: NKever Yang <kever.yang@rock-chips.com> Reviewed-by: NSimon Glass <sjg@chromium.org> Signed-off-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Kever Yang 提交于
When CONFIG_BLK is enabled, the hwpart id is different with legacy interface, update it to kame driver work with CONFIG_BLK. Signed-off-by: NKever Yang <kever.yang@rock-chips.com> Reviewed-by: NSimon Glass <sjg@chromium.org> Signed-off-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Marek Vasut 提交于
I no longer have any of these boards, mark boards orphan. Signed-off-by: NMarek Vasut <marex@denx.de> Cc: Tom Rini <trini@konsulko.com>
-
- 18 7月, 2017 1 次提交
-
-
- 14 7月, 2017 1 次提交
-
-
由 Fabio Estevam 提交于
Move CONFIG_CMD_SATA option to Kconfig to fix the following build error: In file included from include/configs/mx6cuboxi.h:137:0, from include/config.h:7, from include/common.h:21, from common/env_common.c:11: include/config_distro_bootcmd.h:161:2: error: expected '}' before 'BOOT_TARGET_DEVICES_references_SATA_without_CONFIG_SATA' BOOT_TARGET_DEVICES_references_SATA_without_CONFIG_SATA Reported-by: NStefano Babic <sbabic@denx.de> Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com>
-
- 13 7月, 2017 1 次提交
-
-
由 Fabio Estevam 提交于
Since commit ce412b79 ("drivers: net: phy: atheros: add separate config for AR8031") Ethernet does not work on mx6sabreauto. This commit correctly assigns ar8031_config() as the configuration function for AR8031 in the same way as done in the Linux kernel. However, on mx6sabreauto design we need some additional configurations, such as enabling the 125 MHz AR8031 output and setting the TX clock delay that need to be done in the board file. This is the equivalent fix from commit 4b6035da ("mx6sabresd: Make Ethernet functional again"). Reported-by: NMiquel RAYNAL <miquel.raynal@free-electrons.com> Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com>
-
- 12 7月, 2017 14 次提交
-
-
-
由 Patrick Bruenn 提交于
If no vmlinuz is found on mmc, try to boot from pxe. Signed-off-by: NPatrick Bruenn <p.bruenn@beckhoff.com>
-
由 Patrick Bruenn 提交于
Replace fdtaddr and rdaddr variable names with u-boot standard names fdt_addr_r and ramdisk_addr_r. This will make the use of pxe boot more easy. Signed-off-by: NPatrick Bruenn <p.bruenn@beckhoff.com>
-
由 Diego Dorta 提交于
Add support for Falcon mode and explain in the README the steps to boot the kernel directly without loading the full U-Boot. Signed-off-by: NDiego Dorta <diego.dorta@nxp.com> Acked-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Fabio Estevam 提交于
warp can run different kernel versions, such as NXP 4.1 or mainline. Currently the rootfs location is passed via mmcblk number and the problem with this approach is that the mmcblk number for the eMMC changes depending on the kernel version. In order to avoid such issue, use UUID method to specify the rootfs location. Succesfully tested booting a NXP 4.1 and also a mainline 4.12 kernel. Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com> Acked-by: NOtavio Salvador <otavio@ossystems.com.br>
-
由 Fabio Berton 提交于
Currently the rootfs location is passed via mmcblk number and the problem with this approach is that the mmcblk number for the eMMC changes depending on the kernel version. In order to avoid such issue, use UUID method to specify the rootfs location. Also add CONFIG_BOOTCOMMAND to run finduuid function and distro_bootcmd. This change was made based on U-Boot commit: - ca4f338eSigned-off-by: NFabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br> Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Fabio Berton 提交于
Currently the rootfs location is passed via mmcblk number and the problem with this approach is that the mmcblk number for the eMMC changes depending on the kernel version. In order to avoid such issue, use UUID method to specify the rootfs location. This change was made based on U-Boot commit: - ca4f338eSigned-off-by: NFabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br> Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Fabio Berton 提交于
Currently the rootfs location is passed via mmcblk number and the problem with this approach is that the mmcblk number for the eMMC changes depending on the kernel version. In order to avoid such issue, use UUID method to specify the rootfs location. This change was made based on U-Boot commit: - ca4f338eSigned-off-by: NFabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br> Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Fabio Estevam 提交于
mx6sabre boards can run different kernel versions, such as NXP 4.1 or mainline. Currently the rootfs location is passed via mmcblk number and the problem with this approach is that the mmcblk number for the eMMC changes depending on the kernel version. In order to avoid such issue, use UUID method to specify the rootfs location. Succesfully tested booting a NXP 4.1 and also a mainline kernel on a mx6qsabresd and mx6dlsabreauto. Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Fabio Estevam 提交于
WEIM cannot be used when I2C3 is enabled due to pin conflict, so keep WEIM disabled by default. I2C3 controls GPIO I2C expander (USB host and OTG have VBUS controlled by the GPIO I2C expander), magnetometer, accelerometer. Not disabling WEIM in U-Boot causes I2C3 to behave badly when booting a NXP 4.1 kernel, which leads to probe failure on several devices, including the lack of USB: imx_usb 2184000.usb: Can't register ci_hdrc platform device, err=-517 By keeping WEIM disabled in U-Boot these kernel issues are gone. Reported-by: NTakashi Matsuzawa <tmatsuzawa@xevo.com> Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Stefano Babic 提交于
Change is consistent with other SOCs and it is in preparation for adding SOMs. SOC's related files are moved from cpu/ to mach-imx/<SOC>. This change is also coherent with the structure in kernel. Signed-off-by: NStefano Babic <sbabic@denx.de> CC: Fabio Estevam <fabio.estevam@nxp.com> CC: Akshay Bhat <akshaybhat@timesys.com> CC: Ken Lin <Ken.Lin@advantech.com.tw> CC: Marek Vasut <marek.vasut@gmail.com> CC: Heiko Schocher <hs@denx.de> CC: "Sébastien Szymanski" <sebastien.szymanski@armadeus.com> CC: Christian Gmeiner <christian.gmeiner@gmail.com> CC: Stefan Roese <sr@denx.de> CC: Patrick Bruenn <p.bruenn@beckhoff.com> CC: Troy Kisky <troy.kisky@boundarydevices.com> CC: Nikita Kiryanov <nikita@compulab.co.il> CC: Otavio Salvador <otavio@ossystems.com.br> CC: "Eric Bénard" <eric@eukrea.com> CC: Jagan Teki <jagan@amarulasolutions.com> CC: Ye Li <ye.li@nxp.com> CC: Peng Fan <peng.fan@nxp.com> CC: Adrian Alonso <adrian.alonso@nxp.com> CC: Alison Wang <b18965@freescale.com> CC: Tim Harvey <tharvey@gateworks.com> CC: Martin Donnelly <martin.donnelly@ge.com> CC: Marcin Niestroj <m.niestroj@grinn-global.com> CC: Lukasz Majewski <lukma@denx.de> CC: Adam Ford <aford173@gmail.com> CC: "Albert ARIBAUD (3ADEV)" <albert.aribaud@3adev.fr> CC: Boris Brezillon <boris.brezillon@free-electrons.com> CC: Soeren Moch <smoch@web.de> CC: Richard Hu <richard.hu@technexion.com> CC: Wig Cheng <wig.cheng@technexion.com> CC: Vanessa Maegima <vanessa.maegima@nxp.com> CC: Max Krummenacher <max.krummenacher@toradex.com> CC: Stefan Agner <stefan.agner@toradex.com> CC: Markus Niebel <Markus.Niebel@tq-group.com> CC: Breno Lima <breno.lima@nxp.com> CC: Francesco Montefoschi <francesco.montefoschi@udoo.org> CC: Jaehoon Chung <jh80.chung@samsung.com> CC: Scott Wood <oss@buserror.net> CC: Joe Hershberger <joe.hershberger@ni.com> CC: Anatolij Gustschin <agust@denx.de> CC: Simon Glass <sjg@chromium.org> CC: "Andrew F. Davis" <afd@ti.com> CC: "Łukasz Majewski" <l.majewski@samsung.com> CC: Patrice Chotard <patrice.chotard@st.com> CC: Nobuhiro Iwamatsu <iwamatsu@nigauri.org> CC: Hans de Goede <hdegoede@redhat.com> CC: Masahiro Yamada <yamada.masahiro@socionext.com> CC: Stephen Warren <swarren@nvidia.com> CC: Andre Przywara <andre.przywara@arm.com> CC: "Álvaro Fernández Rojas" <noltari@gmail.com> CC: York Sun <york.sun@nxp.com> CC: Xiaoliang Yang <xiaoliang.yang@nxp.com> CC: Chen-Yu Tsai <wens@csie.org> CC: George McCollister <george.mccollister@gmail.com> CC: Sven Ebenfeld <sven.ebenfeld@gmail.com> CC: Filip Brozovic <fbrozovic@gmail.com> CC: Petr Kulhavy <brain@jikos.cz> CC: Eric Nelson <eric@nelint.com> CC: Bai Ping <ping.bai@nxp.com> CC: Anson Huang <Anson.Huang@nxp.com> CC: Sanchayan Maity <maitysanchayan@gmail.com> CC: Lokesh Vutla <lokeshvutla@ti.com> CC: Patrick Delaunay <patrick.delaunay@st.com> CC: Gary Bisson <gary.bisson@boundarydevices.com> CC: Alexander Graf <agraf@suse.de> CC: u-boot@lists.denx.de Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com> Reviewed-by: NChristian Gmeiner <christian.gmeiner@gmail.com>
-
由 Peng Fan 提交于
CONFIG_SYS_FSL_ESDHC_FORCE_VSELECT is not the correct method to set I/O to 1.8. To boards that does not support vqmmc-supply, use vs18_enable in fsl_esdhc_cfg. If regulator is supported, use fixed 1.8V regulator for vqmmc-supply. Signed-off-by: NPeng Fan <peng.fan@nxp.com> Cc: Jaehoon Chung <jh80.chung@samsung.com> Cc: York Sun <york.sun@nxp.com> Cc: Stefano Babic <sbabic@denx.de>
-
由 Peng Fan 提交于
Handle vqmmc supply. Some boards have a fixed I/O voltage at 1.8V for emmc, so the usdhc also needs to be configured as 1.8V by setting VSELECT bit. The vs18_enable is the one that used to checking whether setting VSELECT or not in the driver. So if vqmmc supply is 1.8V, set vs18_enable, the driver will set VSELECT. Signed-off-by: NPeng Fan <peng.fan@nxp.com> Cc: Jaehoon Chung <jh80.chung@samsung.com> Cc: York Sun <york.sun@nxp.com> Cc: Stefano Babic <sbabic@denx.de> Reviewed-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Peng Fan 提交于
When using eMMC with 1.8V I/O, the VSELECT bit need to be set in the USDHC controller when init. This patch adds a parameter "vs18_enable" in fsl_esdhc_cfg structure and priv data, so each controller can have different settings. We could not use CONFIG_SYS_FSL_ESDHC_FORCE_VSELECT, it has problem that it will apply to all USDHC controllers and it only set the 1.8V at init phase. So if user does not select to the eMMC device, the voltage on the I/O pins are not correct. Signed-off-by: NPeng Fan <peng.fan@nxp.com> Cc: Jaehoon Chung <jh80.chung@samsung.com> Cc: York Sun <york.sun@nxp.com> Cc: Stefano Babic <sbabic@denx.de>
-