From: Sinthu Raja
Enable configs for building multiple dtbs into a single fit image
and load the right dtb for next stage. Add k3-am68-sk-base-board
dtb along with evm dtb inside DTB FIT image. This helps to use same
defconfig for both EVM and SK
Signed-off-by: Sinthu Raja
---
configs/j721s2_e
From: Sinthu Raja
Enable configs for building multiple dtbs into a single fit image
and load the right dtb for next stage. This will help to use same
defconfig for both EVM and SK.
Signed-off-by: Sinthu Raja
---
configs/j721s2_evm_r5_defconfig | 3 +++
1 file changed, 3 insertions(+)
diff --g
From: Sinthu Raja
Hi All,
This series of patch add initial support for AM68 starter kit.
Design files can be referrred from https://www.ti.com/lit/zip/SPRR463
Refer below link to J721S2/AM68 Technical Reference Manual for further details:
http://www.ti.com/lit/pdf/spruj28
Link to kerenl patches
From: Sinthu Raja
J721S2 EVM used to store env on eMMC, since EVM and SK uses same
defconfig and there is no eMMC on SK, we need to keep env in an
interface which available on both EVM and SK. So, save env in FAT
partition of MMC SD Card.
Enable defconfigs relevant for storing env on FAT partiti
From: Sinthu Raja
Update setup_board_eeprom_env() to choose the right board name
for am68-sk.
Signed-off-by: Sinthu Raja
Reviewed-by: Tom Rini
---
board/ti/j721s2/evm.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/board/ti/j721s2/evm.c b/board/ti/j721s2/ev
From: Sinthu Raja
J721S2 EVM has EEPROM populated at 0x50. AM68 SK has EEPROM populated at
next address 0x51 in order to be compatible with RPi. So start looking
for TI specific EEPROM at 0x50, if not found look for EEPROM at 0x51.
Signed-off-by: Sinthu Raja
Reviewed-by: Tom Rini
---
board/ti
From: Sinthu Raja
Update the board_fit_config_name_match() to choose the right dtb
based on the board name read from EEPROM.
Also restrict multpile EEPROM reads by verifying if EEPROM is already
read
Signed-off-by: Sinthu Raja
Reviewed-by: Tom Rini
---
board/ti/j721s2/evm.c | 30
From: Sinthu Raja
Although the board_init_f API initialises the SoC, the API name is
incorrectly specified and misleads the functionality. This file should
only include k3-specific functionality. Change the API's name to something
more K3-specific and separate the function to make it more modular
From: Sinthu Raja
Add the board_init_f API for SPL and run the platform-required SoC
initialization.
Add the functionality for board name-based DTB selection from FIT
within SPL. This will make it easier to utilise one defconfig for
both the EVM and the SK.
Signed-off-by: Sinthu Raja
---
Chan
From: Sinthu Raja
AM68 Starter Kit (SK) is a low cost, small form factor board designed
for TI’s AM68 SoC. TI’s AM68 SoC comprises of dual core A72, high
performance vision accelerators, hardware accelerators, latest C71x
DSP, high bandwidth real-time IPs for capture and display. The SoC is
power
From: Sinthu Raja
The SK architecture comprises of baseboard and a SOM board. The
AM68 Starter Kit's baseboard contains most of the actual connectors,
power supply etc. The System on Module (SoM) is plugged on to the base
board. Therefore, add support for peripherals brought out in the base
board
From: Sinthu Raja
Add initial support for AM68 SK device tree that runs on R5.
Signed-off-by: Sinthu Raja
---
arch/arm/dts/Makefile | 1 +
arch/arm/dts/k3-am68-sk-r5-base-board.dts | 194 ++
2 files changed, 195 insertions(+)
create mode 100644 arch/a
From: Sinthu Raja
Now that single defconfig shall be used for booting J721S2 EVM and
AM68 SK, the default device tree will not work for selecting dtb for
kernel. Update the findfdt env to select right dtb based on
board_name env variable.
Signed-off-by: Sinthu Raja
Reviewed-by: Tom Rini
---
i
On Tue, Dec 27, 2022 at 5:46 PM Sinthu Raja
wrote:
>
> From: Sinthu Raja
>
> AM68 Starter Kit (SK) is a low cost, small form factor board designed
> for TI’s AM68 SoC. TI’s AM68 SoC comprises of dual core A72, high
> performance vision accelerators, hardware accelerators, latest C71x
> DSP, high
Modern mobile phones typically have high pixel density.
Bootmenu is hardly readable on those with 8x16 font.
Add 16x32 ter font from linux, and allow font size configuration.
Set 16x32 font for starqltechn board.
Signed-off-by: Dzmitry Sankouski
---
configs/starqltechn_defconfig |1 +
drive
Hi Kojima-san
Overall I think the cleanup is nice and easier to maintain in the long
run.
On Sat, Dec 24, 2022 at 07:57:42AM +0900, Masahisa Kojima wrote:
> Current change boot order implementation does not call
> eficonfig_process_common() and call own menu functions
> for display_statusline, i
Signed-off-by: Brandon Maier
---
test/Kconfig | 2 +-
test/compression.c | 71 ++
2 files changed, 72 insertions(+), 1 deletion(-)
diff --git a/test/Kconfig b/test/Kconfig
index a6b463e4d06..dd2f082ce63 100644
--- a/test/Kconfig
+++ b/test/Kconf
This looks correct to me.
Heinrich can you check if that solves your scrolling issues?
On Sat, Dec 24, 2022 at 07:57:44AM +0900, Masahisa Kojima wrote:
> The current eficonfig menu does not support vertical scroll,
> so it can not display the menu entries greater than
> the console row size.
>
>
On Sat, Dec 24, 2022 at 07:57:43AM +0900, Masahisa Kojima wrote:
> This commit removes the change boot order specific
> menu implementation. The change boot order implementation
> calls eficonfig_process_common() same as other menus.
>
> The change boot order menu requires own item_data_print
> and
On Tue, Dec 27, 2022 at 10:19:37AM +0900, Jaehoon Chung wrote:
> Dear Tom,
>
> Please pull u-boot-pmic master into u-boot master branch.
> If there is a problem, let me know, plz
>
> Best Regards,
> Jaehoon Chung
>
> CI: https://source.denx.de/u-boot/custodians/u-boot-pmic/-/pipelines/14522
>
On 12/27/22 09:46, Brandon Maier wrote:
> +static const unsigned long zstd_compressed_size = 197;
You can use ARRAY_SIZE (or sizeof) for this.
--Sean
The rockchip job is getting close to the hard time limit in Azure for
the free tier. Split this in to 32bit and 64bit board jobs.
Signed-off-by: Tom Rini
---
.azure-pipelines.yml | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/.azure-pipelines.yml b/.azure-pipelines.yml
Hi,
> Da: U-Boot Per conto di Sean Anderson
> Inviato: venerdì 23 dicembre 2022 00:06
>
> On 11/18/22 15:50, Simon Glass wrote:
> > Hi Sean,
> >
> > On Thu, 13 Oct 2022 at 09:41, Sean Anderson
> > wrote:
> >>
> >>
> >>
> >> On 10/13/22 3:14 AM, Rasmus Villemoes wrote:
> >> > On 12/10/2022 18.28
Hi Sean,
> From: Sean Anderson
> On 12/27/22 09:46, Brandon Maier wrote:
> > +static const unsigned long zstd_compressed_size = 197;
>
> You can use ARRAY_SIZE (or sizeof) for this.
sizeof() - 1 as it's a string, but I had put the size here manually as that's
what all the other tests do. I ca
It was temporary disabled due to problem with boot.
Issue was fixed in
commit f5ed6c9ccf3e ("uart: sdm845: Fix debug UART pinmux")
Signed-off-by: Dzmitry Sankouski
---
configs/starqltechn_defconfig | 4 ++--
include/configs/sdm845.h | 5 +++--
2 files changed, 5 insertions(+), 4 deletions(-
KASLR address is needed to boot fully functional Android.
KASLR is set by primary bootloader, and since u-boot is used
as a secondary bootloader(replacing kernel) on sdm845 platform,
KASLR may be found by comparing memory chunks at relocaddr over
supposed KASLR range.
Signed-off-by: Dzmitry Sankou
On 12/22/22 01:21, Rick Chen wrote:
> When fit image boots from ram, the payload will
> be prepared in the address of SPL_LOAD_FIT_ADDRESS.
> In spl fit generic flow, it will malloc another
> memory address and copy whole fit image to this
> malloc address. But it is un-necessary for booting
> fro
Hi Samuel,
Samuel Holland 於 2022年12月28日 週三 上午10:47寫道:
>
> On 12/22/22 01:21, Rick Chen wrote:
> > When fit image boots from ram, the payload will
> > be prepared in the address of SPL_LOAD_FIT_ADDRESS.
> > In spl fit generic flow, it will malloc another
> > memory address and copy whole fit image
On 12/27/22 21:22, Rick Chen wrote:
> Hi Samuel,
>
> Samuel Holland 於 2022年12月28日 週三 上午10:47寫道:
>>
>> On 12/22/22 01:21, Rick Chen wrote:
>>> When fit image boots from ram, the payload will
>>> be prepared in the address of SPL_LOAD_FIT_ADDRESS.
>>> In spl fit generic flow, it will malloc another
> On 12/27/22 21:22, Rick Chen wrote:
> > Hi Samuel,
> >
> > Samuel Holland 於 2022年12月28日 週三 上午10:47寫道:
> >>
> >> On 12/22/22 01:21, Rick Chen wrote:
> >>> When fit image boots from ram, the payload will
> >>> be prepared in the address of SPL_LOAD_FIT_ADDRESS.
> >>> In spl fit generic flow, it wi
On 2022/12/26 21:54, Bin Meng wrote:
> On Mon, Dec 26, 2022 at 3:32 PM yanhong wang
> wrote:
>>
>>
>>
>> On 2022/12/22 17:22, Bin Meng wrote:
>> > On Mon, Dec 12, 2022 at 10:51 AM Yanhong Wang
>> > wrote:
>> >>
>> >> Add StarFive JH7110 SoC to support RISC-V arch.
>> >>
>> >> Signed-off-by: Ya
31 matches
Mail list logo