Skip to content

Add support for lckfb-tspi-3m#3470

Open
FragrantOrchid wants to merge 1 commit intoophub:mainfrom
FragrantOrchid:main
Open

Add support for lckfb-tspi-3m#3470
FragrantOrchid wants to merge 1 commit intoophub:mainfrom
FragrantOrchid:main

Conversation

@FragrantOrchid
Copy link
Copy Markdown

Add support for lckfb-tspi-3m
添加对立创开发板-泰山派-3M的支持,u-boot文件已提交到u-boot仓库
经测试当前仓库使用的kernel无法在此开发板上正常启动,可能是rk3576支持不足,因此将提取的内核放到了different-files下面,又由于rebuild步骤中,添加内核(4/7)位于添加different-files(3/7)后面,因此通过boot.scr指定写死使用的内核文件,后续上游支持充足后再修改。
当前镜像还存在诸多bug,ap6256无法支持,只有有线网可以使用。

@ophub
Copy link
Copy Markdown
Owner

ophub commented Apr 7, 2026

指定写死也没用,因为一更新内核就会删除vmlinuz,不是每个用户都能通知到说不要更新内核,默认内核一直用到老。

rm -f /boot/config-* /boot/initrd.img-* /boot/System.map-* /boot/uInitrd-* /boot/vmlinuz-*

所以必须接近内核适配的问题,最新的6.18测试过吗?f大的rockchip专用bsp内核也不支持吗?
https://github.com/unifreq/linux-6.18.y
https://github.com/unifreq/linux-6.1.y-rockchip

@FragrantOrchid
Copy link
Copy Markdown
Author

FragrantOrchid commented Apr 7, 2026

感谢帮助,经测试,rk35xx下面,f大的rockchip专用内核是可用的,如https://github.com/ophub/kernel/releases/download/kernel_rk35xx/6.1.141-rk35xx-flippy-2603a.tar.gz 经测试可行。抱歉询问一下,model_database.conf文件下的KERNEL_TAGS需要如何写以指定使用rk35xx下面含有flippy的镜像。

@ophub
Copy link
Copy Markdown
Owner

ophub commented Apr 7, 2026

可以参考 r701 :HLink-H28K

r701 :HLink-H28K :rk3528 :rk3528-hlink-h28k.dtb :NA :NA :bootloader.bin :1GB/2GB/4GB-LPDDR4,8G-eMMC,TF,2x1Gb-Nic :rk35xx/6.1.y :rockchip :rk3528 :armbianEnv.txt :unifreq :h28k :yes

9.KERNEL_TAGS
:rk35xx/6.1.y

这个dts你有源码吗?提交到f大的这个内核源码仓库里吧:
https://github.com/unifreq/linux-6.1.y-rockchip/tree/main/arch/arm64/boot/dts/rockchip

@FragrantOrchid
Copy link
Copy Markdown
Author

很抱歉我未能明白,类似r701 :HLink-H28K的:rk35xx/6.1.y写法似乎会匹配到 https://github.com/ophub/kernel/releases/download/kernel_rk35xx/6.1.118.tar.gz ,但是经测试,这个内核无法正常启动,需要rk35xx下的flippy内核 https://github.com/ophub/kernel/releases/download/kernel_rk35xx/6.1.141-rk35xx-flippy-2603a.tar.gz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants