- Aug 08, 2023
-
-
The VNBYTES() macro needs to have parentheses to prevent some (harmless) macro expansion bugs. The VNBYTES() macro is used like this: VID_TO_PIXEL(x) * VNBYTES(vid_priv->bpix) The * operation is done before the / operation. It still ends up with the same results, but it's not ideal. Signed-off-by:
Dan Carpenter <dan.carpenter@linaro.org> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
The parentheses are in the wrong place so this passes the number of bytes to write as "sizeof(index_0) != TPM_SUCCESS" when just "sizeof(index_0)" was intended. (1 byte vs 4 bytes). Signed-off-by:
Dan Carpenter <dan.carpenter@linaro.org>
-
This returns the wrong variable. It ends up returning NULL when it was suppose to return an error pointer. Signed-off-by:
Dan Carpenter <dan.carpenter@linaro.org>
-
strlcat returns min(strlen(dest), count)+strlen(src). Make u16_strlcat's behaviour the same for consistency. Fixes: eca08ce9 ("lib/charset: add u16_strlcat() function") Signed-off-by:
Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
-
Both the Linux kernel and libbsd agree that strlcpy() should always return strlen(src) and not include the NUL termination. The incorrect U-Boot implementation makes it impossible to check the return value for truncation, and breaks code written with the usual implementation in mind (for example, fdtdec_add_reserved_memory() was subtly broken). I reviewed all callers of strlcpy() and strlcat() and fixed them according to my understanding of the intended function. This reverts commit d3358ecc and adds related fixes. Fixes: d3358ecc ("lib: string: Fix strlcpy return value") Signed-off-by:
Matthias Schiffer <matthias.schiffer@ew.tq-group.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Sean Anderson <sean.anderson@seco.com>
-
- Aug 07, 2023
-
-
Tom Rini authored
Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
Rsync all defconfig files using moveconfig.py Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
- Update Azure jobs again, a few MAINTAINERS updates, a few Kconfig fixes, an erofs fix and a fix for the recent ten64 updates.
-
In [1] Sam points out an assertion does not hold true for 32-bit platforms, which only impacts Large File Support (LFS) API usage in erofs-utils according to Xiang [2]. We don't think these APIs are used in u-boot and this restriction could be safely removed. [1] https://lists.denx.de/pipermail/u-boot/2023-July/524679.html [2] https://lists.denx.de/pipermail/u-boot/2023-July/524727.html Fixes: 3a21e92f ("fs/erofs: Introduce new features including ztailpacking, fragments and dedupe") Signed-off-by:
Yifan Zhao <zhaoyifan@sjtu.edu.cn> Tested-by:
Sam Edwards <CFSworks@gmail.com>
-
Drop duplicate space in Kconfig symbol description. Signed-off-by:
Marek Vasut <marex@denx.de>
-
CONFIG_$(SPL_TPL_)SYS_MALLOC_F_LEN is defined as hex. If set to zero manually, .config contains '0x0' and not '0' as value. The default value for CONFIG_SPL_SYS_MALLOC_F_LEN should not be set to 0 but to 0x0 if CONFIG_SPL_FRAMEWORK=n to match a manually set value. Fixes: c0126bd8 ("spl: Support bootstage, log, hash and early malloc in TPL") Fixes: b6169470 ("SPL: Do not enable SPL_SYS_MALLOC_SIMPLE without SPL_FRAMEWORK by default") Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
All SPL hash algorithm options are collected in lib/Kconfig. Move SPL_CRC32 there as well. Signed-off-by:
Oleksandr Suvorov <oleksandr.suvorov@foundries.io> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
There is another SPL_MD5 option defined in lib/Kconfig. Renaming SPL_MD5_SUPPORT introduced duplicate option with different description. As for now FIT and hash algorithm options are not related to each others, removing a duplicate option seems OK. Fixes: 4b00fd1a ("Kconfig: Rename SPL_MD5_SUPPORT to SPL_MD5") Signed-off-by:
Oleksandr Suvorov <oleksandr.suvorov@foundries.io>
-
Tom Rini authored
In the common bloblist code we call crc32 to get a checksum for the data. Ensure we will have the CRC32 code via select. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Add px30, rv1126 soc, and rockchip soc based boards. Signed-off-by:
Kever Yang <kever.yang@rock-chips.com>
-
With this change the DT and binding files are under the at91 tree maintainer, and get_maintainer.pl correctly reports the entry. Signed-off-by:
Eugen Hristev <eugen.hristev@collabora.com>
-
The retimer reset/power on logic was changed in a recent commit, however, it neglected to check if the commands sent to the board microcontroller (to control power to the retimer chip) actually completed. Add return checks for these operations so any failures will be reported to the user. Signed-off-by:
Mathew McBride <matt@traverse.com.au> Fixes: 7a041fea ("board: traverse: ten64: ensure retimer reset is done on new board revisions")
-
Update MAINTAINERS file. Add missing MAINTAINERS file for Spider, Whitehawk and V3HSK boards. Update mail addresses. Add file globs to match on DT and driver files related to these boards. The GRPEACH and R2DPLUS are special in that they are not R-Car and have their own set of specialized drivers. Signed-off-by:
Marek Vasut <marek.vasut+renesas@mailbox.org>
-
Tom Rini authored
As Pali Rohár has asked to not be copied on changes to files he is not a specific maintainer of, add his address to .get_maintainer.ignore. Signed-off-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Michael Trimarchi <michael@amarulasolutions.com>
-
Tom Rini authored
To reduce overall job time, move a number of smaller jobs together. These should still be safely under 1 hour total time, but reducing the overall number of jobs should help with the queue slightly. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
The job for rockchip vendor platforms has again gotten close to or exceeded one hour. Rework things such that we move the 32bit platforms back to the general 32bit ARM job (as there's time there) and make these build only the 64bit platforms. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Aug 06, 2023
-
-
https://source.denx.de/u-boot/custodians/u-boot-dmTom Rini authored
binman support for Xilinx signing buildman minor fixes
-
- Aug 05, 2023
-
-
Simon Glass authored
Some boards use a MAINTAINERS entry to specify common files without referencing any defconfigs. This is allowed and should not result in a warning. Drop the warning in this case. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Recent refactoring changed buildman to continue operation after fetching a toolchain. Fix this. Fixes: b8680646 ("bulidman: Move toolchain handling to a function") Signed-off-by:
Simon Glass <sjg@chromium.org>
-
DM_POST_INIT was changed to DM_POST_INIT_F. To debug correct message, change type_name from dm_post_init to dm_post_init_f. Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com> Reviewed-by:
Simon Glass <sjg@chromium.org> s/an/a/ : Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Add test for the 'xilinx-bootgen' etype Signed-off-by:
Lukas Funke <lukas.funke@weidmueller.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Allow missing bootgen tool; comment testXilinxBootgenMissing() comment: Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This adds a new etype 'xilinx-bootgen'. By using this etype it is possible to created an signed SPL (FSBL in Xilinx terms) for ZynqMP boards. The etype uses Xilinx Bootgen tools in order to transform the SPL into a bootable image and sign the image with a given primary and secondary public key. For more information to signing the FSBL please refer to the Xilinx Bootgen documentation. Here is an example of the etype in use: spl { filename = "boot.signed.bin"; xilinx-bootgen { pmufw-filename = "pmu-firmware.elf"; psk-key-name-hint = "psk0"; ssk-key-name-hint = "ssk0"; auth-params = "ppk_select=0", "spk_id=0x00000000"; u-boot-spl-nodtb { }; u-boot-spl-dtb { }; }; }; For this to work the hash of the primary public key has to be fused into the ZynqMP device and authentication (RSA_EN) has to be set. For testing purposes: if ppk hash check should be skipped one can add the property 'fsbl_config = "bh_auth_enable";' to the etype. However, this should only be used for testing(!). Signed-off-by:
Lukas Funke <lukas.funke@weidmueller.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Add the Xilinx Bootgen as bintool. Xilinx Bootgen is used to create bootable SPL (FSBL in Xilinx terms) images for Zynq/ZynqMP devices. The btool creates a signed version of the SPL. Additionally to signing the key source for the decryption engine can be passend to the boot image. Signed-off-by:
Lukas Funke <lukas.funke@weidmueller.com>
-
Simon Glass authored
These have ended up with the same numbers as earlier files. Fix them. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
https://source.denx.de/u-boot/custodians/u-boot-usbTom Rini authored
- Fix some issues with usb gadget ethernet. A small set of updates for docs, etc, is still pending
-
The nature of the network stack means that if we are going to use the gadget mode USB network driver there's no easy path to implicitly bind/unbind the driver. Enable the "bind" command by default here so that we can bind/unbind this as needed. Signed-off-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Miquel Raynal <miquel.raynal@bootlin.com>
-
Marek Vasut authored
Move the ethernet gadget driver registration and removal from ethernet bind and unbind callbacks into driver DM probe and remove callbacks. This way, when the driver is bound, which is triggered deliberately using 'bind' command, the USB ethernet gadget driver is instantiated and bound to the matching UDC. In reverse, when the driver is unbound, which is again triggered deliberately using 'unbind' command, the USB ethernet gadget driver instance is removed. Effectively, this now behaves like running either 'ums' or 'dfu' or any other commands utilizing USB gadget functionality. This also drops use of usb_gadget_release() and moves the use of usb_gadget_initialize() into usb_ether_init() used only by legacy platforms that do not use 'bind' command properly yet. Those have no place in drivers. Signed-off-by:
Marek Vasut <marex@denx.de> Tested-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
Marek Vasut authored
Move the driver probe function above the driver structure, so it can be placed alongside other related functions, like upcoming remove function. No functional change. Signed-off-by:
Marek Vasut <marex@denx.de> Tested-by:
Tom Rini <trini@konsulko.com> Tested-by:
Miquel Raynal <miquel.raynal@bootlin.com> Tested-by:
Miquel Raynal <miquel.raynal@bootlin.com> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
Marek Vasut authored
These functions here are only ever called once since drop of non-DM networking code. Inline them. No functional change. Signed-off-by:
Marek Vasut <marex@denx.de> Tested-by:
Tom Rini <trini@konsulko.com> Tested-by:
Miquel Raynal <miquel.raynal@bootlin.com> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
- Aug 04, 2023
-
-
Tom Rini authored
Two Toradex platform series. First, to quote Andrejs: This series adds Yavia Carrier board name string to the known Toradex carrier board list, and reworks carrier board and display adapter name handling. And then to quote Marcel: This series adds initial support for the Toradex Verdin AM62 SoM. The first commit adds resp. PID4s to the ConfigBlock, the second one fixes an early clocking issue confirmed to be a weird bug in TI's scripting, the third one fixes some binman labeling issue. And last but not least support for the Toradex Verdin AM62 is added.
-
This adds initial support for the Toradex Verdin AM62 Quad 1GB WB IT V1.0A module and subsequent V1.1 launch configuration SKUs. They are strapped to boot from their on-module eMMC. U-Boot supports booting from the on-module eMMC only, DFU support is disabled for now due to missing AM62x USB support. The device trees were taken straight from Linux v6.5-rc1. Boot sequence is: SYSFW ---> R5 SPL (both in tiboot3.bin) ---> ATF (TF-A) ---> OP-TEE ---> A53 SPL (part of tispl.bin) ---> U-boot proper (u-boot.img) Signed-off-by:
Marcel Ziswiler <marcel.ziswiler@toradex.com> Reviewed-by:
Nishanth Menon <nm@ti.com>
-
Fix rcfg_yaml to really point to rm-cfg.yaml and pcfg_yaml to really point to pm-cfg.yaml which likely is the intention. While at it also add labels for the remaining items like custmpk_pem, dkey_pem, bcfg_yaml_sysfw, scfg_yaml_sysfw, pcfg_yaml_sysfw and rcfg_yaml_sysfw. Signed-off-by:
Marcel Ziswiler <marcel.ziswiler@toradex.com> Reviewed-by:
Neha Malcom Francis <n-francis@ti.com> Reviewed-by:
Nishanth Menon <nm@ti.com>
-
Fix second mux option of clkout0 which should really be DEV_BOARD0_CLKOUT0_IN_PARENT_HSDIV4_16FFT_MAIN_2_HSDIVOUT1_CLK10 rather than twice the same according to [1]. [1] https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/am62x/clocks.html#clocks-for-board0-device Signed-off-by:
Marcel Ziswiler <marcel.ziswiler@toradex.com> Reviewed-by:
Bryan Brattlof <bb@ti.com> Reviewed-by:
Nishanth Menon <nm@ti.com>
-
Add initial Verdin AM62 Quad 1GB WB IT prototype and launch configuration SKUs to ConfigBlock handling. 0069: Verdin AM62 Quad 1GB WB IT 0071: Verdin AM62 Solo 512MB 0072: Verdin AM62 Solo 512MB WB IT 0073: Verdin AM62 Dual 1GB ET 0074: Verdin AM62 Dual 1GB IT 0075: Verdin AM62 Dual 1GB WB IT 0076: Verdin AM62 Quad 2GB WB IT Signed-off-by:
Marcel Ziswiler <marcel.ziswiler@toradex.com> Signed-off-by:
Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
-
Rework the rather big array of zero length strings with 4 entries of actual display adapter names to a array of structs which ties a pid4 to its correspondent human readable string. Provide an accessor to get the string for a given PID4. Signed-off-by:
Max Krummenacher <max.krummenacher@toradex.com> Signed-off-by:
Andrejs Cainikovs <andrejs.cainikovs@toradex.com>
-