Hi,
This is a message is a call for testing as the 11.07 RC is fast
approach. There needs to be a special focus on the new elements that
have been integrated in the builds since the last call for testing.
Please try out the latest Linaro Evaluation Builds (LEBs) images for
both Android and Linux. As always log your results in
qatracker.linaro.org. Even if you're only able to test one
image/hwpack combination, your participation is greatly appreciated
and essential.
The plan from here to the 11.07 release as I understand is as follows:
7/18 (TODAY) - Issue new call for testing
7/21 - 11.07 New Function Freeze
7/22 - 11.07 RC Release
7/28 - 11.07 Release
Changelog
--------------
7-14 to 7-18
* x-loader:
- New upstream release - 1.5.1
- Fixes to make USB EHCI to work properly on Panda
* u-boot-linaro:
- New upstream release - 2011.07.1
- PXE FDT fix from previous ubuntu release so patch has been removed
- Added missing PXE env vars (LP: #808815)
- Generated unique usbethaddr (LP: #809015)
- Modify pxe command to look for usbethaddr if ethaddr is NULL
* libjpeg-turbo:
- New upstream release - 1.1.1
- Replacing libjpeg62 at all Linaro images
* base-files:
- Should now show itself as 11.07 (development branch)
Bugs fixed:
* Bug 809015: u-boot lacks unique mac address on Pandaboard while netbooting
* Bug 810750: Still identifies itself as 11.06
Linaro Evaluation Builds (LEB)
----------------------------------------
These images showcase the current state of development on our LEBs
images on their way to the next release: 11.07.
* Android:
http://snapshots.linaro.org/11.05-daily/linaro-android/leb-panda/20110718/
* Ubuntu:
http://snapshots.linaro.org/11.05-daily/linaro-ubuntu-desktop/20110718/0/im…http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/panda-x11-base/20110…
Installation Instructions
------------------------------
Installation Instructions can be found here:
https://wiki.linaro.org/Platform/Android/ImageInstallationhttps://wiki.linaro.org/Platform/DevPlatform/Ubuntu/ImageInstallation
Unsupported Images and Board Support Packages
------------------------------------------------------------------
Besides the official Linaro Evaluation Builds, the Platform Team hosts
additional functional images and board support packages.
These images and board support packages are not officially supported
and are provided on a best-effort basis in the hope that they can be
useful for the Linux/ARM enthusiast community.
Unsupported Images
-------------------------
* Nano: (Think small)
http://snapshots.linaro.org/11.05-daily/linaro-nano/20110718/0/images/tar/
* ALIP: (xfce UI)
http://snapshots.linaro.org/11.05-daily/linaro-alip/20110718/0/images/tar/
* Developer: (text UI + developer tools)
http://snapshots.linaro.org/11.05-daily/linaro-developer/20110718/0/images/…
Unsupported Board Support Packages:
--------------------------------------------------
Board Support Packages come in the form of what is called a hwpack.
Hwpacks can befound for efikamx, igep, imx51, lt-mx5, lt-mx53loco,
lt-origen, lt-panda-x11-base-natty, lt-panda, lt-s5pv310, lt-snowball,
lt-u8500, omap3-x11-base, omap3, overo, panda, s5pv310, and vexpress
http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/
Android Developer and Experimental Images
----------------------------------------------------------
Developer and Experimental Images based on Android (vanilla AOSP
experience using linux-linaro mainline kernel):
* Android Mainline for BeagleBoardr-xM:
http://snapshots.linaro.org/11.05-daily/linaro-android/beaglexm/20110718/
* Android Mainline for PandaBoard:
http://snapshots.linaro.org/11.05-daily/linaro-android/panda/20110718/
Reporting Testing Results
----------------------------------
Report results at:
http://qatracker.linaro.org
For an explanation of how to use the qatracker please see:
https://wiki.linaro.org/QA/QATracker
--
Regards,
Tom
"We want great men who, when fortune frowns will not be discouraged."
- Colonel Henry Knox
Linaro.org │ Open source software for ARM SoCs
w) tom.gall att linaro.org
w) tom_gall att vnet.ibm.com
h) tom_gall att mac.com
Hi Gang,
Two actions please:
1) Everyone: If you are coming to the Connect in Cambridge, please
bring as much of your hardware as possible. Several of our team coming
from China will not be able to bring theirs and they'll need a loaner
at the Connect.
2) For Linaro assignees: If you've gotten a board from me or your TL
in the last two months, PLEASE make sure you update your HW records.
See "List of Hardware" section on https://wiki.linaro.org/Internal/Hardware
Joey
Hi folks,
Many GNU/Linux distributions are doing some ARM porting; this tends to
result in work duplication, and there doesn't seem to be a general
purpose forum to bring ARM porters together.
We're inviting developers of GNU/Linux distributions with an interest
in ARM to join a new "cross-distro" list, hosted at Linaro:
http://lists.linaro.org/mailman/listinfo/cross-distro
Any ARM Linux / Free Software discussion is welcome on the list, for
instance porting software to build on ARM, toolchain problems, dealing
with new ABIs, Thumb-2, NEON, kernel problems, announcement of new
tools etc.
Cheers,
--
Steve McIntyre steve.mcintyre(a)linaro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs
From: David A. Long <dave.long(a)linaro.org>
Add a new "fdt_high" enviroment variable. This can be used to control (or prevent) the
relocation of the flattened device tree on boot. It can be used to prevent relocation
of the fdt into highmem. The variable behaves similarly to the existing "initrd_high"
variable.
Signed-off-by: David A. Long <dave.long(a)linaro.org>
---
README | 9 ++++++++
common/image.c | 60 ++++++++++++++++++++++++++++++++++++++++++++++----------
2 files changed, 58 insertions(+), 11 deletions(-)
diff --git a/README b/README
index 8bb9c8d..5b95246 100644
--- a/README
+++ b/README
@@ -3281,6 +3281,15 @@ List of environment variables (most likely not complete):
This can be used to load and uncompress arbitrary
data.
+ fdt_high - if set this restricts the maximum address that the
+ flattened device tree will be copied into upon boot.
+ If this is set to the special value 0xFFFFFFFF then
+ the fdt will not be copied at all on boot. For this
+ to work it must reside in writable memory, have
+ sufficient padding on the end of it for u-boot to
+ add the information it needs into it, and the memory
+ must be accessible by the kernel.
+
i2cfast - (PPC405GP|PPC405EP only)
if set to 'y' configures Linux I2C driver for fast
mode (400kHZ). This environment variable is used in
diff --git a/common/image.c b/common/image.c
index e542a57..7853de0 100644
--- a/common/image.c
+++ b/common/image.c
@@ -1234,8 +1234,10 @@ int boot_relocate_fdt (struct lmb *lmb, char **of_flat_tree, ulong *of_size)
{
void *fdt_blob = *of_flat_tree;
void *of_start = 0;
+ char *fdt_high;
ulong of_len = 0;
int err;
+ int disable_relocation=0;
/* nothing to do */
if (*of_size == 0)
@@ -1249,26 +1251,62 @@ int boot_relocate_fdt (struct lmb *lmb, char **of_flat_tree, ulong *of_size)
/* position on a 4K boundary before the alloc_current */
/* Pad the FDT by a specified amount */
of_len = *of_size + CONFIG_SYS_FDT_PAD;
- of_start = (void *)(unsigned long)lmb_alloc_base(lmb, of_len, 0x1000,
- getenv_bootm_mapsize() + getenv_bootm_low());
+
+ /* If fdt_high is set use it to select the relocation address */
+ fdt_high = getenv("fdt_high");
+ if (fdt_high) {
+ void *desired_addr = (void *)simple_strtoul(fdt_high, NULL, 16);
+
+ if (((ulong) desired_addr) == ~0UL) {
+ /* All ones means use fdt in place */
+ desired_addr = fdt_blob;
+ disable_relocation = 1;
+ }
+ if (desired_addr) {
+ of_start =
+ (void *)(ulong) lmb_alloc_base(lmb, of_len, 0x1000,
+ ((ulong)
+ desired_addr)
+ + of_len);
+ if (desired_addr && of_start != desired_addr) {
+ puts("Failed using fdt_high value for Device Tree");
+ goto error;
+ }
+ } else {
+ of_start =
+ (void *)(ulong) mb_alloc(lmb, of_len, 0x1000);
+ }
+ } else {
+ of_start =
+ (void *)(ulong) lmb_alloc_base(lmb, of_len, 0x1000,
+ getenv_bootm_mapsize()
+ + getenv_bootm_low());
+ }
if (of_start == 0) {
puts("device tree - allocation error\n");
goto error;
}
- debug ("## device tree at %p ... %p (len=%ld [0x%lX])\n",
- fdt_blob, fdt_blob + *of_size - 1, of_len, of_len);
+ if (disable_relocation) {
+ /* We assume there is space after the existing fdt to use for padding */
+ fdt_set_totalsize(of_start, of_len);
+ printf(" Using Device Tree in place at %p, end %p\n",
+ of_start, of_start + of_len - 1);
+ } else {
+ debug ("## device tree at %p ... %p (len=%ld [0x%lX])\n",
+ fdt_blob, fdt_blob + *of_size - 1, of_len, of_len);
- printf (" Loading Device Tree to %p, end %p ... ",
- of_start, of_start + of_len - 1);
+ printf (" Loading Device Tree to %p, end %p ... ",
+ of_start, of_start + of_len - 1);
- err = fdt_open_into (fdt_blob, of_start, of_len);
- if (err != 0) {
- fdt_error ("fdt move failed");
- goto error;
+ err = fdt_open_into (fdt_blob, of_start, of_len);
+ if (err != 0) {
+ fdt_error ("fdt move failed");
+ goto error;
+ }
+ puts ("OK\n");
}
- puts ("OK\n");
*of_flat_tree = of_start;
*of_size = of_len;
The first 11.07 Android rc builds are out.
Bero and Mathieu, would you test the LEB's that came out for iMX53 and
Snowball and attach logs to this email?
I've also filed bugs on things that aren't working right.
We have till UTC tomorrow to finish up the RC, but these should give
us a good baseline. Please concentrate on the remaining issues.
Overall we're looking good.
Botao,
Any chance we can get a Samsung build into the build system? ;)
Here are all the builds:
Panda
https://android-build.linaro.org/builds/~linaro-android/panda-11.07-release…
linaro-image-tools
376
Plug into DVI port, 640x480p @60Hz DVI
0xbench runs
Bug:
HDMI fails to come up on panda 11.07 rc build 1
https://bugs.launchpad.net/linaro-android/+bug/812097
Beagle C4
https://android-build.linaro.org/builds/~linaro-android/beagle-11.07-releas…
linaro-image-tools
376
Plug into DVI port, 1280x720p @58Hz DVI
0xbench runs
Beagle xM
https://android-build.linaro.org/builds/~linaro-android/beagle-11.07-releas…
linaro-image-tools
376
Display doesn't come up
Bug:
Display fails to come up on DVI or HDMI on beagle xm 11.07 rc build 1
https://bugs.launchpad.net/linaro-android/+bug/812098
Panda-LEB
https://android-build.linaro.org/builds/~linaro-android/leb-panda-11.07-rel…
linaro-image-tools
376
Screen comes up in 1920x1080p@60Hz DVI, then the build crashes
Bug:
Build crashes on Panda LEB 11.07 rc build 1
https://bugs.launchpad.net/linaro-android/+bug/812100
iMX53
~linaro-android/leb-imx53-11.07-release
Snowball
~linaro-android/leb-snowball-11.07-release
-Zach
On 17 July 2011 17:48, Zach Pfeffer <zach.pfeffer(a)linaro.org> wrote:
> Right now you'd just
>
> git clone git://git.linaro.org/android/platform/manifests.git
> cd manifests
> git checkout linaro_android_2.3.4
>
>
> Add the test to all the manifests:
>
> default.xml LEB-iMX53.xml LEB-panda.xml
>
> then something like:
>
> git remote add manifests
> ssh://pfefferz@git.linaro.org/srv/git.linaro.org/git/android/platform/manifests.git
>
> git push manifests HEAD
>
> When we cut the official builds we take the pinned manifest from a
> successful build and check it in on something like
>
> linaro-android-11.07-release
>
> -Zach
>
> On 17 July 2011 02:47, Bernhard Rosenkranzer
> <bernhard.rosenkranzer(a)linaro.org> wrote:
>> On 15 July 2011 20:57, Zach Pfeffer <zach.pfeffer(a)linaro.org> wrote:
>>> Multimedia test framework
>>> Pull into official manifest
>>
>> Is there any trick to get this into every manifest, or do I have to
>> edit all the LEB-*.xml files?
>> Will get the "no test files" dialog in today...
>>
>>> Freescale
>>> Need to get the current build in the build system
>>
>> Some good news on that one:
>> It builds 100% these days, even in android-build.
>> https://android-build.linaro.org/builds/~berolinux/imx53-20110706-0/
>
> Cool, thanks for the great work. Lets make it an official WIP LEB.
>
>>
>> Still got lots of testing+fixing to do though.
>>
>> ttyl
>> bero
>>
>
Hi All,
I'm pleased to announce we have changed the date for Linaro Connect Q4 2011.
It will now be October 31 - 4 November, still in Orlando Florida and still
co-located with Ubuntu Developer Summit (which has also changed date).
The reason for this is primarily to avoid clashing with other important
industry events including ELC Europe, Gstreamer 2011 and ARM TechCon
I strongly suggest you start booking travel now. At least from UK, airline
flights are already pretty restricted as its around half term week for kids
(oh, joy - that will make the plane trip fun ;-).
Details about Linaro Connect will start building here:
https://wiki.linaro.org/Events/LinaroConnectQ4.11
Thx
Stephen Doel
Chief Operating Officer
T: +44 1223 45 00 23 │ M: +44 77 66 014 247
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro/155974581091106>
Facebook | <http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
In-order to make reproducible builds we create pinned manifests with
each commit explicitly listed. We also use this method to create a
release. We depend on these pinned commits - if they don't exist the
"released" builds can no longer be reproduced.
-Zach
