- Sep 12, 2017
-
-
Bin Meng authored
Convert SANDBOX_BITS_PER_LONG to Kconfig and assign it a correct number depending on which host we are going to build and run. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Bin Meng authored
It seems most of the time we are building and running sandbox on 64-bit host. But we do support 32-bit host as well. Introduce Kconfig option for this. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Jean-Jacques Hiblot authored
There is an overflow problem when taking the size instead of the number of blocks in blk_create_device(). This results in a wrong device size: the device apparent size is its real size modulo 4GB. Using the number of blocks instead of the device size fixes the problem and is more coherent with the internals of the block layer. Signed-off-by:
Jean-Jacques Hiblot <jjhiblot@ti.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Sep 11, 2017
-
-
Tom Rini authored
Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Jorge Ramirez-Ortiz authored
Replacing original author Mateusz Kulikowski <mateusz.kulikowski@gmail.com> as db410c maintainer Signed-off-by:
Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
-
- Sep 10, 2017
-
-
Bin Meng authored
At present the IDE device number is initialized to -1, which means we cannot type "ide read" command before setting the device number via "ide device #". For convenience, let's set the first device as the default one. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Bin Meng authored
When there is no CDROM inserted, the block size is zero hence there is no need to create a BLK device for it. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Bin Meng authored
This converts the IDE driver to driver model so that block read and write are fully functional. Fixes: b7c6baef ("x86: Convert MMC to driver model") Reported-by:
Heinrich Schuchardt <xypron.glpk@gmx.de> Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Tested-by:
Heinrich Schuchardt <xypron.glpk@gmx.de>
-
Bin Meng authored
So far these are using magic numbers. Replace them with macros. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Sep 08, 2017
-
-
Tom Rini authored
This board does dwc3 gadget, not host, so we cannot have host support or we will fail to link. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
The underlying implementation for ENV_AES has security complications and is not recommended for use. Please see CVE-2017-3225 and CVE-2017-3226 for more details. Mark this as deprecated now and delete this in the medium term if no one comes forward to re-work the support. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Chris Packham authored
A number of the config options for USB networking have been migrated to Kconfig. Update README.usb to reflect this. Signed-off-by:
Chris Packham <judge.packham@gmail.com>
-
Chris Packham authored
This migrates ASIX, ASIX88179, MCS7830, RTL8152 and SMSC95XX to Kconfig. Update defconfigs. Signed-off-by:
Chris Packham <judge.packham@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Chris Packham authored
CONFIG_USB_HOST_ETHER is the framework that the drivers are dependent on USB_HOST_ETHER. Use this as a menu and move the existing LAN75XX and LAN78XX options under new menu. Finally update the defconfigs that need CONFIG_USB_HOST_ETHER. Signed-off-by:
Chris Packham <judge.packham@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Chris Packham authored
This is not a valid option. Drop it. Signed-off-by:
Chris Packham <judge.packham@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Chris Packham authored
This is not a valid option. Drop it. Signed-off-by:
Chris Packham <judge.packham@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Nobuhiro Iwamatsu authored
The correct name is 'gd->fdt_blob', not 'gd->blob'. Signed-off-by:
Nobuhiro Iwamatsu <iwamatsu@nigauri.org> CC: Simon Glass <sjg@chromium.org> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Tom Rini authored
Rsync all defconfig files using moveconfig.py Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Kever Yang authored
With Makefiles testing for $(SPL_TPL_)SYSRESET, we need SPL_SYSRESET for do_reset() in SPL for Rockchip SoCs. References: 87c16d49 "drivers: spl: consistently use the $(SPL_TPL_) macro" Signed-off-by:
Kever Yang <kever.yang@rock-chips.com> Acked-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
Kever Yang authored
syscon id table need a dummy member as NULL ending, or else system will panic while try to match a compatible in this table as a list. Signed-off-by:
Kever Yang <kever.yang@rock-chips.com> Acked-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
Marek Vasut authored
Disable CONFIG_ARCH_FIXUP_FDT_MEMORY to prevent U-Boot from modifying the memory {} nodes in the DT passed to the Linux kernel. The R8A779x DT contains multiple memory {} nodes, while U-Boot only modifies the first one and stuffs all the memory entries into it, which is wrong. Disabling CONFIG_ARCH_FIXUP_FDT_MEMORY is the least intrusive way to fix the issue this close to the release, while the real fix is to extend the fdt_fixup_memory_banks() to handle multiple memory nodes in DT. Signed-off-by:
Marek Vasut <marek.vasut+renesas@gmail.com> Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
-
Marek Vasut authored
On RCar M3 and on RCar H3 newer than and not including ES1.0, the SD clock must be divided by 4 rather than 2 because a hardware workaround present only in the H3 ES1.0 has been removed from these chips. U-Boot currently only supports M3 and H3 ES 2.0 and newer, so configure the SD pre-divider to 4 to prevent SD instability. Signed-off-by:
Marek Vasut <marek.vasut+renesas@gmail.com> Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
-
- Sep 07, 2017
-
-
git://git.denx.de/u-boot-netTom Rini authored
-
Heinrich Schuchardt authored
%s/Desriptor/Descriptor/g Signed-off-by:
Heinrich Schuchardt <xypron.glpk@gmx.de> Acked-by:
Joe Hershberger <joe.hershberger@ni.com>
-
Madalin Bucur authored
Signed-off-by:
Madalin Bucur <madalin.bucur@nxp.com> Acked-by:
Joe Hershberger <joe.hershberger@ni.com> Acked-by:
York Sun <york.sun@nxp.com>
-
Tom Rini authored
In the general case, CONFIG_NFS_READ_SIZE is unchanged from the default of 1024. There are in fact no in-tree users that increase this size. Adjust the comment to reflect what could be done in the future in conjunction with CONFIG_IP_DEFRAG. Cc: Joe Hershberger <joe.hershberger@ni.com> Signed-off-by:
Tom Rini <trini@konsulko.com> Acked-by:
Joe Hershberger <joe.hershberger@ni.com>
-
Madalin Bucur authored
The old logic always enabled the TX-delay when the phy-mode was set to PHY_INTERFACE_MODE_RGMII. With this patch we enable the TX delay for PHY_INTERFACE_MODE_RGMII_ID and PHY_INTERFACE_MODE_RGMII_TXID and disable it for PHY_INTERFACE_MODE_RGMII. Based on a similar change made in the Linux Realtek PHY driver by Martin Blumenstingl <martin.blumenstingl@googlemail.com>. Signed-off-by:
Madalin Bucur <madalin.bucur@nxp.com> Acked-by:
Joe Hershberger <joe.hershberger@ni.com> Acked-by:
York Sun <york.sun@nxp.com>
-
Kever Yang authored
Delete one redundant 'which' for SPL_ATF_SUPPORT description. Signed-off-by:
Kever Yang <kever.yang@rock-chips.com>
-
Heinrich Schuchardt authored
Remove a comment line refering to a non-existent file. Signed-off-by:
Heinrich Schuchardt <xypron.glpk@gmx.de>
-
Heinrich Schuchardt authored
The inline documentation of vsprintf mentions a parameter size which does not exist in the function declaration. int vsprintf(char *buf, const char *fmt, va_list args); Signed-off-by:
Heinrich Schuchardt <xypron.glpk@gmx.de>
-
Paul Barker authored
This reverts commit 25877d4e. This is a workaround for Raspberry Pi boot failures seen when passing on the device tree provided by the Raspberry Pi firmware at boot. Without CONFIG_OF_EMBED, we just get stuck at "Starting kernel ..." when we try to boot Linux with this device tree. Signed-off-by:
Paul Barker <pbarker@toganlabs.com> Cc: Simon Glass <sjg@chromium.org> Tested-by:
Jonathan Gray <jsg@jsg.id.au> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Bin Meng authored
Some files are generated during libfdt build. Ignore them. This was wrongly put in the .gitignore in the root directory before. Now let's remove entries there and put them in the right place. Fixes: 34e2c285 ("gitignore: add intermediates from libfdt build") Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
-
Bin Meng authored
These are currently out of alphabetical order. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
-
Alison Chaiken authored
Signed-off-by:
Alison Chaiken <alison@she-devel.com>
-
Bin Meng authored
Change to use 'debug' to output the error message if it fails to read the driver descriptor block. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
-
- Sep 06, 2017
-
-
Simon Glass authored
The target is not currently mentioned anywhere. Add it to the help so people can find it. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
This was broken by the recent environment refactoring. Specifically: $ make environ scripts/Makefile.build:59: tools/environ/Makefile: No such file or directory make[1]: *** No rule to make target 'tools/environ/Makefile'. Stop. make: *** [Makefile:1469: environ] Error 2 Fix this by updating the Makefile and adjusting the #include filesnames in two C files. Fixes: ec74f5f9 (Makefile: Rename 'env' target to 'environ') Reported-by:
Måns Rullgård <mans@mansr.com> Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Sam Protsenko authored
Since commit 842778a0 ("usb: gadget: g_dnl: only set iSerialNumber if we have a serial#") "fastboot devices" stopped to show correct device serial number for TI boards, showing this line instead: ???????????? fastboot This is because serial# env variable could be set after g_dnl gadget was initialized (e.g. by using env_set() in the board file). To fix this, let's update internal serial number variable (g_dnl_serial) when "serial#" env var is changed. Signed-off-by:
Sam Protsenko <semen.protsenko@linaro.org> Cc: Felipe Balbi <felipe.balbi@linux.intel.com> Tested-by:
Heiko Schocher <hs@denx.de> Acked-by:
Łukasz Majewski <lukma@denx.de> Reviewed-by:
Marek Vasut <marex@denx.de>
-
- Sep 05, 2017
-
-
Tom Rini authored
With the move of environment code from common/ to env/ a number of changes needed to be made to various make targets. We missed updating some of the files required for out of tree builds of the tools. Correct the 'environ' target to know that we need to work under tools/env/ still (not tools/environ/) and then update the wrappers in env_attr.c and env_flags.c to point to the new correct file. Reported-by:
Peter Robinson <pbrobinson@gmail.com> Tested-by:
Peter Robinson <pbrobinson@gmail.com> Signed-off-by:
Tom Rini <trini@konsulko.com>
-
git://git.denx.de/u-boot-videoTom Rini authored
-