[U-Boot] [PATCH] arm: mvebu: ClearFog: document boot selection switches, update UART

Signed-off-by: Florian Klink <flo...@flokli.de> --- board/solidrun/clearfog/README | 21 + 1 file changed, 17 insertions(+), 4 deletions(-) diff --git a/board/solidrun/clearfog/README b/board/solidrun/clearfog/README index ef1e3bf426..a7bc0d4e23 100644 --- a/board/so

[U-Boot] arm: mvebu: ClearFog: booting u-boot from ssd?

Hey, I tried getting ClearFog to load u-boot from a M.2 SSD (via SATA) So I built u-boot-spl.kwb make clearfog_defconfig make -j4 ARCH=arm CROSS_COMPILE=arm-none-eabi- dd'ed it on the SSD: dd if=u-boot-spl.kwb of=/dev/sdX bs=512 seek=1 changed SW1 dip to 11100, and got this: BootROM -

Re: [U-Boot] arm: mvebu: ClearFog: booting u-boot from ssd?

Hey Stefan, According to the clearfog wiki and uboot-armada38x src tree, there are separate images for sd and sata, with the makefile there calling $(obj)tools/marvell/doimage -T mmc -D 0x0 -E 0x0 -G $(obj)tools/marvell/bin_hdr/bin_hdr.bin u-boot.bin u-boot.mmc vs $(obj)tools/marvell/doimage

[PATCH] ARM: dts: xilinx: Fix I2C and SPI bus warnings

Ported over from https://patchwork.kernel.org/patch/10599941/ Signed-off-by: Florian Klink --- arch/arm/dts/zynq-zc702.dts | 12 ++-- arch/arm/dts/zynq-zc770-xm010.dts | 2 +- arch/arm/dts/zynq-zc770-xm013.dts | 2 +- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git

Setting DEVICE_TREE for xilinx_zynq_virt_defconfig?

Hey, I tried building latest master 2b8692bac1e8795cbb87b0d00213fd193409851d, for a zynq device, and did according to the documentation: $ export DEVICE_TREE=zynq-zc702 $ make xilinx_zynq_virt_defconfig $ make Reading f7c6ee7fe7bcc387de4c92300f46cb725b845b53, I assumed this should have fixed

Re: Setting DEVICE_TREE for xilinx_zynq_virt_defconfig?

On 20-12-27 17:48:51, Florian Klink wrote: On 20-06-22 14:12:59, Michal Simek wrote: I tried building latest master 2b8692bac1e8795cbb87b0d00213fd193409851d, for a zynq device, and did according to the documentation: $ export DEVICE_TREE=zynq-zc702 $ make xilinx_zynq_virt_defconfig $ make

[PATCH] dts: Log name of expected .dtb file

-boot didn't like not being able to find the .dtb file that should have been produced. Simply logging the expected .dtb file name should make it easier to spot such mistakes. Signed-off-by: Florian Klink --- dts/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dts

[PATCH 1/2] ARM: zynq: add Digilent Zynq PYNQ Board(s)

, so the DTB is the same. Co-authored-by: Thomas Heijligen Signed-off-by: Florian Klink Signed-off-by: Thomas Heijligen --- arch/arm/dts/Makefile | 1 + arch/arm/dts/zynq-pynq.dts | 68 ++ configs/xilinx_zynq_virt_defconfig | 2 +- 3 files

Re: Setting DEVICE_TREE for xilinx_zynq_virt_defconfig?

On 20-06-22 14:12:59, Michal Simek wrote: Hi, On 20. 06. 20 20:06, Florian Klink wrote: Hey, I tried building latest master 2b8692bac1e8795cbb87b0d00213fd193409851d, for a zynq device, and did according to the documentation: $ export DEVICE_TREE=zynq-zc702 $ make xilinx_zynq_virt_defconfig

Re: [PATCH] rk3399: Add basic support for helios64

to point to an issue with the dmc frequency. I've compiled an excerpt of interesting looking logs from a couple of boots here (you should be able to comment on the doc as well): https://hackmd.io/@lorbus/SyXTj0lXu Please take a look and let me know what you think. Best regards, Christian -- Florian

Re: [PATCH v2] board: rockchip: Add the Turing RK1 SoM

Hey Sam, On 24-04-11 16:35:57, Sam Edwards wrote: On Thu, Apr 11, 2024 at 1:29 AM Florian Klink wrote: On 23-12-14 18:46:47, Joshua Riek wrote: >The Turing RK1 is a Rockchip RK3588 based SoM from Turing Machines. > >Specifications: > >Rockchip RK3588 SoC >4x ARM

Re: [PATCH v2] board: rockchip: Add the Turing RK1 SoM

On 23-12-14 18:46:47, Joshua Riek wrote: The Turing RK1 is a Rockchip RK3588 based SoM from Turing Machines. Specifications: Rockchip RK3588 SoC 4x ARM Cortex-A76, 4x ARM Cortex-A55 8/16/32GB memory LPDDR4x Mali G610MC4 GPU 32GB eMMC HS400 2x USB 2.0, 2x USB 3.0 2x MIPI