开云体育

From: Neil Armstrong <neil.armstrong@...> Hi, Thanks, Applied to https://source.denx.de/u-boot/custodians/u-boot-amlogic (u-boot-amlogic-next) [1/3] arm: meson: unify type being used for

Hi, sorry, but i don't see it merged. Is it ok? Thanks

The Amlogic Meson SoC secure monitor (TF-A) handles a call (0x82000044) to retrieve a chip_id from eFuse OTP data [1]. Previously, this sm call (0x82000044) was used to retrieve just unique SoC

socinfo_ API uses u32 type, hence let's use it everywhere for consistency. Signed-off-by: Evgeny Bachinin <EABachinin@...> --- arch/arm/mach-meson/board-info.c | 9 +++++---- 1 file

SM_CHIP_ID_SIZE is used nowhere. Moreover, it specifies wrong chip_id size: Amlogic chip_id v1 and v2 is always 16 bytes long. Signed-off-by: Evgeny Bachinin <EABachinin@...> ---

Patch introduces: * chip_id API - useful for various things, but used now for device_id (did) generation as mentioned in [1] on our private board code. Our device_id is calculated by means of

Hi! 10/02/2025 20.50, Evgeny Bachinin wrote:

Superseed by https://lore.kernel.org/u-boot/20250210-meson_chip_id_all_vers-v1-0-b98f8b6880b8@.../ 17/01/2025 13.41, Viacheslav Bocharov wrote:

This is now in master. -- Tom

Hi Tom, Glad to see DT subtree resync, it has been smooth up-revs then what I had expected initially when we introduced it. -Sumit

8531b4b4988c Merge tag 'v6.13-rc7-dts-raw' [snip] git-subtree-dir: dts/upstream git-subtree-split: 8531b4b4988c2c9bddc90ea74f2d3e2dca9d5056 --- This will bring us to the v6.13-dts tag of the

From: Nikita Maslo <nam@...> The Amlogic Meson SoC Secure Monitor implements a call to retrieve an unique SoC ID starting from the GX Family and all new families. But GX-family chips (e.g.

The previous instructions resulted in a bootloader that wouldn't fit in an MBR gap. I have updated the docs based on upstream's build process. Signed-off-by: Baltazár Radics

On 10/01/2025 12:11, Baltazár Radics wrote: > The previous instructions resulted in a bootloader that wouldn't fit in > an MBR gap. I have updated the docs based on upstream's build process. >

Please disregard this patch. I’ve spotted the issue in our distro packaging and this is not required. Apologies for the noise. CH.

Commit 834e7c8136c6 ("dts: meson-g12a: Switch to using upstream DT") changed Amlogic configs to contain the default /amlogic device-tree path prefix, e.g. for

On Mon, Jan 06, 2025 at 10:27:39AM +0100, Neil Armstrong wrote: [snip] > > Reviewed-by: Neil Armstrong <neil.armstrong@...> > > Via which tree this should be merged ? Your amlogic tree when

On 03/01/2025 22:58, Jonas Karlman wrote: > GXBB BL1 only tries to read boot image from sector 0 on eMMC and sector > 1 on SD-card. GXL and newer read boot image from sector 1 on both eMMC > and

On 03/01/2025 22:58, Jonas Karlman wrote: > Add support for creating an Amlogic Boot Image that pass CHK in BL1 on > Amlogic AArch64 SoCs. > Images can optionally be signed for secure boot scenario,

On 05/01/2025 11:24, Ferass El Hafidi wrote: > Hi Jonas and Simon, > On Sat Jan 4, 2025 at 10:23 PM UTC, Jonas Karlman wrote: >> Hi Simon, >> >> On 2025-01-04 20:31, Simon Glass wrote: >>> Hi