u-boot.git/common, branch v2024.07-rc3

Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet""

2024-05-19T14:16:36Z

When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman Signed-off-by: Tom Rini

global: Make include

2024-05-06T21:07:48Z

This follows the example of RISC-V where includes directly as "gd" includes a reference to bd_info already and so the first must include the second anyhow. We then remove from all of the places which include references to "gd" an so have already. Signed-off-by: Tom Rini

common: Remove and add needed includes

2024-05-06T21:05:04Z

Remove from all "commmon/" files and when needed add missing include files directly. Signed-off-by: Tom Rini

rockchip: Enable preconsole for rk3328

2024-04-21T07:07:00Z

Enable and set the start address of pre-console buffer for RK3328. Signed-off-by: Jagan Teki

Merge https://source.denx.de/u-boot/custodians/u-boot-usb

2024-04-14T21:58:31Z

Merge patch series "mcheck implementation for U-Boot"

2024-04-12T22:23:19Z

Eugene Uriev says: There was no "mcheck" for U-Boot before. Since U-Boot has only 1 thread, and normally makes 4000+ - 6000+ mallocs, it's better to use havier canaries to protect heap-chunks. My variant uses 2x8 = 16byte-long protector. And the multiplier could be changed to tune speed/protection tradeoff. This protects not only against memset()-s, but against "near" wild pointers too, and makes more probable to catch "distant" ones. The core file of the set is included into the C-file, not complied separately in order to enable (potential) coexisting of mcheck-protectors, e.g. malloc_simple(.) and dlmalloc simultaneously. My tests were for ARM SoC, 64bit, so the patch is aware of alignment. Primary this patch is for using by developers: to verify, if a change doesn't break the heap integrity. By default the mcheck is disabled and wouldn't affect the boot. I used pedantic mode, canary=16byte, registry-size=6608. For my system the overhead was 230ms.

mcheck: let mcheck_abortfunc_t print the pointer

2024-04-12T22:23:06Z

Signed-off-by: Eugene Uriev

mcheck: add stats, add a comment with test results

2024-04-12T22:23:06Z

My tests have been run on an U-Boot (of older version) for ARM (64bits). Signed-off-by: Eugene Uriev

mcheck: introduce mcheck_on_ramrelocation(.)

2024-04-12T22:23:06Z

The using of pre-reloc/malloc_simple heap is too hard to follow after the relocation. So lets drop it from the pedantic registry and switch to dlmalloc, when moved. The offset is ignored, but kept in the API for the probable case, when that early heap is relocated too. Signed-off-by: Eugene Uriev

mcheck: add pedantic mode support

2024-04-12T22:23:06Z

The pedantic mode is run-time contolled, so appropriate registry take place everytime. Maybe it's worth to use compile-time control only. So, the registry could be optimized out by an #ifdef. Signed-off-by: Eugene Uriev