MiCode / MiCode/Xiaomi_Kernel_OpenSource

[Request] Kernel Sources for Redmi Note 10 5G/Redmi Note 11SE/Redmi Note 10T 5G/POCO M3 Pro 5G (camellia(n)) kernel 4.14.186

Open
#41,032 1 comment 2 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

Dear @mi-code,

I'm writing to request the immediate release of fixed kernel sources with proper display drivers for the Redmi Note 10 5G/Redmi Note 11SE/Redmi Note 10T 5G/POCO M3 Pro 5G with the codenames "camellia" and "camellian".

The Redmi Note 10 5G/Redmi Note 11SE/Redmi Note 10T 5G/POCO M3 Pro 5G was released with MIUI 12.5 (Android 11) powered by a modified Linux kernel version 4.14. The GPLv2-only license under which the Linux kernel is distributed, paragraph 3, requires the release of the latest, complete, and corresponding sources for modified programs licensed under it.

This device was released over five years ago and stopped receiving official updates about 3 years ago. The Redmi Note 11E/Redmi 10 5G/POCO M4 5G/Redmi 11 Prime 5G was released at the same time as the Redmi Note 10 5G/Redmi Note 11SE/Redmi Note 10T 5G/POCO M3 Pro 5G.They shares the exact same SoC-MediaTek Dimensity 700 (MT6833). Device with similar SoC codename light have their kernel sources present in the repository and have 4.19 instead of 4.14, and I don't see a reason why the Redmi Note 10 5G/Redmi Note 11SE/Redmi Note 10T 5G/POCO M3 Pro 5G is left behind if it is not a conscious GPLv2 violation.

The Redmi Note 11E/Redmi 10 5G/POCO M4 5G/Redmi 11 Prime 5G kernel sources, codename light, branch light-u-oss, despite being based on the same SoC, are not a perfect match for the Redmi Note 10 5G/Redmi Note 11SE/Redmi Note 10T 5G/POCO M3 Pro 5G. There are bugs that can only be resolved by obtaining the corresponding kernel sources. Developers have to reverse-engineer them to work more or less properly on camellia.

The community has been asking for kernel sources for over five years. I myself have been requesting them for the past months; I even tried my luck with the Xiaomi Global Support Team-no luck. Emails to tousu@ received no response, legal@ rejected the email immediately with "Access denied," and the support team replied with canned responses that could be addressed to any problem.

Throughout my requests and emails, I've asked for either of the following:

The release of the latest, complete, and corresponding kernel sources for the Redmi Note 10 5G/Redmi Note 11SE/Redmi Note 10T 5G/POCO M3 Pro 5G-branch camellia-u-oss, camellia-r-oss, or any matching equivalent; or
An official statement regarding the status of the kernel sources and their absence.
I've received neither. If the fixed kernel sources are not present in this repository within several days, I will have no choice but to report this violation to the SFC. All the requests, as well as my email chain with the Customer Support Team, will serve as evidence of a conscious GPLv2 violation.

I'm open to negotiation.

The camellia(n) user and ROM developer.

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 Xiaomi_Kernel_OpenSource repository for the camellia-u-oss and camellia-r-oss branches or another matching kernel source branch. Compare any available camellia(n) sources with the requested complete, corresponding Linux 4.14.186 sources; the request is complete when the matching sources or an official status statement is provided.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.