Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RK3588: edge: Bump kernel from v6.11 to v6.12-rc #7372

Closed
wants to merge 20 commits into from

Conversation

ColorfulRhino
Copy link
Collaborator

@ColorfulRhino ColorfulRhino commented Oct 14, 2024

Description

Kernel 6.12 brings several improvements for the Rockchip RK3588, so we can drop some patches as listed below.

Dropped patches (have been upstreamed)

SoC patches:

  • 0026-RK3588-Add-VPU121-H.264-Decoder-Support
  • 0029-arm64-dts-rockchip-rk3588-add-RGA2-node

HDMI patches:

  • 0130-phy-phy-rockchip-samsung-hdptx-Enable-runtime-PM
  • 0131-phy-phy-rockchip-samsung-hdptx-Add-clock-provider
  • 0134-drm-bridge-synopsys-Add-initial-support-for-DW-HDMI-Controller

Board patches:

  • 1051-arm64-dts-rockchip-nanopct6-lts-and-fixes-v6
  • rk3588-nanopc-cm3588-nas.dts (keep compatibility include)

Patches that needed adaption for 6.12

  • 0001-general-add-overlay-support
  • 0024-RK3588-Add-Crypto-Support (asm/unaligned.h moved to linux/unaligned.h)
  • 0025-RK3588-Add-HW-RNG-Support (rename driver file to avoid conflict with new 6.12 driver)

Added patches

To Do

  • Test current patched-in hardware RNG driver against the newly introduced one in 6.12 (only introduced for RK3568, but might also be good for RK3588?)
  • Rewrite kernel patches (after all patches like the RNG or HDMI stuff has been sorted out)

How Has This Been Tested?

Please edit this list if you have successfully tested 6.12 on your board :) Thanks!

  • Build success: ./compile.sh build BOARD=cm3588-nas BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=trixie
  • Board: CM3588-NAS: Boot success without any apparent issues
  • HDMI untested, please comment if you can confirm that HDMI still works

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings
  • Any dependent changes have been merged and published in downstream modules

@ColorfulRhino ColorfulRhino added Discussion Being discussed - Voice your opinions :) Needs review Seeking for review labels Oct 14, 2024
@github-actions github-actions bot added size/large PR with 250 lines or more Hardware Hardware related like kernel, U-Boot, ... Patches Patches related to kernel, U-Boot, ... labels Oct 14, 2024
@efectn
Copy link
Member

efectn commented Oct 14, 2024

Thanks for the PR. I will check HDMI today. I also agree with you that we need to adjust rng patch. I think we can add it as -v2 driver

@ColorfulRhino
Copy link
Collaborator Author

Meta discussion about reviews and security

Unfortunately, all the kernel patches show up as newly created files. This is due to the fact that both current and edge kernel were on the same kernel version 6.11 and when current was switched to 6.11, there was only one patch folder left for both edge and current.
This makes reviewing changes harder. I have tried to make it easier for everyone to review by using atomic commits (e.g. doing one commit where patches are copied without any changes from 6.11) and documenting which patches were dropped and which were changed. Hope this helps at least somewhat :)

However, this is also a security risk. since in theory I could have buried some vulnerability or malware deep into one of the patches (let's be real, probably noone is going to go through all the patches when they're all shown as newly added files instead 😅). If the patch files were simply moved, GitHub would show any changes to the files, making it way more difficult for an attacker to hide something. (example: last RK3588 kernel bump PR)

Can we please agree on some standard procedure so changes are easier to follow in the future?

E.g. Move both edge and current to new versions in the same PR? Or rename the patch folders to include edge or current? (Still looking for an even better solution which can be in two different PRs, please let us know if you have anything in mind).

@ColorfulRhino
Copy link
Collaborator Author

ColorfulRhino commented Oct 14, 2024

Hardware RNG driver evaluation

Tests

/dev/random (software implementation)

CM3588-NAS:

cat /dev/random | rngtest -c 10000
rngtest 2.4
Copyright (c) 2004 by Henrique de Moraes Holschuh
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

rngtest: starting FIPS tests...
rngtest: bits received from input: 200000032
rngtest: FIPS 140-2 successes: 9996
rngtest: FIPS 140-2 failures: 4
rngtest: FIPS 140-2(2001-10-10) Monobit: 0
rngtest: FIPS 140-2(2001-10-10) Poker: 1
rngtest: FIPS 140-2(2001-10-10) Runs: 1
rngtest: FIPS 140-2(2001-10-10) Long run: 2
rngtest: FIPS 140-2(2001-10-10) Continuous run: 0
rngtest: input channel speed: (min=1.863; avg=13.957; max=18.626)Gibits/s
rngtest: FIPS tests speed: (min=41.374; avg=134.771; max=147.856)Mibits/s
rngtest: Program run time: 1432229 microseconds

/dev/hwrng with the patched-in rockchip-rng-rk3588.c driver from patch number 0025

CM3588-NAS:

cat /dev/hwrng | rngtest -c 10000
rngtest 2.4
Copyright (c) 2004 by Henrique de Moraes Holschuh
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

rngtest: starting FIPS tests...
rngtest: bits received from input: 200000032
rngtest: FIPS 140-2 successes: 9994
rngtest: FIPS 140-2 failures: 6
rngtest: FIPS 140-2(2001-10-10) Monobit: 1
rngtest: FIPS 140-2(2001-10-10) Poker: 2
rngtest: FIPS 140-2(2001-10-10) Runs: 2
rngtest: FIPS 140-2(2001-10-10) Long run: 1
rngtest: FIPS 140-2(2001-10-10) Continuous run: 0
rngtest: input channel speed: (min=444.923; avg=23600.774; max=19531250.000)Kibits/s
rngtest: FIPS tests speed: (min=45.521; avg=132.260; max=146.719)Mibits/s
rngtest: Program run time: 9771854 microseconds

/dev/hwrng with the rockchip-rng.c driver that was added to mainline 6.12 only for RK3566

(rng node has to be added to the rk3588-base.dtsi)
Not going to test myself due to prioritizing other issues.

Not able to be tested since RK3588 has a different RNG hardware than RK3568 (@efectn ).

Result comparison and discussion

/dev/hwrng seems slightly worse than /dev/random in entropy quality and much worse in performance.

Option 1) We just leave the driver as-is (but there really is not much use for it since /dev/random is better in performance)

Option 2) We remove the patched-in rockchip-rng-rk3588.c driver from patch number 0025 and wait for a better one from upstream.

What do you think?

@ColorfulRhino ColorfulRhino added the 11 Milestone: Fourth quarter release label Oct 14, 2024
@rpardini
Copy link
Member

Unfortunately, all the kernel patches show up as newly created files

Indeed. I feel your pain. We've tried those bumps every other way by now, and there's always the case where this might happen. If you really, really want to keep the history you can try this - which fools git into thinking the copies are really renames -- but that might or not get flattened out/rebased when it's eventually merged into main.

@efectn
Copy link
Member

efectn commented Oct 17, 2024

Just checked HDMI on Opi5 and it doesn't seem to work. It seems like the HDMI bridge pathces have been removed during rebases. They need to be re-added from https://lore.kernel.org/all/20241016-b4-rk3588-bridge-upstream-v10-0-87ef92a6d14e@collabora.com/

@igorpecovnik igorpecovnik added the Work in progress Unfinished / work in progress label Oct 18, 2024
@ColorfulRhino
Copy link
Collaborator Author

Unfortunately, all the kernel patches show up as newly created files

Indeed. I feel your pain. We've tried those bumps every other way by now, and there's always the case where this might happen. If you really, really want to keep the history you can try this - which fools git into thinking the copies are really renames -- but that might or not get flattened out/rebased when it's eventually merged into main.

Interesting, thanks! I'll have a look at it when I got time. Fooling Git is one thing, but if fooling GitHub is possible, that is to see 😄

@ColorfulRhino
Copy link
Collaborator Author

ColorfulRhino commented Oct 18, 2024

Just checked HDMI on Opi5 and it doesn't seem to work. It seems like the HDMI bridge pathces have been removed during rebases. They need to be re-added from https://lore.kernel.org/all/20241016-b4-rk3588-bridge-upstream-v10-0-87ef92a6d14e@collabora.com/

Thanks for testing! Good to see that there is a very new (2 days old) HDMI patch. I will try to switch to these new patches soon.

Edit: Done. Not tested, but compiles fine.

@ColorfulRhino
Copy link
Collaborator Author

Update: Added commits:

  • rk3588: edge: Add new v10 patch for basic HDMI out support
  • rk3588: edge: Enable new HDMI output driver in kernel config
  • rk3588: edge: Enable kernel config option CONFIG_NETKIT
  • rk3588: edge: Rewrite kernel patches against 6.12-rc3

@efectn
Copy link
Member

efectn commented Oct 18, 2024

Hardware RNG driver evaluation

Tests

/dev/random (software implementation)

CM3588-NAS:

cat /dev/random | rngtest -c 10000
rngtest 2.4
Copyright (c) 2004 by Henrique de Moraes Holschuh
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

rngtest: starting FIPS tests...
rngtest: bits received from input: 200000032
rngtest: FIPS 140-2 successes: 9996
rngtest: FIPS 140-2 failures: 4
rngtest: FIPS 140-2(2001-10-10) Monobit: 0
rngtest: FIPS 140-2(2001-10-10) Poker: 1
rngtest: FIPS 140-2(2001-10-10) Runs: 1
rngtest: FIPS 140-2(2001-10-10) Long run: 2
rngtest: FIPS 140-2(2001-10-10) Continuous run: 0
rngtest: input channel speed: (min=1.863; avg=13.957; max=18.626)Gibits/s
rngtest: FIPS tests speed: (min=41.374; avg=134.771; max=147.856)Mibits/s
rngtest: Program run time: 1432229 microseconds

/dev/hwrng with the patched-in rockchip-rng-rk3588.c driver from patch number 0025

CM3588-NAS:

cat /dev/hwrng | rngtest -c 10000
rngtest 2.4
Copyright (c) 2004 by Henrique de Moraes Holschuh
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

rngtest: starting FIPS tests...
rngtest: bits received from input: 200000032
rngtest: FIPS 140-2 successes: 9994
rngtest: FIPS 140-2 failures: 6
rngtest: FIPS 140-2(2001-10-10) Monobit: 1
rngtest: FIPS 140-2(2001-10-10) Poker: 2
rngtest: FIPS 140-2(2001-10-10) Runs: 2
rngtest: FIPS 140-2(2001-10-10) Long run: 1
rngtest: FIPS 140-2(2001-10-10) Continuous run: 0
rngtest: input channel speed: (min=444.923; avg=23600.774; max=19531250.000)Kibits/s
rngtest: FIPS tests speed: (min=45.521; avg=132.260; max=146.719)Mibits/s
rngtest: Program run time: 9771854 microseconds

/dev/hwrng with the rockchip-rng.c driver that was added to mainline 6.12 only for RK3566

(rng node has to be added to the rk3588-base.dtsi) Not going to test myself due to prioritizing other issues.

Result comparison and discussion

/dev/hwrng seems slightly worse than /dev/random in entropy quality and much worse in performance.

Option 1) We just leave the driver as-is (but there really is not much use for it since /dev/random is better in performance)

Option 2) We remove the patched-in rockchip-rng-rk3588.c driver from patch number 0025 and wait for a better one from upstream.

What do you think?

I don't think we can use upstream rng driver since RK3568 and RK3588 have different RNG IPs. perhaps we can add rk3588 as v1 driver just as how it has been done for vendor driver https://github.com/armbian/linux-rockchip/blob/693a5ea9432443eb4a58eee8a37f3b34501eb21b/drivers/char/hw_random/rockchip-rng.c#L447

@ColorfulRhino
Copy link
Collaborator Author

I don't think we can use upstream rng driver since RK3568 and RK3588 have different RNG IPs. perhaps we can add rk3588 as v1 driver just as how it has been done for vendor driver https://github.com/armbian/linux-rockchip/blob/693a5ea9432443eb4a58eee8a37f3b34501eb21b/drivers/char/hw_random/rockchip-rng.c#L447

Thanks for checking! The driver (patch 0025) has been patched in for at least 3 kernel versions now. But as shown above, using /dev/random is simply superior. Let's not patch-in any stuff that for sure will not be part of mainline 😅 I am of the opinion that less complexity is better as a whole, largely also for maintainability.

The evaluation was more meant to see if the currently used driver is very bad as in should not be used at all (like the driver for RK3566 as seen in one of the links sent in this topic).

Since afaik users have to actively choose to use /dev/hwrng for any given application instead of the usual /dev/random, I honestly doubt that more than a few people are using it (if even). Please correct me if I'm wrong :)

@sfx2000 also seems to be interested in RNG crypto stuff and has posted a nice comment about this topic a while back, see #6781 (comment)

@efectn
Copy link
Member

efectn commented Oct 18, 2024

Yeah i agree with you. Let's remove it for now

@rpardini
Copy link
Member

Cherry picked, built ok. Tested on R6C, most stuff seems to work (HDMI untested).
There's a constant panic and hang on reboot related to rockchip_drm_platform_shutdown, though:

Details
[   78.224471] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000a8
[   78.225245] Mem abort in: DABT (current EL), IL = 32 bits
[   78.226291]   SET = 0, FnVPTW = 0
  78.227289] Data abort info:level 0 translation fault
[   78.227546]   ISV = 0, ISS = 0, ISS2 = 0x00000000
[   78.228027]   CM = 0, WnR = 0, TnD = 0, ess = 0
[   78.228470]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs0
[   78.228938] user pgtable: 4k pages, 48-bit VAs, pgdp=00000800000
[   78.229503] [00000000000000a8] pgd=0000000000000000, p4d=0000000000000000
[   78.230104] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
[   78.230656] Modules linked in: tls cfg80211 rfkill sunrpc binfmt_misc hantro_vpu crct10dif_ce rockchip_vdec2 rockchip_rga v4l2_vp9 at24 v4l2_jpeg rk805_pwrkey v4l2_h264 v4l2_mem2mem videobuf2_dma_sg videobuf2_dma_contig videobuf2_memops rk_crypto2 videobuf2_v4l2 nvmem_rockchip_otp sm3_generic videodev crypto_engine rockchip_rng_rk3588 sm3 videobuf2_common mc ip_tables x_tables autofs4 dm_mod r8169 rk808_regulator phy_rockchip_samsung_hdptx rk8xx_spi rk8xx_core rockchipdrm dw_hdmi_qp dw_mipi_dsi dw_hdmi analogix_dp cec drm_dma_helper panthor drm_gpuvm gpu_sched drm_display_helper drm_shmem_helper drm_exec drm_kms_helper drm adc_keys
[   78.235652] CPU: 1 UID: 0 PID: 1 Comm: systemd-shutdow Not tainted 6.12.0-rc3-edge-rockchip-rk3588 #1
[   78.236459] Hardwre name: FriendlyElec NanoPi R6C (DT)
[   78.236919] pstate: 609 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[   78.237530]pc : drm_atomic_helper_shutdown+0x34/0x140 [drm_kms_helper]
[  78.238126] lr : rockchip_drm_platform_shutdown+0x18/0x28 [rockch
[   78.238734] sp : ffff80008005bba0
[   78.239028] x29: ffff80008005bba0 x28: ffff6872403ab480 x27: 0000000000000000
[   78.239661] x26: 0000000000000008 x25: ffffa9914783b848 x24: ffffa948918048
[   78.240293] x23: ffff687240bc5890 x22: ffffa991489cx21: ffffa99148805430
[   78.240925] x20: ffff687240fd4000 x19:ffff687240bc5818 x18: 0000000000000003
[   78.241558] x17: ffffb2c0 x16: 0000000000000000 x15: ffffa99147609118
[   78.242190]0000000000000b x13: ffff6872402bb210 x12: 0000000000000000
[   42822] x11: 0000000000000040 x10: ffffa99148630158 x9 : ffffa99148630150
[   78.243454] x8 : ffff6872404034a0 x7 : 0000000000000000 x6 : 0000000000000000
[   78.244086] x5 : ffff687240403478 x4 : ffff687240403510 x3 : 0000000000000000
[   78.244717] x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000000
[   78.245349] Call trace:
[   78.245567]  drm_atomic_helper_shutdown+0x34/0x140 [drm_kms_helper]
[   78.246128]  rockchip_drm_platform_shutdown+0x18/0x28 [rockchipdrm]
[   78.246687]  platform_shutdown+0x24/0x34
[   78.247039]  device_shutdown+0x154/0x258
[   78.247389]  kernel_restart+0x40/0xa8
[   78.247718]  __do_sys_reboot+0x1e0/0x26c
[   78.248069]  __arm64_sys_reboot+0x24/0x30
[   78.248426]  invoke_syscall+0x48/0x110
[   78.248763]  el0_svc_common.constprop.0+0x40/0xe8
[   78.249181]  do_el0_svc+0x20/0x2c
[   78.249479]  el0_svc+0x38/0x100
[   78.249762]  el0t_64_sync_handler+0x13c/0x158
[   78.250149]  el0t_64_sync+0x1a4/0x1a8
[   78.250479] Code: b4000554 f90013f5 f9401a80 b9406a81 (b940a800)
[   78.251014] ---[ end trace 0000000000000000 ]---
[   78.251442] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[   78.252185] Kernel Offset: 0x2990c6200000 from 0xffff800080000000
[   78.252720] PHYS_OFFSET: 0xffff978ec0000000
[   78.253089] CPU features: 0x1c,00000017,00280928,4200720b
[   78.253564] Memory Limit: none
[   78.253837] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---

@efectn
Copy link
Member

efectn commented Oct 21, 2024

uhm after install boot on SPI and the system on emmc I got this error panic:

[    4.247441] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[    4.248129] CPU: 4 UID: 0 PID: 1 Comm: run-init Not tainted 6.12.0-rc4-edge-rockchip-rk3588 #1
[    4.248890] Hardware name: FriendlyElec NanoPC-T6 LTS (DT)
[    4.249374] Call trace:
[    4.249592]  dump_backtrace+0x94/0x114
[    4.249932]  show_stack+0x18/0x24
[    4.250228]  dump_stack_lvl+0xc8/0xf4
[    4.250558]  dump_stack+0x18/0x24
[    4.250854]  panic+0x3c0/0x3d4
[    4.251132]  do_exit+0x8a0/0x9c8
[    4.251420]  make_task_dead+0x0/0x188
[    4.251747]  invoke_syscall+0x48/0x110
[    4.252086]  el0_svc_common.constprop.0+0x40/0xe8
[    4.252508]  do_el0_svc+0x20/0x2c
[    4.252808]  el0_svc+0x38/0x100
[    4.253093]  el0t_64_sync_handler+0x13c/0x158
[    4.253483]  el0t_64_sync+0x1a4/0x1a8
[    4.253811] SMP: stopping secondary CPUs
[    4.254247] Kernel Offset: disabled
[    4.254556] CPU features: 0x1c,00000007,00280928,4200720b
[    4.255034] Memory Limit: none
[    4.255311] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 ]---

have you experienced this issue?

I also sometimes get the same kernel panic at SD card

@SuperKali
Copy link
Member

I also sometimes get the same kernel panic at SD card

I'm retrying to rebuild the OS, I'm flashing now the sdcard I will look again.

@SuperKali
Copy link
Member

After rebuilding the OS and reflashed the image on emmc via dd command through the img it works, but this is not normal that some time kernel crashes

@The-going
Copy link
Contributor

@SuperKali Please check the file system on the eMMC partition after booting from the SD card.

@SuperKali
Copy link
Member

@SuperKali Please check the file system on the eMMC partition after booting from the SD card.

Usually I install all on emmc because it's more faster than sd card, but I clean every time the partition.

@The-going
Copy link
Contributor

Usually I install all on emmc because it's more faster than sd card, but I clean every time the partition.

The file system may be disrupted due to the wear and tear of a certain number of memory cells.
You record using the dd command.
That may be the problem.

@SuperKali
Copy link
Member

The file system may be disrupted due to the wear and tear of a certain number of memory cells.
You record using the dd command.
That may be the problem.

Using armbian-install directly not works :(

@SuperKali
Copy link
Member

the system on emmc I got this error panic:

Is the file system on eMMC OK?

Obviously the emmc is ok, I’ve tried vendor kernel and works correctly 🙂

@The-going
Copy link
Contributor

Using armbian-install directly not works

You can state your concerns, comments, or suggestions here

@The-going
Copy link
Contributor

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x412fd050]
[    0.000000] Linux version 6.12.0-rc4-edge-rockchip-rk3588 (build@armbian) (aarch64-linux-gnu-gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #1 SMP PREEMPT Sun Oct 20 22:19:38 UTC 2024
[    0.000000] KASLR enabled
[    0.000000] Machine model: Xunlong Orange Pi 5 Plus

Up 1h:40min, no errors

@SuperKali
Copy link
Member

i have tested nvme boot on nanopc t6 lts and works corrently

@SuperKali
Copy link
Member

image

@SuperKali
Copy link
Member

@ColorfulRhino You managed to run the HDMI port on your boards?

@The-going
Copy link
Contributor

[ 0.000000] Machine model: Xunlong Orange Pi 5 Plus

HDMI is not working

@SuperKali
Copy link
Member

[ 0.000000] Machine model: Xunlong Orange Pi 5 Plus

HDMI is not working

I tried to add the missing nodes for hdmi but I can't figure it out for the nanopc t6 lts, I have no video output

@ColorfulRhino
Copy link
Collaborator Author

ColorfulRhino commented Oct 27, 2024

@ColorfulRhino You managed to run the HDMI port on your boards?

tldr: No and I don't have the time and passion to test and fix HDMI.

Long answer: No. Usually I do not test HDMI or try to get it running. I try to provide upstream patches to keep the HDMI output functionality, but since I do not use HDMI myself and honestly don't care much about it, I won't spend time and energy towards that. It's always better to let someone work on a topic they have a passion for or have other incentives for 😄 Anyone is welcome to add to this PR, my only request is to at least try to keep the high quality I'm trying to maintain (code/patches/commit messages/atomic commit style) when adding commits. I'll gladly help by providing guides and links on how to do this :)


On getting HDMI working: I guess there is probably only one patch either missing or one of our older patches is too much/breaks the new HDMI series.
Nevertheless, this is the struggle of maintaining a kernel with many patches 😆

@The-going
Copy link
Contributor

I'll gladly help by providing guides and links on how to do this

I have always been interested in exactly how such files are obtained in a simple way.
Or even worse, this file.
And what is the easiest way to keep such files up-to-date when migrating to a new version?

@amazingfate
Copy link
Contributor

@amazingfate
Copy link
Contributor

Tested with rock5b, it boots fine.
This pr does not include #7429, so the deocder is detected 1080p in chromium. But never mind, we can add it back after merge because rockchip64 is also bumping to 6.12 and rockchip64-6.11 is deleted.

@amazingfate
Copy link
Contributor

And one comment: why not delete old rockchip-rk3588-6.11 so in git we can see the changes more clearly.

@efectn
Copy link
Member

efectn commented Nov 8, 2024

Tested with rock5b, it boots fine. This pr does not include #7429, so the deocder is detected 1080p in chromium. But never mind, we can add it back after merge because rockchip64 is also bumping to 6.12 and rockchip64-6.11 is deleted.

Is HDMI working properly? By the time i tested 6.12, it hadn't been working. I can test it again if it works

@amazingfate
Copy link
Contributor

Tested with rock5b, it boots fine. This pr does not include #7429, so the deocder is detected 1080p in chromium. But never mind, we can add it back after merge because rockchip64 is also bumping to 6.12 and rockchip64-6.11 is deleted.

Is HDMI working properly? By the time i tested 6.12, it hadn't been working. I can test it again if it works

HDMI is working, I'm testing with a 1080p monitor.

# Verisilicon media platform drivers
#
CONFIG_VIDEO_HANTRO=m
CONFIG_VIDEO_HANTRO_HEVC_RFC=y
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not necessary for rockchip.

@ColorfulRhino
Copy link
Collaborator Author

And one comment: why not delete old rockchip-rk3588-6.11 so in git we can see the changes more clearly.

The idea of current was to provide a stable kernel, while edge usually gets bumped to rc kernels. This PR is already a month old, in the past the RK3588 PRs were much faster, in such a way that we often had rk3588-6.xx-rc3 in Armbian.

IMO, current as a stable kernel should not be bumped to 6.12 until 6.12 is listed as stable at kernel.org

@ColorfulRhino
Copy link
Collaborator Author

I have always been interested in exactly how such files are obtained in a simple way. Or even worse, this file. And what is the easiest way to keep such files up-to-date when migrating to a new version?

Editing patches directly is always difficult. But usually these patches are taken from another GitHub repository (one patch = one commit) or from the kernel mailing list. If we have a patch-set (multiple patches in a single file) and want to update a single patch, we can download the patch from the kernel mailing list or from patchwork (https://patchwork.kernel.org/) and copy-paste it inside the file, replacing the old patch. You may need to modify the line From: ...... After that is done, we should run ./compile.sh rewrite-kernel-patches ....... to put the patch in the correct Armbian format.
See also this comment/instruction #7078 (comment)

For example, the patch series you linked can be downloaded from https://patchwork.kernel.org/project/linux-rockchip/cover/20241108185212.198603-1-detlev.casanova@collabora.com/ (either as single patch or as patch series), but you need to modify all From: lines (there is one per patch, so in this case three lines since there are three patches in the series)

@SuperKali
Copy link
Member

We can close this PR as #7455 as been merged

@SuperKali SuperKali closed this Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
11 Milestone: Fourth quarter release Discussion Being discussed - Voice your opinions :) Hardware Hardware related like kernel, U-Boot, ... Needs review Seeking for review Patches Patches related to kernel, U-Boot, ... size/large PR with 250 lines or more Work in progress Unfinished / work in progress
Development

Successfully merging this pull request may close these issues.

7 participants