DO-NOT-MERGE: early bump to 6.15 (uefi-all, meson64, rockchip64)

[rpardini]

Hey, I started bumping to 6.15(-rc1) thinking it was gonna be easy.
As always, it.. wasn't.
So here's a branch on the upstream and a draft PR so we can maybe coordinate who can work on what.
As-is, the branch disables EXTRAWIFI and predatorily drops patches until things build.
All the commits marked HACK must be dropped and replaced with actual fixes.
We could this per-family, but the wifi drivers question is common to mostly all.

• meson64: mostly clean, @pyavitz already rebased the patch that needed it, thanks
• uefi-arm64: clean
• rockchip64: large number of landed patches, large number of non-applying patches
• wifi drivers: mostly all broken
• rockchip64: patches on top of broken wifi drivers also broken

---

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

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

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[rpardini]

Ref the out-of-tree wifi drivers, I think all of them have trouble building, my guess it is regarding some kind of -I $(src) $(srctree) or such Makefile change upstream.

   drivers/net/wireless/rtl8192eu/core/rtw_cmd.c:17:10: fatal error: drv_types.h: No such file or directory
      17 | #include <drv_types.h>
         |          ^~~~~~~~~~~~~

   drivers/net/wireless/rtl8189es/core/rtw_cmd.c:17:10: fatal error: drv_types.h: No such file or directory
      17 | #include <drv_types.h>
         |          ^~~~~~~~~~~~~

   drivers/net/wireless/rtl88x2cs/core/rtw_cmd.c:17:10: fatal error: drv_types.h: No such file or directory
      17 | #include <drv_types.h>
        |          ^~~~~~~~~~~~~

And so on and so forth.

[timsurber]

Hi,
arm-trusted firmware should also be switched to mainline for all boards (at least for mainline kernel) to support HDMI-RX like it was already done on FriendlyElec CM3588.