The T-Firefly ROC-RK3308-CC is a miniature and compact main board which is
equipped with a cost-effective RK3308 Core Processor and a high-performance
CODEC.
Features:
- Rockchip RK3308, 64-bit, quad-core, Arm Cortex-A35 processor @ 1.3GHz
- 100M ethernet
- PoE
- USB 2.0 and Type-C (OTG and
In upstream mainline U-Boot commit 9e13fef00b8d ("rockchip: Kconfig: Enable
external TPL binary for rk3308") U-Boot was changed to incorporate the DDR TPL
using the same mechanism as the RK3568 and RK3588 platforms.
Signed-off-by: Trevor Woerner
---
recipes-bsp/u-boot/u-boot%.bbappend | 10
From: Quanyang Wang
The per cpu variable cpu_number1 is passed to xlnx_event_handler as
argument "dev_id", but is not used in this function. So drop the
initialization of this variable and rename it to dummy_cpu_number.
This patch is to fix the following calltrace when the kernel option
Disable HDMI audio simple-audio-card node as a workaround, since we did not
have the document and not figure out how to set the HDMI audio parameters
for the BBB target board, to avoid below booting error information if
connecting HDMI monitor:
davinci-mcasp.0-i2s-hifi: ASoC: error at
Support TPS65217 voltage regulator driver and TPS65217 Backlight driver.
And enable them by default. This will avoid below booting failed
information:
tps65217-pmic: Failed to locate of_node [id: -1]
tps65217-bl: Failed to locate of_node [id: -1]
Signed-off-by: Xulin Sun
---
From: Quanyang Wang
The per cpu variable cpu_number1 is passed to xlnx_event_handler as
argument "dev_id", but is not used in this function. So drop the
initialization of this variable and rename it to dummy_cpu_number.
This patch is to fix the following calltrace when the kernel option
AKA the "renegade"
The ROC-RK3328-CC platform is built on the Rockchip RK3328 system-on-chip
optimized for low cost, low power, and high performance IO. It features a
high performance native USB 3.0 interface and Gigabit MAC.
Specs:
- RaspberryPi 2/3 form factor
- quad-core ARM Cortex-A53 @
The device-tree for the GbE interface of the rock-pi-e had some properties
in the wrong location. Oddly enough the older rock-pi-e devices with
the Realtek 8211e PHY worked fine, but the latest spin (v1.21) with the
rtl8211f PHY didn't. This fixes allows both PHYs to work.
Signed-off-by: Trevor
The rock-pi-e currently comes in 4 board revisions, the latest of which
(v1.21) replaces the realtek 8211e PHY with the 8211f.
This patch enables networking on the rock-pi-e, which had not been working up
to this point. Interestingly enough, this patch also has the side-effect of
enabling both
The rock-pi-e currently comes in 4 board revisions, the latest of which
(v1.21) replaces the realtek 8211e PHY with the 8211f.
This patch enables networking on the rock-pi-e, which had not been working up
to this point. Interestingly enough, this patch also has the side-effect of
enabling both
Some recipes (gnome-settings-daemon, accountsservice) depend on polkit
DISTRO_FEATURES. Set this up so that we get wider source mirror coverage
and fewer warnings.
Signed-off-by: Yoann Congal
---
config.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/config.json
The rock-pi-e currently comes in 4 board revisions, the latest of which
(v1.21) replaces the realtek 8211e PHY with the 8211f.
This patch enables networking on the rock-pi-e, which had not been working up
to this point. Interestingly enough, this patch also has the side-effect of
enabling both
From: Xiangyu Chen
Hi Bruce,
After using kernel-hardening-checker[1] utils to check current configs, we
picked up some configs from failure case to
feature/security/security.cfg to improve the kernel security.
Following configs no impact on performance but can improve kernel security:
From: Xiangyu Chen
Add some configs to harden protection:
CONFIG_HW_RANDOM_TPM=y Exposing the TPM's Random Number Generator as a hwrng
device.
CONFIG_DEBUG_WX=y Warn on W+X mappings at boot.
CONFIG_SECURITY_DMESG_RESTRICT=y Restrict unprivileged access to the kernel
syslog.
Matt Wood escreveu (segunda, 15/01/2024 à(s)
19:44):
> Hi,
>
> I was wondering if the IMAGE_INSTALL:append syntax could work in
> multiconfig environment from the top-level local.conf file?
>
> For example, I have a meta-layer that defines the muitconfig (main.conf
> and initramfs.conf). From
Hi Bruce,
This is a trial merge of the stable kernel v5.15.147 v6.1.73 for the following
branches in the linux-yocto.
9a246c2e36ad v5.15/standard/sdkv5.10/axxia
c2332b69f732 v5.15/standard/preempt-rt/sdkv5.10/axxia
2e914c1570ee v5.15/standard/base
ae36cbd24fb1
Hello,
I am currently on Yocto Kirkstone. The u-boot version used there is `2022.01`
in the `poky/meta/recipes-bsp/u-boot`:
```
lukasz@vmks:~/beaglenode/beaglenodeos/poky/meta/recipes-bsp/u-boot$ ls
files libubootenv_0.3.2.bb u-boot_2022.01.bb u-boot-common.inc
u-boot-configure.inc
17 matches
Mail list logo
