List of notes in Linux Kernel Brickers:
- als
- aosp_docs
- authorship
- benchkit
- bisect
- bldgcc
- bringupchat
- caftracker
- cherrypicking
- clang
- compilation
- errortemplate
- gpu_profiling
- hackbench
- hastebin
- help
- io_bench
- io_bench_help
- meld_merge
- mergeqcacld
- mergingcaf
- missingheaders
- newgcc
- oem_caftag
- oemcommits
- ot
- patching
- powerofstable
- pstore
- subtreemerge
- tc-build
- upstream
You can retrieve these notes by using /get notename, or #notename
https://github.com/nathanchance/android-kernel-clang
Читать полностью…
List of notes in Linux Kernel Brickers:
- als
- aosp_docs
- authorship
- benchkit
- bisect
- bldgcc
- bringupchat
- caftracker
- cherrypicking
- clang
- compilation
- errortemplate
- gpu_profiling
- hackbench
- hastebin
- help
- io_bench
- io_bench_help
- meld_merge
- mergeqcacld
- mergingcaf
- missingheaders
- newgcc
- oem_caftag
- oemcommits
- ot
- patching
- powerofstable
- pstore
- subtreemerge
- tc-build
- upstream
You can retrieve these notes by using /get notename, or #notename
If you just wanna learn kernel compilation is easy
Читать полностью…
https://github.com/nathanchance/android-kernel-clang
Читать полностью…
https://gist.github.com/DD3Boh/6c51fd3c5f91b1042e956771483714de
Читать полностью…
https://github.com/nathanchance/android-kernel-clang
Читать полностью…
List of notes in Linux Kernel Brickers:
- als
- aosp_docs
- authorship
- benchkit
- bisect
- bldgcc
- bringupchat
- caftracker
- cherrypicking
- clang
- compilation
- errortemplate
- gpu_profiling
- hackbench
- hastebin
- help
- io_bench
- io_bench_help
- meld_merge
- mergeqcacld
- mergingcaf
- missingheaders
- newgcc
- oem_caftag
- oemcommits
- ot
- patching
- powerofstable
- pstore
- subtreemerge
- tc-build
- upstream
You can retrieve these notes by using /get notename, or #notename
On newer CAF revisions, standalone compilation will NOT work without specifying an out folder. Change all calls to make to make O=out in your scriptand missing headers should now resolve correctly. Alternatively, you can cherry-pick this commit.
Commits that change the location of the headers are NOT necessary and can potentially cause conflicts down the road.
Initial merge:git remote add qcacld-3.0 https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0git fetch qcacld-3.0 <TAG>git merge -s ours --no-commit --allow-unrelated-histories FETCH_HEADgit read-tree --prefix=drivers/staging/qcacld-3.0 -u FETCH_HEADgit commit
Updating to a newer tag:git fetch qcacld-3.0 <TAG>git merge -X subtree=drivers/staging/qcacld-3.0 FETCH_HEAD
Repeat the above for qca-wifi-host-cmn and fw-api as well.
qcacld-3.0 source: https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0
fw-api source: https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/fw-api
qca-wifi-host-cmn source: https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qca-wifi-host-cmn
Example commit
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/commit/4d40ad79436fec3874f79f14d9534cfe0e47e315
Breaking down a massive OEM commitsgit reset HEAD^ drivers/gpu
This resets the HEAD and only grabs the directories I specifygit commit --amend
This obviously amends the original commitgit add --all
This adds the directories I specified abovegit commit -a -m "Import OEM gpu driver changes"
This obviously adds the commit message
And finally this is the weird partgit rebase -i HEAD~2
After that last command is executed it will display a commit window.
This rebases and displays the last 2 commits in the repo. The original Xiaomi commit is on top and my commit is underneath. Xiaomi commit being the 2nd and mine being the first. So I need to move that Xiaomi commit to be the latest commit in git history.. Ctrl+k to cut the Xiaomi commit, and Ctrl+u to paste it under my commit. Boom, history is re-written and my commit is now older in history so I can proceed to do the same thing over and over again to the rest of the directories in this massive commit.
Then you get sexy commit history like this and makes things easier to find when you hit conflicts or build errors after merging your kernel with kernel-msm or caf or upstream.
https://github.com/deadman96385/android_kernel_lenovo_msm8909/commits/LA.BR.1.2.7-02810-8x09
Hey there DLK, and welcome to Linux Kernel Brickers! How are you?
Читать полностью…
It depends on what you want!! From learning kernel dev!! Whats your target
Читать полностью…
List of notes in Linux Kernel Brickers:
- als
- aosp_docs
- authorship
- benchkit
- bisect
- bldgcc
- bringupchat
- caftracker
- cherrypicking
- clang
- compilation
- errortemplate
- gpu_profiling
- hackbench
- hastebin
- help
- io_bench
- io_bench_help
- meld_merge
- mergeqcacld
- mergingcaf
- missingheaders
- newgcc
- oem_caftag
- oemcommits
- ot
- patching
- powerofstable
- pstore
- subtreemerge
- tc-build
- upstream
You can retrieve these notes by using /get notename, or #notename
