Hi, Tim
We only run boot test for the master juno build, but it failed to boot on our LAVA as well. One problem I can see there is about getting the value of ro.hardware. You can try with passing "androidboot.hardware=juno" as kernel parameter to check if you can boot the recent builds.
Since we don't have much resources before, there was not maintainer for this master juno build for a while.
But you can always send mail to linaro-android@lists.linaro.org mailing list for any question related to android.
Thanks, Yongqin Liu
On 28 May 2015 at 04:43, Tim Klein Tim.Klein@arm.com wrote:
Hi,
I work for ARM and am trying to find someone in Linaro who is responsible for maintaining the Android master Juno snapshots. After a bit of searching forums etc. it seems that you may be able to help. If you are not the correct person then I’d be really grateful if you could point me in the right direction.
I’ve successfully run build 251 of the snapshots http://snapshots.linaro.org/android/~linaro-android/armv8-aosp-master-juno-l... , however more recent versions do not seem to run. Before I look into the problem further it would be really useful to understand what testing is done on these snapshots and what expectations one should have on their functionality.
If they ‘should work out the box’ then I should assume that I’m doing something wrong and would appreciate help in working what mistakes I’m making.
Many thanks in advance,
Tim Klein
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
On Thu, 2015-05-28 at 15:53 +0800, YongQin Liu wrote:
Hi, Tim
We only run boot test for the master juno build, but it failed to boot on our LAVA as well. One problem I can see there is about getting the value of ro.hardware. You can try with passing "androidboot.hardware=juno" as kernel parameter to check if you can boot the recent builds.
That build seems to use the kernel produced by the ARM Landing Team within Linaro. I removed the hack from that a while ago that gave the board the model name 'Juno' which Android uses to determine the hardware type. So yes, to get it working again you will need androidboot.hardware=juno on the kernel command-line. That's what our latest UEFI defaults to doing.
BTW, the latest kernel also requires the latest firmware, due to changes in SCPI interface.
Generally, the best bet to get a working Android on Juno is to use a proper monthly release and follow its instructions. Either the one done for ARM specifically [1] or the Linaro Confectionery Release (LCR). As there is a confusing and every changing plethora of builds Linaro does I would start from the main downloads page [2], that hasn't been updated yet for the release due today.
[1] http://releases.linaro.org/15.05/members/arm/android/images/armv8-android-ju... [2] https://www.linaro.org/downloads/
Since we don't have much resources before, there was not maintainer for this master juno build for a while.
So why do Linaro still create the builds? (Rhetorical question)
Tixy,
Thank you for your very helpful reply.
[2] https://www.linaro.org/downloads/ [2], that hasn't been updated yet for the release due today.
The link still doesn't seem to have been updated. Do you know when the update is expected to happen?
Thx,
Tim
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
On Fri, 2015-05-29 at 09:44 +0100, Tim Klein wrote:
[2] https://www.linaro.org/downloads/ [2], that hasn't been updated yet for the release due today.
The link still doesn't seem to have been updated. Do you know when the update is expected to happen?
Whenever ARM sign-off on it. I'm currently awaiting release note tweaks and their final testing. But it effectively a formality now so if you want to get on with things use... http://releases.linaro.org/15.05/members/arm/android/images/armv8-android-ju...
On Thu, 2015-05-28 at 12:44 +0100, Jon Medhurst (Tixy) wrote:
On Thu, 2015-05-28 at 15:53 +0800, YongQin Liu wrote:
Hi, Tim
We only run boot test for the master juno build, but it failed to boot on our LAVA as well. One problem I can see there is about getting the value of ro.hardware. You can try with passing "androidboot.hardware=juno" as kernel parameter to check if you can boot the recent builds.
That build seems to use the kernel produced by the ARM Landing Team within Linaro. I removed the hack from that a while ago that gave the board the model name 'Juno' which Android uses
I was mistaken in that assertion, the device-tree hack [1] is still there in th 15.05 release. I had left it in until we could roll out the new firmware within Linaro that updated the default UEFI kernel commandline. Now that's happened I will remove the hack.
[1] https://git.linaro.org/landing-teams/working/arm/kernel-release.git/commit/d...
On Thu, May 28, 2015 at 6:44 AM, Jon Medhurst (Tixy) tixy@linaro.org wrote:
So why do Linaro still create the builds? (Rhetorical question)
-- Tixy
FWIW, in 15.05 the number of available builds in the android directory is down quite a bit.
Just FVP, Juno and Versatile Express available in 2 flavors.
The R-LCR flavor is just stock 5.1.1 AOSP plus whatever platform support is needed. The R is for Reference.
The M-LCR flavor is includes 5.1.1 AOSP, plus platform support plus additional improvements by the ARM and Linaro engineering teams. The M is for Member.
linaro-android@lists.linaro.org
-
Jon Medhurst (Tixy) -
Tim Klein -
Tom Gall -
YongQin Liu