Code Monkey home page Code Monkey logo

kernel_devicetree's People

Contributors

mi-code avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

kernel_devicetree's Issues

Release kernel source code for Redmi note 12 5G (SUNSTONE)

Greetings, Xiaomi Team

I am writing as a Redmi Note 12 5G Sunstone user to ask for the release of the kernel and device trees for this particular handset.

I'm interested in customizing my device and helping to create custom ROMs and kernels because I'm an enthusiast and developer. Without having access to the required kernel and device tree sources, I am unable to achieve it, though.

I ask Xiaomi to make the Redmi Note 12 5G Sunstone's kernel and device trees available, as doing so will allow the development community to make custom ROMs and kernels for the smartphone and enhance the user experience in general.

I appreciate you giving this issue your attention. I value your ongoing assistance with the information

Xiaomi Pad 5 Missing

The device tree of the Xiaomi Pad 5 (non pro) is missing.
Xiaomi Pad 5 Pro, Xiaomi Pad 5 Pro 5G are available but it is unknown if this device tree can be used for the Xiaomi Pad 5 due to the difference in specifications for the devices.

Please add the device tree for the Xiaomi Pad 5 (non pro)

Repository description spelling error

The description of this repo says kenrel devicetree project for xiaomi kernel opensource when it should say kernel devicetree project for xiaomi kernel opensource

Redmi note 12

Why device trees are not released for this device 🥲

kernel_devicetree/qcom/ is missing kernel_devicetree/qcom/display/ required to build umi / cmi source!

kernel_devicetree/qcom/ is missing kernel_devicetree/qcom/display/ required to build umi / cmi source!

Sample:

EXAMPLE OF MISSING DTSIs required to build umi-q-oss source on Xiaomi_Kernel_Opensource:

/vendor/qcom/Makefile:
ifeq ($(CONFIG_BUILD_ARM64_DT_OVERLAY),y)
dtbo-$(CONFIG_ARCH_KONA) +=
kona-cdp-overlay.dtbo \

kona-cdp-overlay.dts:
#include "kona-cdp.dtsi"

kona-cdp.dtsi:
#include "camera/kona-camera-sensor-cdp.dtsi" -> NOT IN MiCode/kernel_devicetree!

vili-r-oss devicetree broken

Hello, your vili-r-oss devicetree source is incomplete, as these needed DTS modifications are missing.

qcom/camera
qcom/display

It would be appreciated on uploading them, for avoiding usage of prebuilt DTBO image, or painfully reverse-engineer that.
Only pushing them will help a lot, for devs wanting to improve the device, and for users, knowing how that works

Device Tree for Picasso seems broken

I don't know if it's my mess-up, but I was not able to build the exact same dtb image as found in the official boot.img. My built dtb image is 4.4M when concatenated while the official one is only ~800K, and most importantly, when packaged into boot.img, the one built by me does not work and fails straight into bootloader. In console-ramoops I can't even see kernel messages during such a crash, which probably means the kernel isn't even booted enough to output anything to ramoops. I tried to unpack the concatenated dtb images and compare them one-by-one, but it seemed to me that even the same dtb in the two images do not really match up and differs quite significantly.

In my current effort to port LineageOS 17.1 to this device, I resorted to using OSS kernel + prebuilt DTB / DTBO for now. I hope that this can be sorted out soon as some of my kernel changes had to be dirty hacks without functional OSS DTB / DTBO.

Of course, since I'm not aware of anyone else that is currently trying to build kernel + dt for this device, it could be totally my fault instead of Xiaomi's. But for now since I do not know, I'm keeping this open until someone fixed it or could help figure out why mine does not work. My forked kernel source code (with dt included) is at https://github.com/PeterCxy/android_kernel_xiaomi_sm7250

[GPL] Xiaomi mondrian Poco F5 Pro / Redmi K60 big amount of changes missing / not pushed

Please review and provide the full code for the following device.

We are missing a huge amount of parts for the device including Techpack Entirely.

  • Missing Techpack entirely [audio, camera, cvp, dataipa, datarmnet-ext, datarmnet, display, eva, mmm-test, mmm, video]
  • Missing "Kernel: Xiaomi kernel_audio for Redmi K60 Android S"
  • Missing "Kernel: Xiaomi camera-kernel changes for Redmi K60 Android S"
  • Missing appropriate "Kernel-devicetree: Xiaomi kernel changes for Redmi K60 Android S"
  • Missing drivers/misc/hwid, which is device-specific
  • Missing Touchscreen drivers
  • CONFIG_TOUCHSCREEN_ST_FTS_V521_SPI=m
  • CONFIG_TOUCHSCREEN_XIAOMI_TOUCHFEATURE=m
  • List can be prolongated.

Mi Max 3 missing

I am still searching for a decently current device tree for the Mi Max 3 (nitrogen)

Verizon APN settings for 12 global

The verizon apn settings are incorrect. They default to the LTE - Verizon settings for CBS, IMS, INTERNET, and FOTA. These settings are incorrect, after experimenting with the settings from google source these 8 entries should be removed and replaced. Sorry if this isnt the best description, let me know if you require pictures or more information. Thank you!

gauguin-q-oss tree does not compile

From a basic setup using kernel e601e14 and device tree 726054c:

arch/arm64/boot/dts/vendor/qcom/gauguin-sm6350-overlay.dtbo: ERROR (duplicate_property_names): /fragment@46/__overlay__:qcom,mdss-dsi-bl-max-level: Duplicate property name
arch/arm64/boot/dts/vendor/qcom/gauguin-sm6350-overlay.dtbo: ERROR (duplicate_property_names): /fragment@47/__overlay__:qcom,mdss-dsi-bl-max-level: Duplicate property name
arch/arm64/boot/dts/vendor/qcom/gauguin-sm6350-overlay.dtbo: ERROR (duplicate_property_names): /fragment@48/__overlay__:qcom,mdss-dsi-bl-max-level: Duplicate property name
arch/arm64/boot/dts/vendor/qcom/gauguin-sm6350-overlay.dtbo: ERROR (duplicate_property_names): /fragment@49/__overlay__:qcom,mdss-dsi-bl-max-level: Duplicate property name
arch/arm64/boot/dts/vendor/qcom/gauguin-sm6350-overlay.dtbo: ERROR (duplicate_property_names): /fragment@50/__overlay__:qcom,mdss-dsi-bl-max-level: Duplicate property name
arch/arm64/boot/dts/vendor/qcom/gauguin-sm6350-overlay.dtbo: ERROR (duplicate_property_names): /fragment@51/__overlay__:qcom,mdss-dsi-bl-max-level: Duplicate property name
ERROR: Input tree has errors, aborting (use -f to force output)
make[4]: *** [scripts/Makefile.dtbo:25: arch/arm64/boot/dts/vendor/qcom/gauguin-sm6350-overlay.dtbo] Error 2
make[3]: *** [../scripts/Makefile.build:643: arch/arm64/boot/dts/vendor/qcom] Error 2
make[2]: *** [../scripts/Makefile.build:643: arch/arm64/boot/dts/vendor] Error 2
make[1]: *** [arch/arm64/Makefile:159: dtbs] Error 2
make: *** [Makefile:146: sub-make] Error 2

I've made a potential patch over at https://github.com/FloatingGhost/device_tree_xiaomi_gauguin which fixes compilation and allows a device to boot based on the dtb image, but i'm not well-versed enough in how the kernel works to know if this is the right way to go about it

Redmi K30 pro (lmi) 分支的device tree 好像缺文件啊?

对比 AndroidDump/dtbo 下的dtb 和 dtbo.img 的entry cout发现是有13个dtb 的,但是 lmi 分支里配置上 CONFIG_BUILD_ARM64_DT_OVERLAY=y 再加上 lmi-sm8250-overlay.dtbo 编出来的也仅仅10个entry count.
应该是少了 xiaomi-skuld-dtbo.dts, xiaomi-urd-dtbo.dts 和 xiaomi-verthandi-dtbo.dts 相关的源码文件。
这个与 #2 这个问题类似, 相关的data-kernel, audio-kernel, techpack, qcom-caf的补丁都打好了,使用dump 出来的dtb和dtbo.img, 是可以启动stock rom的。
如果缺少device tree, 请补充好可用的device tree, 半成品没法玩啊。
如果是编译方式有问题, 还请不吝指出。
@ivan19871002 @mi-code @liuguo09

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.