I want to build kernel with some flags enabled for my Samsung Nexus 10. Here is the info from android About device.
Android version
5.1.1
Kernel Version
3.4.67-g84ad5a4
android-build#wpee22.hot.corp.google.com#1
Fri Nov 13 21:33:05 UTC 2015
Build Number
LMY49J
I am following this AOSP guide to build the kernel -
https://source.android.com/source/building-kernels
I have cloned the repo but have no clue which branch and the commit to checkout.
arpit#arpit-ubuntu:~/kernel$ git clone https://android.googlesource.com/kernel/exynos.git
Cloning into 'exynos'...
remote: Sending approximately 874.72 MiB ...
remote: Counting objects: 15, done
remote: Total 3997821 (delta 3353407), reused 3997821 (delta 3353407)
Receiving objects: 100% (3997821/3997821), 874.72 MiB | 9.86 MiB/s, done.
Resolving deltas: 100% (3353407/3353407), done.
Checking connectivity... done.
arpit#arpit-ubuntu:~/kernel$ cd exynos/
arpit#arpit-ubuntu:~/kernel/exynos$ ls -l
total 0
arpit#arpit-ubuntu:~/kernel/exynos$
This directory is empty, so the logic given on AOSP to find commit and branch info from kernel binary logs is not applicable here.
git branch -a returns the following .
arpit#arpit-ubuntu:~/kernel/exynos$ git branch -a
* master
remotes/origin/HEAD -> origin/master
remotes/origin/android-exynos-3.4
remotes/origin/android-exynos-koi-3.10-marshmallow-dr1-wear-release
remotes/origin/android-exynos-koi-3.10-marshmallow-mr1-wear-release
remotes/origin/android-exynos-koi-3.18-nougat-mr1-wear-release
remotes/origin/android-exynos-manta-3.4-adf
remotes/origin/android-exynos-manta-3.4-jb-mr1
remotes/origin/android-exynos-manta-3.4-jb-mr1-fr
remotes/origin/android-exynos-manta-3.4-jb-mr1.1
remotes/origin/android-exynos-manta-3.4-jb-mr2
remotes/origin/android-exynos-manta-3.4-kitkat-mr0
remotes/origin/android-exynos-manta-3.4-kitkat-mr1
remotes/origin/android-exynos-manta-3.4-kitkat-mr2
remotes/origin/android-exynos-manta-3.4-lollipop-mr1
remotes/origin/android-exynos-manta-3.4-lollipop-release
remotes/origin/master
arpit#arpit-ubuntu:~/kernel/exynos$
My possible guess is the branch name is remotes/origin/android-exynos-manta-3.4-lollipop-mr1.
But none of the commits in this branch has this substring 84ad5a4 (Obtained from kernel version on device). Google search for string 84ad514 also doesn't return anything.
So I am struck here. I want to use the exact code corresponding to the kernel shipped on my device and not the most recent code on the kernel branch. Can you tell me how to figure out the branch and exact commit corresponding to the shipped kernel on my device.
Related
I have deployed the code once on github using github pages and now i have maked the changes in some of the code and now i am not able to push the code .I deleted the all branches and code on repo and did the process once again but still on live website i am not getting any changes .
PS D:\VJTI_Racing_Website_2.0\frontend> git add .
>> git commit -m "updated"
>> git push origin master
On branch gh-pages
nothing to commit, working tree clean
Enumerating objects: 26890, done.
Counting objects: 100% (26890/26890), done.
Delta compression using up to 8 threads
Compressing objects: 100% (21199/21199), done.
Writing objects: 100% (26890/26890), 779.96 MiB | 1.96 MiB/s, done.
Total 26890 (delta 4725), reused 26890 (delta 4725), pack-reused 0
remote: Resolving deltas: 100% (4725/4725), done.
remote: warning: File node_modules/.cache/default-development/3.pack is 52.95 MB; this is larger than GitHub's recommended maximum file size of 50.00 MB
remote: error: Trace: d119776a9de8bb6b95dccf52e4031387455d238a7a7367d558a094750a2328de
remote: error: See http://git.io/iEPt8g for more information.
remote: error: File node_modules/.cache/default-development/0.pack is 490.10 MB; this exceeds GitHub's file size limit of 100.00 MB
remote: error: GH001: Large files detected. You may want to try Git Large File Storage - https://git-lfs.github.com.
To https://github.com/vjtiracing/VJTI_Racing_Website_2.0.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://github.com/vjtiracing/VJTI_Racing_Website_2.0.git'
the error showing is of large file but I deleted the node modules file and also cleared the cache please someone help me out here.
I have a folder with codes, i pushed it on github after creating a repository but the process was successful but i can not see any file in the repository, any help guys, this is my cli codes
SydoTech#DESKTOP-PUHK97G MINGW64 /d/james/ict-specialists (master)
$ git remote add origin https://github.com/Kato669/ict-specialist-website.git
SydoTech#DESKTOP-PUHK97G MINGW64 /d/james/ict-specialists (master)
$ git push origin main
error: src refspec main does not match any
error: failed to push some refs to 'https://github.com/Kato669/ict-specialist-website.git'
SydoTech#DESKTOP-PUHK97G MINGW64 /d/james/ict-specialists (master)
$ git push origin master
Enumerating objects: 1383, done.
Counting objects: 100% (1383/1383), done.
Delta compression using up to 4 threads
Compressing objects: 100% (1380/1380), done.
error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8)
send-pack: unexpected disconnect while reading sideband packet
Writing objects: 100% (1383/1383), 35.93 MiB | 323.00 KiB/s, done.
Total 1383 (delta 181), reused 0 (delta 0), pack-reused 0
fatal: the remote end hung up unexpectedly
Everything up-to-date
SydoTech#DESKTOP-PUHK97G MINGW64 /d/james/ict-specialists (master)
$
Please! I lost all my day's work.
I created a github repository... I've been working all day doing git add -A and commit but I never did a push. I changed a readme directly on the page (not knowing I was going to have problems to merge those same branches).
When I tried to make git push after all day's rok the following happened:
To https://github.com/NEGU93/Steganography.git
! [rejected] master -> master (fetch first)
error: failed to push some refs to 'https://github.com/NEGU93/Steganography.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
So I tried ta git pull --rebase but it started crashing some things I don't know what it is:
remote: Counting objects: 3, done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 3 (delta 0), reused 0 (delta 0), pack-reused 0
Unpacking objects: 100% (3/3), done.
From https://github.com/NEGU93/Steganography
6161279..44d1f0f master -> origin/master
0 [main] expr 8516 open_stackdumpfile: Dumping stack trace to expr.exe.stackdump
0 [main] cat 15632 open_stackdumpfile: Dumping stack trace to cat.exe.stackdump
0 [main] rm 4660 open_stackdumpfile: Dumping stack trace to rm.exe.stackdump
^C
I put ctrl+C to stop the crashin there. So I made a git fetch and then a git push of my work:
fatal: You are not currently on a branch.
To push the history leading to the current (detached HEAD)
state now, use
git push origin HEAD:<name-of-remote-branch>
So I did as suggested and made a git push to master:
git push origin HEAD:master
Counting objects: 6, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 1.49 KiB | 0 bytes/s, done.
Total 5 (delta 1), reused 0 (delta 0)
remote: Resolving deltas: 100% (1/1), done.
To https://github.com/NEGU93/Steganography.git
44d1f0f..c3b8393 HEAD -> master
But now when I got back the work was not there... Help! I don't know what to do and I'm starting to panic. I think the problem is with git fetch. Is there a way to get all my work back???
Use git reflog to see past commits, then use the commit's hash to reset hard e.g.:
git reset --hard e870e41
See How can I recover a lost commit in Git?
http://git.buildroot.net/buildroot/tree/board/raspberrypi/readme.txt states the following — where the last line is the interesting one:
The raspberrypi_defconfig configuration is a minimal configuration
with all that is required to bring the Raspberry Pi up. You should
base your work on this defconfig:
$ make raspberrypi_defconfig
Alternatively, if you want to test support for the Device Tree:
$ make raspberrypi_dt_defconfig
For Raspberry Pi 2 use a different defconfig:
$ make raspberrypi2_defconfig
Is that raspberrypi2_defconfig required to use buildroot on an Raspberry Pi 2, or does it just contain RPi2 optimizations? The reason why I'm asking is that I don't find that configuration in the latest stable version of Buildroot, and the current git version abort the build with an
"HTTP request sent, awaiting response... 404: Not Found"
====================================
Console printout after second build crasch:
make[1]: Leaving directory `/home/fredrik/buildroot/output/build/host-lzop-1.03'
>>> linux 2c4959b772a35d9d459b0a92f39bb066e9a44d37 Downloading
Doing shallow clone
Cloning into bare repository 'linux-2c4959b772a35d9d459b0a92f39bb066e9a44d37'...
WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-BVQjKJ/pkcs11: No such file or directory
POST git-upload-pack (gzip 1077 to 570 bytes)
POST git-upload-pack (gzip 1086 to 577 bytes)
remote: Counting objects: 223619, done.
remote: Compressing objects: 100% (141382/141382), done.
remote: Total 223619 (delta 145491), reused 134621 (delta 80295), pack-reused 0
Receiving objects: 100% (223619/223619), 271.86 MiB | 1.80 MiB/s, done.
Resolving deltas: 100% (145491/145491), done.
warning: Remote branch 2c4959b772a35d9d459b0a92f39bb066e9a44d37 not found in upstream origin, using HEAD instead
fatal: not a tree object
--2015-04-13 00:26:38-- http://sources.buildroot.net/linux-2c4959b772a35d9d459b0a92f39bb066e9a44d37.tar.gz
Resolving sources.buildroot.net (sources.buildroot.net)... 176.9.16.109
Connecting to sources.buildroot.net (sources.buildroot.net)|176.9.16.109|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-04-13 00:26:38 ERROR 404: Not Found.
make: *** [/home/fredrik/buildroot/output/build/linux-2c4959b772a35d9d459b0a92f39bb066e9a44d37/.stamp_downloaded] Error 1
It's not mandatory, but it's a prebuilt configuration that ensures that you will have a working system.
When pasting errors, please include more lines (like 50-100 lines), because the real error is not this 404. It's earlier, the fact that it can't find in the RPi kernel Git repository the commit we're looking for. Try again with the latest Buildroot, I think we've updated the raspberrypi2_defconfig with a more recent RPi kernel commit.
The problem is that the RPi kernel git repository is often rebased against the linux-stable kernel, which means that the commit that buildroot refers to is no longer accessible.
The solution is to use a stable branch from the RPi kernel git repository, where no rebasing is done. This is done by this patch.
I tried deploying the sample GO application to Heroku listed here
But when I run the command:
git push heroku master
I get the following error:
Counting objects: 28, done.
Compressing objects: 100% (21/21), done. Writing objects: 100%
(28/28), 3.08 KiB, done. Total 28 (delta 6), reused 0 (delta 0)
! Heroku push rejected, no Cedar-supported app detected
To git#heroku.com:mysterious-refuge-1227.git ! [remote rejected]
master -> master (pre-receive hook declined) error: failed to push
some refs to 'git#heroku.com:mysterious-refuge-1227.git'
The sample code might be out-of-date so I created a simple hello world GO App but from the same git push command I got the following error:
Counting objects: 10, done.
Compressing objects: 100% (8/8), done.
Writing objects: 100% (10/10), 1.16 MiB | 690 KiB/s, done.
Total 10 (delta 1), reused 0 (delta 0)
-----> Fetching custom git buildpack... done
-----> Go app detected
-----> Installing Go 1.1... done
Installing Virtualenv... done
Installing Mercurial... done
Installing Bazaar... done
-----> Running: go get -tags heroku ./...
package echo/...: unrecognized import path "echo/..."
! Heroku push rejected, failed to compile Go app
To git#heroku.com:evening-reef-1503.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'git#heroku.com:evening-reef-1503.git'
Any ideas on how I can resolve this issue?
Here is my system info:
GoLang version: go version go1.1 linux/386
Kubuntu version: 12.10
I suspect your original error is because you created the application with heroku create. You're using Go, which is supported through a buildpack, so you should create the application with something like heroku create -b https://github.com/kr/heroku-buildpack-go.git. I believe the demo app makes the same mistake - my fork fixes it - and I've submitted a pull request too.