This is a cache of https://discuss.96boards.org/t/android-release/88. It is a snapshot of the page at 2024-10-31T02:35:16.014+0000.
Android release? - DragonBoard410c - 96Boards Forum

Android release?

Products Support DragonBoard410c
#1

So…

The board comes with Android-something pre-installed. The only identification I can come up with for that, is the kernel build date of June 10, 2015.

On the 96boards product page, there is something identified as release “15.06”. I take that to mean June 2015. Is this the same build as it ships with?

In addition, there is a set of build instructions that involve CAF release tag LA.BR.1.2.4-00310-8x16. This is dated to all the way back to May 19. Does this CAF tag match against either the pre-installed or the downloadable build?

#2

No it is not the same build

The kernel associated to 15.06 has the following signature:
Linux version 3.10.49-g3339759-00001-g4c4bccd (buildslave@aosp-x86-64-08) (gcc version 4.9.x-google 20140827 (prerelease) (gcc) ) #15 SMP PREEMPT Tue Jun 16 08:29:35

You can upgrade by

  1. download the bootloader:
    https://builds.96boards.org/releases/dragonboard410c/linaro/rescue/15.06

  2. download Android 15.06 images:
    https://builds.96boards.org/releases/dragonboard410c/qualcomm/android/15.06

Note that you can simply execute wget as follows:
wget -r -nH --cut-dirs=2 --no-parent --reject=“index.html*” https://builds.96boards.org/releases/dragonboard410c/qualcomm/android/15.06

  1. follow the instructions in the Android document:
    https://www.96boards.org/products/ce/dragonboard410c/
#3

That really isn’t what I was asking. I know how to update everything.

I’m interested in knowing where everything comes from and what the relationships between the different available pieces are.

In particular, June 10th vs June 16th doesn’t necessarily imply that the source code it was built FROM is actually any different.

#4

Actually that is what you asked (although I can see not exactly what you meant)

Q: “On the 96boards product page, there is something identified as release “15.06”. I take that to mean June 2015. Is this the same build as it ships with?”
A:No it is not the same build

If the git tag is in the install instructions (LA.BR.1.2.4-00310-8×16 is a GIT tag) it must have been used for one of the releases.

[jramirez@calypso linux.git (LA.BR.1.2.4_rb1.2)]$ git show LA.BR.1.2.4-00310-8x16.0
tag LA.BR.1.2.4-00310-8x16.0
Tagger: Linux Build Service Account <lnxbuild@localhost>
Date: Tue May 19 05:55:34 2015 -0700

“LA.BR.1.2.4-00310-8x16.0”

commit dc27d9bbafbfd9c1e0cfbb4b5da083b312963549
Merge: bf19b76 88b27d9
Author: Linux Build Service Account <lnxbuild@localhost>
Date: Fri May 15 07:33:38 2015 -0700

Merge "arch:arm: msm: removed not needed device trees" into LA.BR.1.2.4_rb1.2

Please point me to the instructions you are following and maybe reword your question so I can help.

I am really not sure what you are asking: If you know how to update everything it means you already have access to all the necessary repositories and therefore it is a matter of identifying the commits.

Are you perhaps trying to learn how are the releases generated?

#5

I was reading gain your original note. Actually I was confused by the build dates you provided (releases dont get rebuild unless there are significant changes) so let me check again.

Looking at the install scripts and trying to answer your other question:
“Does this CAF tag match against either the pre-installed or the downloadable build?”

After looking at the release generation scripts I believe the kernel should be the same on both (default and 15.06).

Releases get put together from here: https://git.linaro.org/ci/job/configs.git/blob/HEAD:/96boards-dragonboard410c-android.yaml

This is the relevant section for the manifest:

0 MANIFEST_FILENAME=LA.BR.1.2.4-00310-8x16.0.xml

  1. repo init -u git://codeaurora.org/platform/manifest.git -b release -m ${MANIFEST_FILENAME} --repo-url=git://codeaurora.org/tools/repo.git

  2. if you look in the manifest associated to the build for the kernel you will see:
    <project name=“kernel/msm-3.10” path=“kernel” revision=“dc27d9bbafbfd9c1e0cfbb4b5da083b312963549” upstream=“LA.BR.1.2.4_rb1.2”/>

  3. that should be the kernel being used for the release (independently of the build date)

does this help?

#6

Perfect, yes. Thank you very much!