MiCode / MiCode/MTK_kernel_device_modules

warhol (Xiaomi 17T Pro): source missing for 28 GPL-licensed kernel modules

Open
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
10
Forks
9
PR merge metrics
No merged PRs in 30d

Description

Thank you for publishing the bsp-warhol-w-oss branches of MTK_kernel_device_modules and MTK_kernel_modules.

Comparing those branches with the kernel modules that ship on the device, 28 modules have no source in either branch. Each one declares MODULE_LICENSE("GPL") or MODULE_LICENSE("GPL v2") in its own .modinfo, so under GPLv2 section 3 their corresponding source should be available as well.

Device: Xiaomi 17T Pro (warhol), model 2602EPTC0G
Firmware: OS3.0.310.0.WPSMIXM (Android 16)
Kernel: 6.12.38-android16-5-g1d46253471dd-ab15048002-4k

Modules (file, where it ships, declared license):

  • binder_gki.ko (vendor_dlkm, GPL)
  • binder_prio.ko (vendor_dlkm, GPL)
  • crash_module.ko (vendor_boot, GPL v2)
  • dynamic_readahead.ko (vendor_boot, GPL v2)
  • io_monitor.ko (vendor_boot, GPL v2)
  • iorap2.ko (vendor_dlkm, GPL v2)
  • kshrink_slabd.ko (vendor_boot and vendor_dlkm, GPL v2)
  • metis.ko (vendor_dlkm, GPL)
  • mi_mem_epoll.ko (vendor_dlkm, GPL)
  • mi_memory.ko (vendor_boot, GPL)
  • mi_mempool.ko (vendor_dlkm, GPL)
  • mi_schedule.ko (vendor_dlkm, GPL)
  • mi_thermal_interface.ko (vendor_dlkm, GPL v2)
  • mi_unfairmem.ko (vendor_dlkm, GPL)
  • miev.ko (vendor_boot, GPL)
  • migt.ko (vendor_dlkm, GPL)
  • millet_binder.ko (vendor_dlkm, GPL)
  • millet_core.ko (vendor_dlkm, GPL)
  • millet_hs.ko (vendor_dlkm, GPL)
  • millet_oem_cgroup.ko (vendor_dlkm, GPL)
  • millet_pkg.ko (vendor_dlkm, GPL)
  • millet_sig.ko (vendor_dlkm, GPL)
  • perf_helper.ko (vendor_boot and vendor_dlkm, GPL)
  • powersave.ko (vendor_dlkm, GPL)
  • simtray.ko (vendor_boot and vendor_dlkm, GPL)
  • sla.ko (vendor_dlkm, GPL v2)
  • xiaomi_spi_tee.ko (vendor_dlkm, GPL)
  • xm_power.ko (vendor_dlkm, GPL)

Could you please publish the source for these modules, matching the version shipped in OS3.0.310.0.WPSMIXM, together with the Kbuild/Makefile/BUILD.bazel entries and headers needed to build them? Adding them to the existing bsp-warhol-w-oss branches would be ideal.

How this was checked: every .ko in the vendor_boot ramdisk and in vendor_dlkm was matched by name against the Kbuild, Makefile and Bazel files and the source file names in both branches. These 28 have no match. For miev, only the header include/miev/mievent.h is present, not the driver.

Thank you.

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

Compare the bsp-warhol-w-oss branches with the listed modules shipped in vendor_boot and vendor_dlkm. Start by checking the existing Kbuild, Makefile, BUILD.bazel files and headers, including include/miev/mievent.h. Done means matching source, build entries, and required headers are published for OS3.0.310.0.WPSMIXM.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, linux
Domain
build-system, operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.