- 10 7月, 2018 10 次提交
-
-
由 Manivannan Sadhasivam 提交于
Add myself as the Maintainer for Actions Semi OWL family and its relevant board, drivers. Signed-off-by: NManivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
-
由 Manivannan Sadhasivam 提交于
This commit adds Actions Semi OWL family UART support. This driver relies on baudrate configured by primary bootloaders. Signed-off-by: NManivannan Sadhasivam <manivannan.sadhasivam@linaro.org> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Manivannan Sadhasivam 提交于
This commit enables UART5 found in S900 SoC for serial console support. Signed-off-by: NManivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
-
由 Manivannan Sadhasivam 提交于
This commit adds UART node for Actions Semi S900 SoC. Signed-off-by: NManivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
-
由 Manivannan Sadhasivam 提交于
This commit adds Actions Semi OWL family base clock and S900 SoC specific clock support. For S900 peripheral clock support, only UART clock has been added for now. Signed-off-by: NManivannan Sadhasivam <manivannan.sadhasivam@linaro.org> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Manivannan Sadhasivam 提交于
This commit adds Clock Management Unit (CMU) nodes for Actions Semi S900 SoC. Signed-off-by: NManivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
-
由 Manivannan Sadhasivam 提交于
This commit adds Actions Semi S900 CMU register definitions to clock bindings. Signed-off-by: NManivannan Sadhasivam <manivannan.sadhasivam@linaro.org> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Manivannan Sadhasivam 提交于
This commit adds uCRobotics Bubblegum-96 board support. This board is one of the 96Boards Consumer Edition platform based on Actions Semi S900 SoC. Features: - Actions Semi S900 SoC (4xCortex A53, Power VR G6230 GPU) - 2GiB RAM - 8GiB eMMC, uSD slot - WiFi, Bluetooth and GPS module - 2x Host, 1x Device USB port - HDMI - 20-pin low speed and 40-pin high speed expanders, 6 LED, 3 buttons U-Boot will be loaded by ATF at EL2 execution level. Relevant driver support will be added in further commits. Signed-off-by: NManivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
-
由 Manivannan Sadhasivam 提交于
This commit adds Actions Semi OWL SoC family support with S900 as the first target SoC. Signed-off-by: NManivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
-
由 Tom Rini 提交于
Rsync all defconfig files using moveconfig.py Signed-off-by: NTom Rini <trini@konsulko.com>
-
- 09 7月, 2018 2 次提交
-
-
由 Tom Rini 提交于
Signed-off-by: NTom Rini <trini@konsulko.com>
-
-
- 07 7月, 2018 2 次提交
-
-
-
由 Peter Robinson 提交于
To build U-Boot on a Nyan Big Chromebook the docs outline adjusting the Tegra124 defined CONFIG_SYS_TEXT_BASE but this has since been moved to individual config files. We should have the default required for U-Boot chain loading on the chromebook as the default CONFIG_SYS_TEXT_BASE and update the docs to remove this now non required step. Signed-off-by: NPeter Robinson <pbrobinson@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org> Signed-off-by: NTom Warren <twarren@nvidia.com>
-
- 06 7月, 2018 1 次提交
-
-
- 05 7月, 2018 2 次提交
-
-
由 Andre Przywara 提交于
On the A64 the clock for the first USB controller is actually the parent of the clock for the second controller, so turning them off in that order makes the system hang. Fix this by only turning off *both* clocks when the *last* OHCI controller is brought down. This covers the case when only one controller is used. Signed-off-by: NAndre Przywara <andre.przywara@arm.com>
-
由 Emmanuel Vadot 提交于
When using CONFIG_OF_BOARD on rpi to use the dtb provided by the RaspberryPi Fundation, the compatible string isn't the same, resulting in not-functional usb from u-boot. Signed-off-by: NOleksandr Tymoshenko <gonzo@FreeBSD.org> Signed-off-by: NEmmanuel Vadot <manu@freebsd.org>
-
- 04 7月, 2018 3 次提交
-
-
-
由 Andre Przywara 提交于
The Allwinner A64 SoCs suffers from an arch timer implementation erratum, where sometimes the lower 11 bits of the counter value erroneously become all 0's or all 1's [1]. This leads to sudden jumps, both forwards and backwards, with the latter one often showing weird behaviour. Port the workaround proposed for Linux to U-Boot and activate it for all A64 boards. This fixes crashes when accessing MMC devices (SD cards), caused by a recent change to actually use the counter value for timeout checks. Fixes: 5ff8e548 ("sunxi: improve throughput in the sunxi_mmc driver") [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2018-May/576886.htmlSigned-off-by: NAndre Przywara <andre.przywara@arm.com> Reviewed-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com> Tested-by: NJagan Teki <jagan@amarulasolutions.com> Tested-by: NAndreas Färber <afaerber@suse.de> Tested-by: NGuillaume Gardet <guillaume.gardet@free.fr>
-
由 Andre Przywara 提交于
At the moment we have the workaround for the Freescale arch timer erratum A-008585 merged into the generic timer_read_counter() routine. Split those two up, so that we can add other errata workaround more easily. Also add an explaining comment on the way. Signed-off-by: NAndre Przywara <andre.przywara@arm.com> Tested-by: NJagan Teki <jagan@amarulasolutions.com> Tested-by: NAndreas Färber <afaerber@suse.de> Tested-by: NGuillaume Gardet <guillaume.gardet@free.fr>
-
- 03 7月, 2018 12 次提交
-
-
由 Tom Rini 提交于
Signed-off-by: NTom Rini <trini@konsulko.com>
-
-
由 Tom Rini 提交于
The various Aries Embedded boards have been orphaned for a year and no one has come forward to take care of them. Remove. Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Alexander Graf 提交于
The ax25-ae350 target currently uses CONFIG_BOOTP_SERVERIP which means we ignore the DHCP provided TFTP ip address. This breaks every case where we do now provide a serverip environment variable. Instead, let's use the new CONFIG_BOOT_PREFER_SERVERIP option to fall back to the DHCP provided TFTP IP if no serverip environment variable is set. Signed-off-by: NAlexander Graf <agraf@suse.de> Acked-by: NJoe Hershberger <joe.hershberger@ni.com> Acked-by: NRick Chen <rick@andestech.com>
-
由 Alexander Graf 提交于
Currently we can choose between 2 different types of behavior for the serverip variable: 1) Always overwrite it with the DHCP server IP address (default) 2) Ignore what the DHCP server says (CONFIG_BOOTP_SERVERIP) This patch adds a 3rd option: 3) Use serverip from DHCP if no serverip is given (CONFIG_BOOTP_PREFER_SERVERIP) With this new option, we can have the default case that a boot file gets loaded from the DHCP provided TFTP server work while allowing users to specify their own serverip variable to explicitly use a different tftp server. Signed-off-by: NAlexander Graf <agraf@suse.de> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Alexander Graf 提交于
We can call commands like dhcp and bootp without arguments or with explicit command line arguments that really should tell the code where to look for files instead. Unfortunately, the current code simply overwrites command line arguments in the dhcp case with dhcp values. This patch allows the code to preserve the command line values if they were set on the command line. That way the semantics are slightly more intuitive. The reason this patch does that by introducing a new variable is that we can not rely on net_boot_file_name[0] being unset, as today it's completely legal to call "dhcp" and afterwards run "tftp" and expect the latter to repeat the same query as before. I would prefer not to break that behavior in case anyone relies on it. Signed-off-by: NAlexander Graf <agraf@suse.de> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Lothar Felten 提交于
Add a new command 'wol': Wait for an incoming Wake-on-LAN packet or time out if no WoL packed is received. If the WoL packet contains a password, it is saved in the environment variable 'wolpassword' using the etherwake format (dot or colon separated decimals). Intended use case: a networked device should boot an alternate image. It's attached to a network on a client site, modifying the DHCP server configuration or setup of a tftp server is not allowed. After power on the device waits a few seconds for a WoL packet. If a packet is received, the device boots the alternate image. Otherwise it boots the default image. This method is a simple way to interact with a system via network even if only the MAC address is known. Tools to send WoL packets are available on all common platforms. Some Ethernet drivers seem to pad the incoming packet. The additional padding bytes might be recognized as Wake-on-LAN password bytes. By default enabled in pengwyn_defconfig. Signed-off-by: NLothar Felten <lothar.felten@gmail.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Rabeeh Khoury 提交于
Make the initialization sequence consistent with the Linux kernel driver. Reviewed-by: NStefan Roese <sr@denx.de> Acked-by: NJoe Hershberger <joe.hershberger@ni.com> Signed-off-by: NRabeeh Khoury <rabeeh@solid-run.com> Signed-off-by: NBaruch Siach <baruch@tkos.co.il>
-
由 Rabeeh Khoury 提交于
This fixes sporadic timeout on initial packet Tx (usually ARP), with an error message like: timeout: packet not sent Reviewed-by: NStefan Roese <sr@denx.de> Tested-by: NChris Packham <judge.packham@gmail.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com> Signed-off-by: NRabeeh Khoury <rabeeh@solid-run.com> Signed-off-by: NBaruch Siach <baruch@tkos.co.il>
-
由 Alex Kiernan 提交于
When building without FASTBOOT_FLASH we don't include the intermediate update callback to keep the client alive, so ensure we don't try setting it here. Signed-off-by: NAlex Kiernan <alex.kiernan@gmail.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Michal Simek 提交于
phyread can timeout and val will contain random value. Initialize it to zero not to report random value in case of error. Signed-off-by: NMichal Simek <michal.simek@xilinx.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
-
- 02 7月, 2018 8 次提交
-
-
由 Emmanuel Vadot 提交于
When using CONFIG_OF_BOARD on rpi to use the dtb provided by the RaspberryPi Fundation, the compatible string isn't the same, resulting in not-functional video in u-boot. Signed-off-by: NOleksandr Tymoshenko <gonzo@FreeBSD.org> Signed-off-by: NEmmanuel Vadot <manu@freebsd.org>
-
-
由 Tom Rini 提交于
As pointed out by Wolfgang Denk, the problem with this fix is that while interactive users will see that we have found one part of the environment failed and are using the other, progmatic use will not see this and can lead to problems. Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Bin Meng 提交于
This updates the doc to mention chain-loading an x86 kernel via 'bootefi' command, along with several typos fix. Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NAlexander Graf <agraf@suse.de>
-
由 Bin Meng 提交于
CONFIG_EFI_LOADER is fully supported on x86 now. Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NAlexander Graf <agraf@suse.de>
-
由 Bin Meng 提交于
Output ACPI configuration table if it exists. Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Bin Meng 提交于
ACPI tables can be passed via EFI configuration table to an EFI application. This is only supported on x86 so far. Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Bin Meng 提交于
At present the number of configuration tables is set to 2. By looking at which tables the Linux EFI stub or iPXE can process, it looks 16 is a reasonable number. Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-