On 17.02.24 04:11, Alexander Sverdlin wrote:
> Hello Nishanth,
>
> On Fri, 2023-08-25 at 13:02 -0500, Nishanth Menon wrote:
>> Switch to using bootstd. Note with this change, we will stop using
>> distro_bootcmd and instead depend entirely on bootflow method of
>> starting the system up.
>>
>> Sug
On 2024-02-17 01:22, Jonas Karlman wrote:
> This series contains miscellaneous updates to defconfigs, syncs latest
> device trees from linux, fixes an issue loading FIT from SD-card when
> running SPL from eMMC and enables building a bootable SPI image on
> RK3328 boards.
>
> I am also adding myse
If a device-tree is passed to the bootefi command while using ACPI, we
currently only show a warning that the device-tree will be ignored. But we
use that device-tree to create memory reservations.
To be consistent we need to fallback to the internal device-tree.
Signed-off-by: Heinrich Schuchard
On 2024-02-15 21:52, Caleb Connolly wrote:
> Add support for a vbus-supply regulator specified in devicetree. This
> provides generic support to avoid hardcoded GPIO configuration in board
> init code.
>
> Reviewed-by: Neil Armstrong
> Signed-off-by: Caleb Connolly
> ---
> This patch has no depe
On 2/16/24 3:17 PM, Mark Kettenis wrote:
Date: Fri, 16 Feb 2024 00:38:25 +0100
From: Heinrich Schuchardt
Am 16. Februar 2024 00:25:34 MEZ schrieb Mark Kettenis :
Moving the efi_carve_out_dt_rsv() call in commit 1be415b21b2d
("efi_loader: create memory reservations in ACPI case")
broke boards t
CoolPi 4B is a rk3588s based SBC.
Specification:
- Rockchip RK3588S
- LPDDR4 2/4/8/16 GB
- TF scard slot
- eMMC 8/32/64/128 GB module
- SPI Nor 8MB
- Gigabit ethernet drived by PCIE with RTL8111HS
- HDMI Type D out
- Mini DP out
- USB 2.0 Host x 2
- USB 3.0 OTG x 1
- USB 3.0 Host x 1
- WIFI/BT mod
Cool Pi CM5 EVB works as a mother board connect with CM5.
CM5 Specification:
- Rockchip RK3588
- LPDDR4 2/4/8/16 GB
- TF scard slot
- eMMC 8/32/64/128 GB module
- SPI Nor 8MB
- Gigabit ethernet x 1 with PHY YT8531
- Gigabit ethernet x 1 drived by PCIE with YT6801S
CM5 EVB Specification:
- HDMI Ty
Hi Jan!
On Sat, 2024-02-17 at 09:42 +0100, Jan Kiszka wrote:
> > U-Boot 2024.01 (Feb 15 2024 - 01:43:17 +0100)
> >
> > SoC: AM62X SR1.0 HS-FS
> > Model: Texas Instruments AM625 SK
> > DRAM: 2 GiB
> > Core: 56 devices, 23 uclasses, devicetree: separate
> > MMC: mmc@fa1: 0, mmc@fa0: 1
Pinconfig nodes normally bind recursively with PINCTRL_FULL and
PINCONF_RECURSIVE enabled. However, during U-Boot proper pre-relocation
any node marked with e.g. bootph-all will not bind unless its parent is
also marked for pre-reloc.
group1 {
pinconf1 {
bootph-all;
};
};
Add APIs to set a firmware_name to a rproc and boot the rproc with the
same firmware.
Clients can call rproc_set_firmware() API to set firmware_name for a rproc
whereas rproc_boot() will load the firmware set by rproc_set_firmware() to
a buffer by calling request_firmware_into_buf(). rproc_boot()
FIT checksum validation is very slow in SPL due to D-cache not being
enabled.
Enable caches in SPL on ARM64 SoCs to speed up FIT checksum validation,
from seconds to milliseconds.
This change enables caches in SPL on all Rockchip ARM64 boards, the
Kconfig options SPL_SYS_ICACHE_OFF and SPL_SYS_DC
> From: Jonas Karlman
> Date: Sat, 17 Feb 2024 12:34:04 +
>
> FIT checksum validation is very slow in SPL due to D-cache not being
> enabled.
>
> Enable caches in SPL on ARM64 SoCs to speed up FIT checksum validation,
> from seconds to milliseconds.
>
> This change enables caches in SPL on
During address translation #address/size-cells props are expected to
apply to child nodes. However, devfdt_get_addr_index() incorrectly use
the parent offset of the udevice parent instead of getting the offset of
the node parent. This will work in most cases when there is only one
udevice tied to a
This commit allows user to determine whether to have history recording
in command-line. Previously the history data as uninitialized static
array would not directly take much space in binary file since it only
marks size in the binary. However now it asks to allocate space. By
connecting the origin
This commit allows users to choose the appropriate memory
allocation method between static allocated and dynamically
calloc. The previous static-array way will not obviously
contribute to the final binary size since it is uninitialized,
and might have better performance than the dynamical one.
Now
I am running Arch ARM on a RPi4B and also on a RPi5B. My RPi4B can boot the
vanilla kernel package (linux-aarch64) with the latest uboot-raspberrypi
(2024.04-rc2) just fine. Yet, if I take that uSD card and place it in my RPi5B,
it does not boot. I only see the "U-Boot" submarine logo in the upp
> I am running the NanoPi R6C. The device is not capable of booting from
> the SSD, the next best thing is to load the root filesystem from the SSD.
By booting you mean loading the firmware from SSD (by which I think
you mean NVME right).
> Using rockchip's repos, I compile from source the image
On Sat, 17 Feb 2024 at 16:53, John wrote:
>
> I am running Arch ARM on a RPi4B and also on a RPi5B. My RPi4B can boot the
> vanilla kernel package (linux-aarch64) with the latest uboot-raspberrypi
> (2024.04-rc2) just fine. Yet, if I take that uSD card and place it in my
> RPi5B, it does not bo
This series remove old unused board_early_init_f() functions, adds
support for RK3399 to the IO-domain driver and migrates all boards that
used setup_iodomain() to now use the IO-domain driver instead.
Also add device tree files and myself as reviewer to MAINTAINERS.
This series depends on cleanu
Add myself as a reviewer for RK3399 boards that I have and can help with
review and testing of defconfig and device tree changes.
Signed-off-by: Jonas Karlman
---
board/pine64/pinebook-pro-rk3399/MAINTAINERS | 1 +
board/pine64/rockpro64_rk3399/MAINTAINERS| 1 +
board/rockchip/evb_rk3399/MAI
Update MAINTAINERS files for RK3399 boards to include related device
tree files. Also correct a few filenames.
Signed-off-by: Jonas Karlman
---
board/firefly/roc-pc-rk3399/MAINTAINERS | 5
board/pine64/pinebook-pro-rk3399/MAINTAINERS | 2 +-
board/pine64/pinephone-pro-rk3399/MAINTA
These functions is excluded from SPL build and BOARD_EARLY_INIT_F is not
enabled for any of the affected boards, so this legacy code is not used.
Rockchip common board code already enable all regulators flagged as
always-on or boot-on in device tree, and fixed/gpio regulators now have
basic refere
Move ROCK Pi 4 specific board code from the shared evb_rk3399 target
into its own board target and update related defconfigs to use the new
TARGET_ROCKPI4_RK3399 option.
Also move the call to gpt_capsule_update_setup() from the weak function
rk_board_late_init() into the main board_late_init() fun
Switch to use the IO-domain driver to configure IO-domain based on
device tree instead of a setup_iodomain() function.
Signed-off-by: Jonas Karlman
---
board/pine64/rockpro64_rk3399/Makefile| 7
.../rockpro64_rk3399/rockpro64-rk3399.c | 39 ---
configs/rockpro
Port the RK3399 part of the Rockchip IO-domain driver from linux.
This differs from linux version in that pmu io iodomain bit is enabled
in the write ops instead of in an init ops as in linux, this way we can
avoid keeping a full state of all supply that have been configured.
Signed-off-by: Jonas
Switch to use the IO-domain driver to configure IO-domain based on
device tree instead of a setup_iodomain() function.
Signed-off-by: Jonas Karlman
---
This should be runtime tested by someone with a puma device. All DT
props and driver seem to be enabled and I expect the io_vsel to be
configured
Switch to use the IO-domain driver to configure IO-domain based on
device tree instead of a setup_iodomain() function.
Signed-off-by: Jonas Karlman
---
board/pine64/pinebook-pro-rk3399/Makefile | 1 -
.../pinebook-pro-rk3399/pinebook-pro-rk3399.c | 39 ---
configs/pinebook-p
Switch to use the IO-domain driver to configure IO-domain based on
device tree instead of a setup_iodomain() function.
Signed-off-by: Jonas Karlman
---
This should be runtime tested by someone with a pinephone-pro device.
All DT props and driver seem to be enabled and I expect the io_vsel to
be c
Switch to use the IO-domain driver to configure IO-domain based on
device tree instead of a setup_iodomain() function.
Signed-off-by: Jonas Karlman
---
board/vamrs/rock960_rk3399/Makefile | 6 -
board/vamrs/rock960_rk3399/rock960-rk3399.c | 27 -
configs/ficus-rk
Switch to use the IO-domain driver to configure IO-domain based on
device tree instead of a setup_iodomain() function.
Signed-off-by: Jonas Karlman
---
This should be runtime tested by someone with a gru device. All DT props
and driver seem to be enabled and I expect the io_vsel and soc_con0 to
b
On Saturday, February 17th, 2024 at 1:55 PM, Jojan wrote:
> For RPi 5B you need bcm2712 device tree . RPi4 uses 2711.
> So the e rpi_arm64_confi does not work for RPi5
>
Which config target did you build or did you modify rpi_arm64_config? If so,
can you share the diff? You mentioned modif
Thank you for the steps. If the NIC is non-functional, I think I will wait for
official RPi5B support to come to u-boot.
On Saturday, February 17th, 2024 at 2:25 PM, Jojan wrote:
> yes , I created new config by renaming ' rpi_arm64_config' to
> rpi5_arm64_config.
> and edited the device tr
On Mon, 12 Feb 2024 at 09:37, Dmitry Baryshkov
wrote:
>
> The functions virtio_pci_get_config() and virtio_pci_set_config() don't
> take the offset into account when reading the config space. For example
> this manifests when U-Boot tries to read the MAC address of the VirtIO
> networking device.
For RPi 5B you need bcm2712 device tree . RPi4 uses 2711.So the e
rpi_arm64_confi does not work for RPi5
Also make sure that you have the changes discussed here.[GIT PULL] rpi:
updates for v2024.04 (mail-archive.com)
Iwas able to get the git
(https://source.denx.de/u-boot/custodians/u-boot-ra
yes , I created new config by renaming ' rpi_arm64_config' to
rpi5_arm64_config.and edited the device tree to bcm2712-rpi-5-b.dtb. Then get
get the dts files from
linux/arch/arm/boot/dts/bcm2712-rpi-5-b.dts at rpi-6.1.y
)
It gets booted but still need more controllers( ethernet)
On Satu
You might get these build errorsError:arch/arm/dts/bcm283x-u-boot.dtsi:42.1-14
Label or path uart0_gpio14 not found
Error: arch/arm/dts/bcm283x-u-boot.dtsi:46.1-14 Label or path uart1_gpio14
notfound
I just Just commented out that.
On Saturday, February 17, 2024 at 11:17:12 AM PST, John
Hi John,
Am 17.02.24 um 17:33 schrieb John:
I am running Arch ARM on a RPi4B and also on a RPi5B. My RPi4B can boot the
vanilla kernel package (linux-aarch64) with the latest uboot-raspberrypi
(2024.04-rc2) just fine.
btw the mainline kernel doesn't have any RPi 5 support yet. So you will
nee
The following changes since commit 9e00b6993f724da9699ef12573307afea8c19284:
Merge tag 'u-boot-dfu-20240215' of
https://source.denx.de/u-boot/custodians/u-boot-dfu (2024-02-15 10:26:24 -0500)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-sh.git mast
Hi Quentin,
On 2024/2/9 21:18, Quentin Schulz wrote:
From: Quentin Schulz
The STM32_RST line is routed to the ATtiny microcontroller
PA0/RESET/UPDI pin. By driving the PX30 SoC pin as GPIO output high, we
prevent external UPDI to be used for flashing without first putting this
pin as GPIO input
On Sun, Feb 18, 2024 at 12:34:49AM +0100, Marek Vasut wrote:
> The following changes since commit 9e00b6993f724da9699ef12573307afea8c19284:
>
> Merge tag 'u-boot-dfu-20240215' of
> https://source.denx.de/u-boot/custodians/u-boot-dfu (2024-02-15 10:26:24
> -0500)
>
> are available in the Git
40 matches
Mail list logo
