MiCode / MiCode/Xiaomi_Kernel_OpenSource

GPL Source Code Request: Incomplete kernel source for spinel (Redmi Note 15 4G) — published branch does not match official shipped firmware

Open
#41,055 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
9.9k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

Subject: GPL Source Code Request: Incomplete kernel source for spinel (Redmi Note 15 4G)

Hello,

I am writing to request complete GPLv2-compliant kernel source code for the
device "spinel" (Redmi Note 15 4G / REDMI Note 15).

The branch currently published at:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/spinel-v-oss

contains only a generic, unmodified Linux 5.10 GKI common-kernel tree with no
device-specific content:

  • No device tree source (arch/arm64/boot/dts/mediatek/) for this device
  • No device-specific defconfig (only generic gki_defconfig / mgk_64_k510_defconfig)
  • No vendor modules, MTK proprietary drivers, or any board-specific code

The official HyperOS firmware currently released for this device (build
3.301.0) reports a kernel version of 6.12, not 5.10. The published branch
does not correspond to the kernel actually shipping in the official release.

Under GPLv2, distribution of a device with a Linux kernel requires that the
complete corresponding source code (including all kernel modifications,
device tree, and any GPL-licensed kernel modules) be made available to
recipients of the binary. A generic upstream tree with no device-specific
code does not satisfy this obligation.

I would appreciate it if you could:

  1. Publish the actual kernel source tree that matches the kernel shipping in
    the official spinel (Redmi Note 15 4G) release, including device tree,
    board defconfig, and all kernel modules (in-tree and out-of-tree)
    required to build a working kernel for this device.
  2. Confirm which kernel version (5.10 or 6.12) is actually shipping in the
    official 3.301.0 release, and update the branch name/tag accordingly if
    there is a mismatch.

Please let me know if you need any additional information to process this
request.

Thank you,
Fraykiee

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the spinel-v-oss branch and the reported kernel version for official firmware build 3.301.0. Compare the published tree with the requested device tree, board defconfig, and kernel modules; done means the matching source is published or the shipping kernel version is confirmed and the branch is corrected.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
embedded-iot, operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.