Skip to content

sunxi: bump edge to 6.19 #9381

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.

Sign up for GitHub

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

Jump to bottom
Open
EvilOlaf wants to merge 14 commits into
base: main
Choose a base branch
from
Open

sunxi: bump edge to 6.19 #9381

EvilOlaf wants to merge 14 commits into from
+93,918 −17

Conversation

@EvilOlaf
Copy link
Member

@EvilOlaf EvilOlaf commented Feb 9, 2026 •
edited
Loading

Description

  • groundhog day
  • re-extract the full patchset from megi
  • update sun4i-drm-refactor patchset from jernejsk
  • remove most backport stuff
  • adjust a few broken patches
  • disabled two fairly recently added once for fixing
    • This will affect sun55i (opi4a/cubie-a5e) as pcie is borked
  • rewrite everything (at some point in-between lol)

This shall be tested on as many boards as possible so we can shift current to legacy and edge to current.
Orangepi Zero 2: https://paste.armbian.com/udoforonih

How Has This Been Tested?

  • build sunxi
  • build sunxi64

Checklist:

Please delete options that are not relevant.

  • 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 (too many to count in compilation)
  • Any dependent changes have been merged and published in downstream modules

EvilOlaf added 13 commits February 9, 2026 15:09
@EvilOlaf
copy old patchset
d14ed61
@EvilOlaf
bump to 6.19
21f707d
@EvilOlaf
megous: replace 6.18 with 6.19 patchset
160724b
@EvilOlaf
drm-sun4i: remove upstreamed patch series
d05b78f
@EvilOlaf
backports: remove fully upstreamed patches
8fcb9b7
@EvilOlaf
uwe5622: fix patch for 6.19
1151e1d
@EvilOlaf
megi: remove informational patch, confuses patching logic for unknown…
5f83c1c 
… reason
@EvilOlaf
megi: disable unneeded patch (again)
2f5fb0a
@EvilOlaf
fix various broken patches
24d5aef
@EvilOlaf
sunxi: rewrite the whole patchset
8d0c3dd
@EvilOlaf
sun4i-drm: add patches not upstreamed yet from recent series
eaafe1b
@EvilOlaf
disable broken patch @rvdr
8a326f4 
```
[🔨]   drivers/pci/pcie-sunxi/pcie-sunxi-rc.c: In function 'sunxi_allocate_msi_domains':
[🔨]   drivers/pci/pcie-sunxi/pcie-sunxi-rc.c:198:26: error: implicit declaration of function 'pci_msi_create_irq_domain'; did you mean 'msi_create_irq_domain'? [-Werror=implicit-function-declaration]
[🔨]     198 |         pp->msi_domain = pci_msi_create_irq_domain(fwnode, &sunxi_msi_info, pp->irq_domain);
[🔨]         |                          ^~~~~~~~~~~~~~~~~~~~~~~~~
[🔨]         |                          msi_create_irq_domain
```
@EvilOlaf
same story, disable broken patch
8f5143b 
```
[🔨]   drivers/iommu/sun55i-iommu.c: In function 'sunxi_iommu_profilling_show':
[🔨]   drivers/iommu/sun55i-iommu.c:1110:1: warning: label 'err' defined but not used [-Wunused-label]
[🔨]    1110 | err:
[🔨]         | ^~~
[🔨]   drivers/iommu/sun55i-iommu.c: At top level:
[🔨]   drivers/iommu/sun55i-iommu.c:1379:43: error: initialization of 'int (*)(struct iommu_domain *, struct device *, struct iommu_domain *)' from incompatible pointer type 'int (*)(struct iommu_domain *, struct device *)' [-Werror=incompatible-pointer-types]
[🔨]    1379 |                 .attach_dev             = sun55i_iommu_attach_dev,
[🔨]         |                                           ^~~~~~~~~~~~~~~~~~~~~~~
[🔨]   drivers/iommu/sun55i-iommu.c:1379:43: note: (near initialization for '(anonymous).attach_dev')
```
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 9, 2026 •
edited
Loading

Important

Review skipped

Too many files!

This PR contains 300 files, which is 150 over the limit of 150.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions bot added size/large PR with 250 lines or more 02 Milestone: First quarter release Needs review Seeking for review labels Feb 9, 2026
@github-actions github-actions bot added Hardware Hardware related like kernel, U-Boot, ... Patches Patches related to kernel, U-Boot, ... labels Feb 9, 2026
@EvilOlaf EvilOlaf added 05 Milestone: Second quarter release and removed 02 Milestone: First quarter release labels Feb 9, 2026
@EvilOlaf
Copy link
Member Author

EvilOlaf commented Feb 10, 2026

@rvdr I had to disable two of your patches since they fail to build in 6.19. Please check if they're still necessary or send a fix.

@EvilOlaf
Copy link
Member Author

EvilOlaf commented Feb 11, 2026

@igorpecovnik could we produce some test images from via ci to make barrier for testing lower?

@igorpecovnik
Copy link
Member

igorpecovnik commented Feb 11, 2026

could we produce some test images from via ci to make barrier for testing lower?

We can generate all nightly / community images from branches that are at build repository. Second problem is that we don't have edge branches enabled at build lists. Its some work to prepare this, but its duable.

@EvilOlaf
Copy link
Member Author

EvilOlaf commented Feb 11, 2026 •
edited
Loading

Second problem is that we don't have edge branches enabled at build lists. Its some work to prepare this, but its duable.

Well we'll have the same issue in a few month again with 7.0 and further... :)
I mean just the most common or probably one board per family which is the most common, like OPi zero 2 for H616, Opi zero 3 for H618, Opi1+ for H6, one for H5, Opi zero for H2+, perhaps one H3 like nanopi neo. Not sure about even older ones.

@igorpecovnik
Copy link
Member

igorpecovnik commented Feb 11, 2026

I'll try to figure out something.

@EvilOlaf EvilOlaf mentioned this pull request Feb 11, 2026
Open
6 tasks
@github-actions github-actions bot added the 02 Milestone: First quarter release label Feb 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@AGM1968 AGM1968 Awaiting requested review from AGM1968 AGM1968 is a code owner

@JohnTheCoolingFan JohnTheCoolingFan Awaiting requested review from JohnTheCoolingFan JohnTheCoolingFan is a code owner

@PanderMusubi PanderMusubi Awaiting requested review from PanderMusubi PanderMusubi is a code owner

@TheSnowfield TheSnowfield Awaiting requested review from TheSnowfield TheSnowfield is a code owner

@Tonymac32 Tonymac32 Awaiting requested review from Tonymac32 Tonymac32 is a code owner

@chraac chraac Awaiting requested review from chraac chraac is a code owner

@igorpecovnik igorpecovnik Awaiting requested review from igorpecovnik igorpecovnik is a code owner

@janprunk janprunk Awaiting requested review from janprunk janprunk is a code owner

@krachlatte krachlatte Awaiting requested review from krachlatte krachlatte is a code owner

@pyavitz pyavitz Awaiting requested review from pyavitz pyavitz is a code owner

@schwar3kat schwar3kat Awaiting requested review from schwar3kat schwar3kat is a code owner

@sgjava sgjava Awaiting requested review from sgjava sgjava is a code owner

@teknoid teknoid Awaiting requested review from teknoid teknoid is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

02 Milestone: First quarter release 05 Milestone: Second quarter release 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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@EvilOlaf @igorpecovnik