- 19 6月, 2020 2 次提交
-
-
由 Anatolij Gustschin 提交于
After migration to DM 'vga' name is not longer supported, Update the upgrade script to use 'vidconsole' instead. Signed-off-by: NAnatolij Gustschin <agust@denx.de> Cc: Troy Kisky <troy.kisky@boundarydevices.com> Acked-by: NTroy Kisky <troy.kisky@boundarydevices.com>
-
由 Troy Kisky 提交于
Enable driver model for Video to remove compiler warning. To enable display, issue setenv stdout serial,vidconsole; Add CONFIG_DM_VIDEO to all defconfigs whose board is nitrogen6x. mx6qsabrelite_defconfig nitrogen6dl2g_defconfig nitrogen6dl_defconfig nitrogen6q2g_defconfig nitrogen6q_defconfig nitrogen6s1g_defconfig nitrogen6s_defconfig Signed-off-by: NTroy Kisky <troy.kisky@boundarydevices.com> Tested-by: NAnatolij Gustschin <agust@denx.de>
-
- 16 6月, 2020 1 次提交
-
-
由 Harald Seiler 提交于
Remove a left-over debug printf that was introduced with SHA512 support. Fixes: d16b38f4 ("Add support for SHA384 and SHA512") Signed-off-by: NHarald Seiler <hws@denx.de>
-
- 13 6月, 2020 32 次提交
-
-
git://git.denx.de/u-boot-dm由 Tom Rini 提交于
patman improvements to allow it to work with Zephyr change to how sequence numbers are assigned to devices minor fixes and improvements
-
由 Tom Rini 提交于
- Merge tbs2910 distro boot support and associated clean-ups and size reduction. - Assorted networking corrections / bugfixes. - Drop smc911x standalone API example as it was likely non-functional for a long time. - Enhanced support for TI PHYs - rtl8139 DM conversion
-
由 Baruch Siach 提交于
The random_port() routine is not used anywhere else. Make it local to dns.c to reduce code clutter, and shrink generated code a little. Signed-off-by: NBaruch Siach <baruch@tkos.co.il>
-
由 Ravik Hasija 提交于
RFC2348, RFC2349: - Option string is case in-sensitive. - Client must generate ERR pkt in case option value mismatch in server OACK - Fix debug print for options Signed-off-by: NRavik Hasija <rahasij@linux.microsoft.com> Reviewed-By: NRamon Fried <rfried.dev@gmail.com>
-
由 Marek Vasut 提交于
Add support for driver model to the driver. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Joe Hershberger <joe.hershberger@ni.com>
-
由 Marek Vasut 提交于
Do not re-read the HW address from the EEPROM on every start of transfer, otherwise the user will not be able to adjust ethaddr as needed. Read the address only once, when the card is detected. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Joe Hershberger <joe.hershberger@ni.com>
-
由 Marek Vasut 提交于
Use this macro to fully fill the PCI device ID table. This is mandatory for the DM PCI support, which checks all the fields. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Joe Hershberger <joe.hershberger@ni.com>
-
由 Marek Vasut 提交于
Split the driver into common and non-DM functionality, so that the DM support can later re-use the common code, while we retain the non-DM code until all the platforms are converted. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Joe Hershberger <joe.hershberger@ni.com>
-
由 Marek Vasut 提交于
Instead of always calling rtl8139_eeprom_delay() with priv->ioaddr, call it with priv and let the function access priv->ioaddr. This reduces code duplication and has no impact, since the compiler will inline this as needed anyway. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Joe Hershberger <joe.hershberger@ni.com>
-
由 Marek Vasut 提交于
Introduce rtl8139_pdata, which is a super-structure around eth_device and tracks per-device state, here the device IO address, PCI BDF, RX and TX ring position. Pass this structure around instead of the old non-DM eth_device in preparation for DM conversion. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Joe Hershberger <joe.hershberger@ni.com>
-
由 Marek Vasut 提交于
These macros depended on the dev variable being declared wherever they were used. This is wrong and will not work with DM anyway, so pass only the PCI BFD into these macros, which fixes the dependency and prepares them for DM support as well. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Joe Hershberger <joe.hershberger@ni.com>
-
由 Marek Vasut 提交于
Replace the use of custom static ioaddr variable with common dev->iobase, no functional change. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Joe Hershberger <joe.hershberger@ni.com>
-
由 Marek Vasut 提交于
Replace malloc()+memset() combination with calloc(), no functional change. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Joe Hershberger <joe.hershberger@ni.com>
-
由 Marek Vasut 提交于
Pull the device name setting into a separate function, as this will be shared between DM/non-DM variants. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Joe Hershberger <joe.hershberger@ni.com>
-
由 Ravik Hasija 提交于
During packet sequence number wraparound the show_block_marker() API was not called, as a result the progress marker doesn't stay within column boundary. Use position in file instead of sequence number to align the marker. Signed-off-by: NRavik Hasija <rahasij@linux.microsoft.com> Reviewed-By: NRamon Fried <rfried.dev@gmail.com>
-
由 Dan Murphy 提交于
Add the DP8382X generic PHY registration to the TI PHY init file. Acked-by: NMichal Simek <michal.simek@xilinx.com> Signed-off-by: NDan Murphy <dmurphy@ti.com>
-
由 Dan Murphy 提交于
ti_phy_init function was allocated to the DP83867 PHY. This function name is to generic for a specific PHY. The function can be moved to a TI specific file that can register all TI PHYs that are defined in the defconfig. The ti_phy_init file will contain all TI PHYs initialization so that only phy_ti_init can be called from the framework. In addition to the above the config flag for the DP83867 needs to be changed in the Kconfig and dependent defconfig files. The config flag that was used for the DP83867 was also generic in nature so a more specific config flag for the DP83867 was created. Acked-by: NMichal Simek <michal.simek@xilinx.com> Signed-off-by: NDan Murphy <dmurphy@ti.com>
-
由 Dan Murphy 提交于
Add phy_set/clear_bit helper routines so that ported drivers from the kernel can use these functions. Acked-by: NMichal Simek <michal.simek@xilinx.com> Signed-off-by: NDan Murphy <dmurphy@ti.com>
-
由 Dan Murphy 提交于
Fix kernel doc warnings in phy.h. Mostly the warnings were due to the return missing the semi-colon. Acked-by: NMichal Simek <michal.simek@xilinx.com> Signed-off-by: NDan Murphy <dmurphy@ti.com>
-
由 Dan Murphy 提交于
Add kernel doc to the phy_read/write utility functions in phy.h Acked-by: NMichal Simek <michal.simek@xilinx.com> Signed-off-by: NDan Murphy <dmurphy@ti.com>
-
由 Florin Chiculita 提交于
There are devices accesible through mdio clause-45, such as retimers, that do not have PMA or PCS blocks. This patch adds MDIO_MMD_VEND1 on the list of device addresses where phyid is searched. Previous order of devices was kept. Signed-off-by: NFlorin Chiculita <florinlaurentiu.chiculita@nxp.com> Reviewed-by: NMadalin Bucur <madalin.bucur@oss.nxp.com>
-
由 Tom Warren 提交于
This is a WAR for DHCP failure after rebooting from the L4T kernel. The r8169.c kernel driver is setting bit 19 of the rt816x HW register 0xF0, which goes by FuncEvent and MISC in various driver source/datasheets. That bit is called RxDv_Gated_En in the r8169.c kernel driver. Clear it here at the end of probe to ensure that U-Boot can get an IP assigned via DHCP. Signed-off-by: NTom Warren <twarren@nvidia.com>
-
由 Bryan O'Donoghue 提交于
Linux commit 232ba3a51cc2 ('net: phy: Micrel KSZ8061: link failure after cable connect') implements a fix for the above errata. This patch replicates that errata fix in an ksz8061 specific init routine. Signed-off-by: NBryan O'Donoghue <bod@denx.de> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Marek Vasut 提交于
Drop the example, for two reasons. First, it is tapping directly into the IO accessors of the SMC911x, while it should instead go through the net device API. Second, this makes conversion of the SMC911x driver to DM real hard. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Joe Hershberger <joe.hershberger@ni.com> Cc: Tom Rini <trini@konsulko.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Krebs, Olaf 提交于
If 'CONFIG_CMD_TFTPBOOT' or 'CONFIG_CMD_BOOTP' are disabled, the usage must be disabled, too! Signed-off-by: NOlaf Krebs <olaf.krebs@emh-metering.com> CC: Joe Hershberger <joe.hershberger@ni.com>
-
由 Denis 'GNUtoo' Carikli 提交于
This documents the u-boot installation procedure and the hardware in order to get started. Signed-off-by: NDenis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> [trini: Add MAINTAINERS entry for doc file per Soeren's request]
-
由 Denis 'GNUtoo' Carikli 提交于
This keeps the compatibility with the old bootcmd. The fdtfile environment variable also needed to be set to imx6q-tbs2910.dtb to enable booting mainline kernels otherwise with extlinux.conf it tries to load mx6-tbs2910.dtb instead. With arm-linux-gnueabi-gcc 9.2.0-1 from the Parabola GNU/Linux distribution, we have the following size differences: - text: +2041 bytes - data: 0 bytes - bss: 0 bytes - total: +2041 bytes Signed-off-by: NDenis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> Reviewed-by: NSoeren Moch <smoch@web.de>
-
由 Denis 'GNUtoo' Carikli 提交于
This is needed to enable distro_boot support later on. Adding the necessary configuration to enable booting general purpose distributions is typically done by enabling CONFIG_DISTRO_DEFAULTS. However the resulting image size is is already very close to the size limit and PXE isn't strictly needed, so instead we made sure that all the configuration selected by CONFIG_DISTRO_DEFAULTS were selected, with the exception of PXE related configuration (CONFIG_BOOTP_PXE and CONFIG_CMD_PXE) that are both disabled. With arm-linux-gnueabi-gcc 9.3.0-1 from the Parabola GNU/Linux distribution, we have the following size differences: - text: +7526 bytes - data: +28 bytes - bss: -12 bytes - total: +7542 bytes Signed-off-by: NDenis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> Reviewed-by: NSoeren Moch <smoch@web.de>
-
由 Denis 'GNUtoo' Carikli 提交于
This doesn't affect the size of the image: with arm-linux-gnueabi-gcc 9.2.0-1 from the Parabola GNU/Linux distribution, the text, data, bss and total sizes remain unchanged. Signed-off-by: NDenis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> Reviewed-by: NSoeren Moch <smoch@web.de>
-
由 Denis 'GNUtoo' Carikli 提交于
As that the resulting image is already very close to the size limit, and that CONFIG_GZIP is not strictly required, removing it shouldn't hurt. With arm-linux-gnueabi-gcc 9.2.0-1 from the Parabola GNU/Linux distribution we have the following size reduction: - text: 9752 - data: 0 - bss: 16 - total: 9768 Signed-off-by: NDenis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> Acked-by: NSoeren Moch <smoch@web.de>
-
由 Denis 'GNUtoo' Carikli 提交于
The loadb and loads commands are not needed for booting. There are also more reliable and faster alternatives to loadb and loads that can be used with the current configuration. As that the resulting image is already very close to the size limit, removing the loadb and loads commands shouldn't hurt. With arm-linux-gnueabi-gcc 9.2.0-1 from the Parabola GNU/Linux distribution we have the following size reduction: - text: 6733 bytes - data: 116 bytes - bss: 1172 bytes - total: 8021 bytes Signed-off-by: NDenis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> Acked-by: NSoeren Moch <smoch@web.de>
-
由 Reuben Dowle 提交于
The current recommendation for best security practice from the US government is to use SHA384 for TOP SECRET [1]. This patch adds support for SHA384 and SHA512 in the hash command, and also allows FIT images to be hashed with these algorithms, and signed with sha384,rsaXXXX and sha512,rsaXXXX The SHA implementation is adapted from the linux kernel implementation. [1] Commercial National Security Algorithm Suite http://www.iad.gov/iad/programs/iad-initiatives/cnsa-suite.cfmSigned-off-by: NReuben Dowle <reuben.dowle@4rf.com>
-
- 12 6月, 2020 5 次提交
-
-
由 Dario Binacchi 提交于
Fix the 'memeber' typo in doc/driver-model/design.rst. Signed-off-by: NDario Binacchi <dariobin@libero.it> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Michael Walle 提交于
If there are aliases for an uclass, set the base for the "dynamically" allocated numbers next to the highest alias. Please note, that this might lead to holes in the sequences, depending on the device tree. For example if there is only an alias "ethernet1", the next device seq number would be 2. In particular this fixes a problem with boards which are using ethernet aliases but also might have network add-in cards like the E1000. If the board is started with the add-in card and depending on the order of the drivers, the E1000 might occupy the first ethernet device and mess up all the hardware addresses, because the devices are now shifted by one. Also adapt the test cases to the new handling and add test cases checking the holes in the seq numbers. Signed-off-by: NMichael Walle <michael@walle.cc> Reviewed-by: NAlex Marginean <alexandru.marginean@nxp.com> Tested-by: NAlex Marginean <alexandru.marginean@nxp.com> Acked-by: NVladimir Oltean <olteanv@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org> Tested-by: Michal Simek <michal.simek@xilinx.com> [on zcu102-revA]
-
由 Michael Walle 提交于
If CONFIG_DM_DEV_READ_INLINE is set, dev_read_alias_highest_id() calls libfdt_get_highest_id(). But this function is only available if we have libfdt compiled in. If its not available return -1, which matches the return code for no alias found. This fixes the following error on omapl138_lcdk: arm-linux-gnueabi-ld.bfd: drivers/built-in.o: in function `dev_read_alias_highest_id': /home/mw/repo/u-boot/include/dm/read.h:986: undefined reference to `fdtdec_get_alias_highest_id' Signed-off-by: NMichael Walle <michael@walle.cc> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Michael Walle 提交于
It is possible to specify a device tree node for an USB device. This is useful if you have a static USB setup and want to use aliases which point to these nodes, like on the Raspberry Pi. The nodes are matched against their hub port number, the compatible strings are not matched for now. Signed-off-by: NMichael Walle <michael@walle.cc> Reviewed-by: NMarek Vasut <marex@denx.de> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Heinrich Schuchardt 提交于
Check that the argument provided to the 'log level' command is in the range between zero and CONFIG_LOG_MAX_LEVEL. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by: NSimon Glass <sjg@chromium.org>
-