Hello,
We started migrating Android build artifacts as produced by
https://android-build.linaro.org/ to http:///snapshots.linaro.org
almost 2 months ago and now the migration can be pronounced complete.
From now on, http://snapshots.linaro.org/android/ is the master
download location for all Android builds, with all builds done in last 2
months available there, important historical builds (*1) migrated
there too, and archiving on android-build.linaro.org now turned off.
There are several benefits for hosting Android builds directly on
snapshots.linaro.org:
1. It is a central place for all Linaro downloads.
2. It allows to manage EULA protection in centralized manner.
3. It allows for consistent structuring and styling.
4. It allows for better space and retention policy management.
5. It alleviates Infrastructure team from maintaining Android
downloads on the Jenkins server, allowing us to concentrate on build
side of it.
Please note that this change is transparent to
https://android-build.linaro.org/ - artifacts can still be download
from its detailed pages, the links just point to
snapshots.linaro.org . All existing artifacts also stay available on
android-build.linaro.org, so any previously disseminated links remain
valid (*2).
*1 Only historical releases were migrated to snapshots.linaro.org,
historical daily and developers' built were not due to concerns with
current disk space availability on snapshots.linaro.org. But both daily
and developers' builds are subject to expiration (lifetime 3 months
max), and with 2 months of snapshots.linaro.org archiving, there's only
one month's worth of builds left on android-build.linaro.org, which
would expire shortly.
*2 Subject to expiration policy, per (*1)
--
Best Regards,
Paul
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
Hi,
On Wed, Feb 1, 2012 at 9:54 PM, Francesco Sarasini <sarasini(a)gmail.com> wrote:
>> The changes are seems to be OK. Can you please add some debugging
>> printk in the driver/input/touchscreen/ads7846.c driver?
> yes, can you tell me what I have to print? only function calls or also
> variable values?
Please add printk to show the value of x, y, before and after the
OMAP3EVM macro. That will give better idea about the touchevent.
NOTE: Please always CC to the list. So that, you may get better tips
from other members.
Bye :)
--
Bharathi Subramanian
A little up :)
-----Original Message-----
From: Alexander Sack [mailto:asac@linaro.org]
Sent: Sun 2/12/2012 2:30 AM
To: HUAU Gabriel
Cc: linaro-android(a)lists.linaro.org; Paul Sokolovsky; ?????? ?????
Subject: [RMX:#] Re: error: Cannot fetch platform/external/replicaisland
Hi,
all Linaro has been very busy at Linaro Connect Q1.12 event last week.
Most are traveling back now. so thanks for being patient for a bit...
(CCed Paul who might be able to help on this one...)
On Tue, Feb 7, 2012 at 11:56 PM, Gabriel Huau <ghuau(a)adeneo-embedded.com> wrote:
> Hi all,
>
> I'm trying to mirror the linaro-android repository but I have some
> problems about the replicaisland repository.
>
> To mirror, I have init the directory :
> repo init -u git://android.git.linaro.org/platform/manifest.git --mirror
>
> And sync :
> repo sync -j1
>
> I tried to git clone directly replicaisland :
>
> $ git clone git://android.git.linaro.org/platform/external/replicaisland
> Cloning into replicaisland...
> fatal: The remote end hung up unexpectedly
>
> Someone can confirm this problem please ?
>
> Thanks,
>
> _______________________________________________
> linaro-android mailing list
> linaro-android(a)lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-android
--
Alexander Sack
Technical Director, Linaro Platform Teams
http://www.linaro.org | Open source software for ARM SoCs
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
We can now start playing with gcc 4.7 prereleases:
https://android-build.linaro.org/builds/~linaro-android/toolchain-4.7-bzr/#…
This is built from the toolchain WG's 4.7 repository; however, at the
moment none of their work has gone in (they just created the
repository by importing the FSF gcc 4.7 branch).
At the moment, this is expected to be both buggy (unreleased code...)
and slow (4.6 based toolchain WG work isn't in...), but it's good to
start finding problems and spotting performance regressions quickly.
ttyl
bero