Skip to content

linux: Bump version#616

Open
RevySR wants to merge 3 commits into
openRuyi-Project:mainfrom
RevySR:ruyi/linux
Open

linux: Bump version#616
RevySR wants to merge 3 commits into
openRuyi-Project:mainfrom
RevySR:ruyi/linux

Conversation

@RevySR
Copy link
Copy Markdown
Contributor

@RevySR RevySR commented Jun 4, 2026

Summary

Related Issue

  • Resolves #

Checklist

Assisted-by:

@openruyi-bot openruyi-bot Bot added AI Assistance AI is used to help with portions of code, tests, or documentation. BuildSystem: misc Issue/PR not related to any BuildSystem. Target: Rolling Targeting rolling/current branch. Workflow: Ready For Review Ready for review by anyone with domain expertise. and removed AI Assistance AI is used to help with portions of code, tests, or documentation. labels Jun 4, 2026
@misaka00251 misaka00251 added this to the 2026.06 milestone Jun 4, 2026
@SalimTerryLi
Copy link
Copy Markdown
Contributor

I'd prefer strictly align the version of Linux kernel and its dtb, making no assumptions about the one embedded in the firmware, and always follow the process of dynamic dtb loading and fixup, on platform using fdt.

Requiring a firmware specially constructed for a given kernel implementation makes no difference with those VENDOR solution.

@RevySR
Copy link
Copy Markdown
Contributor Author

RevySR commented Jun 5, 2026

I'd prefer strictly align the version of Linux kernel and its dtb, making no assumptions about the one embedded in the firmware, and always follow the process of dynamic dtb loading and fixup, on platform using fdt.

openRuyi currently supports DTB for all kernels on all supported machines. Incompatibility is a bug.

Requiring a firmware specially constructed for a given kernel implementation makes no difference with those VENDOR solution.

The difference lies in dt-binding of linux, which essentially requires compatibility with the preceding terms; destructive modifications will not be accepted.

@openruyi-bot openruyi-bot Bot added Workflow: In Review Issues that are undergoing code review and/or undergoing design review. and removed Workflow: Ready For Review Ready for review by anyone with domain expertise. labels Jun 5, 2026
@misaka00251 misaka00251 added the Workflow: Blocked Issues that are blocked until another issue has been completed. label Jun 5, 2026
@misaka00251
Copy link
Copy Markdown
Member

misaka00251 commented Jun 5, 2026

The block label was requested by @SalimTerryLi because he believes this topic requires further discussion.

@SalimTerryLi
Copy link
Copy Markdown
Contributor

LGTM

@misaka00251 misaka00251 removed the Workflow: Blocked Issues that are blocked until another issue has been completed. label Jun 5, 2026
@RevySR RevySR added the Workflow: In Dev Issues that are actively being worked on by a developer. label Jun 5, 2026
RevySR added 3 commits June 6, 2026 01:02
Signed-off-by: Han Gao <gaohan@iscas.ac.cn>
Signed-off-by: Han Gao <gaohan@iscas.ac.cn>
Signed-off-by: Han Gao <gaohan@iscas.ac.cn>
@openruyi-bot openruyi-bot Bot removed the Workflow: In Dev Issues that are actively being worked on by a developer. label Jun 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

BuildSystem: misc Issue/PR not related to any BuildSystem. Target: Rolling Targeting rolling/current branch. Workflow: In Review Issues that are undergoing code review and/or undergoing design review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants