[Regression] Android Binder no longer built into linux-neptune since 6.18

已关闭
#2,848 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
66/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
linux

调研方向

Compare the linux-neptune-615 and linux-neptune-616 configurations with the .config files from the linux-neptune-618 and linux-neptune-72 headers packages, using the reported /proc/config.gz values as a check. Locate the kernel configuration entry that controls Android Binder and binderfs, then verify the built kernel exposes the three requested settings in its configuration.

由索引模型根据 Issue 内容生成。

描述

SteamOS: 3.9.2 beta (BUILD_ID 20260925.101), kernel 7.2.7-valve1-1-neptune-72
Device: Lenovo Legion Go S (SteamOS edition)

Binder IPC and binderfs were built into linux-neptune-615 (6.15.11.valve1) and
linux-neptune-616 (6.16.12.valve27 in jupiter-3.8, 6.16.12.valve28 in jupiter-3.9):

  CONFIG_ANDROID_BINDER_IPC=y
  CONFIG_ANDROID_BINDERFS=y
  CONFIG_ANDROID_BINDER_DEVICES=""

This made it possible to run Waydroid on SteamOS without modifying the rootfs
or disabling read-only mode: no extra kernel module was needed, Waydroid itself
can be installed via Nix, and the remaining configuration lives in /etc.

In linux-neptune-618 (6.18.50 current Stable) and linux-neptune-72 (7.2.4, 7.2.7, current Beta) binder is
disabled:

  # CONFIG_ANDROID_BINDER_IPC is not set

so CONFIG_ANDROID_BINDERFS, which depends on it, is unavailable as well.
(Checked in /proc/config.gz on 7.2.7 and in the .config of the
linux-neptune-*-headers packages from the jupiter-3.8/3.9 repos.)

ANDROID_BINDER_IPC is a bool option, so it cannot be built as a module. The
only alternative is an out-of-tree binder module, which must be rebuilt for
every kernel release and taints the kernel (flags O and E).

Request: please re-enable, as in 6.15/6.16:

  CONFIG_ANDROID_BINDER_IPC=y
  CONFIG_ANDROID_BINDERFS=y
  CONFIG_ANDROID_BINDER_DEVICES=""

Related: #922

主要语言
没有语言数据
星标
2.7k
派生
88
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ValveSoftware/SteamOS 的其他 Issue

查看 ValveSoftware/SteamOS 的全部 Issue

相似的 Issue

更多 Operating Systems Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。