Hello Android Team,
For this past weekend, there was scheduled an LDAP authentication
upgrade for review.android.git.linaro.org - sorry, it wasn't announced
to the list, because it should be pretty transparent change, so I just
got an ack from Vishal on IRC.
However, the migration was postponed last-minute because new auth
setup requires having SSL on review.android.git.linaro.org, and we lack
it there. It's not enabled because it has pretty deep 5-level domain
name, we never had such a wildcard certificate, and apparently never
ordered a dedicated certificate for it. During last year or so we
actually gave up many 4-level domain names, by switching to use dashes
as separators instead of dots. That's more cost-effective and much
easier to maintain and avoid situation with expired certificates, etc.
So, what we'd like to do is migrate Android services to contemporary
Linaro naming convention either. It would be:
review.android.git.linaro.org -> android-review.linaro.organdroid.git.linaro.org -> android-git.linaro.org
Note that older names will remain active and will be supported
indefinitely. How it will look like, is that if you access
review.android.git.linaro.org via web browser, you will be
automatically redirected to android-review.linaro.org. Access via
gerrit, git, ssh will work as before.
Overall, the upgrade should be seamless, but as there will be several
moving parts, there may be risk of something breaking for short periods
of time. So, we would like to make sure that there're no concerns and
that e.g. end of next week is good time to proceed.
Thanks,
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, Amit
I see following warnings when boot master builds, do you have any idea
about such thing?
[ 26.253969] init: write_file: Unable to open
'/sys/class/android_usb/android0/enable': No such file or directory
[ 26.253991] init: write_file: Unable to open
'/sys/class/android_usb/android0/idVendor': No such file or directory
[ 26.254010] init: write_file: Unable to open
'/sys/class/android_usb/android0/idProduct': No such file or directory
[ 26.254031] init: write_file: Unable to open
'/sys/class/android_usb/android0/functions': No such file or directory
[ 26.254049] init: write_file: Unable to open
'/sys/class/android_usb/android0/enable': No such file or directory
What's changed in master?
Anything we need to update for these files access?
--
Best Regards,
Yongqin Liu
---------------------------------------------------------------
#mailing list
linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org>
http://lists.linaro.org/mailman/listinfo/linaro-android
Hi,
I tried to download the source code of LCR 15.05 and noticed there
are two type:
reference-lcr
member-lcr
For member-lcr, I got access DENIED when clone local manifest. So
my question is how can I get the access to this private git?
Let me know if this is not correct place to ask this question. Thanks.
Regards
Yin, Fengwei
share it in linaro-android mailing list, so that others could try it and
might have better options.
On 9 June 2015 at 10:45, Vishal Bhoj <vishal.bhoj(a)linaro.org> wrote:
>
>
> On 9 June 2015 at 06:46, YongQin Liu <yongqin.liu(a)linaro.org> wrote:
>
>> Thanks Vishal, this mail is really in time!
>>
>>
>> On 8 June 2015 at 14:23, Vishal Bhoj <vishal.bhoj(a)linaro.org> wrote:
>>
>>> Hi,
>>>
>>> Most of you might already be knowing this. If you already have a version
>>> of source say AOSP in a folder "mydroid" and you want to repo sync code
>>> base from a vendor, you can do this:
>>>
>>> repo init -u $MANIFEST_URL --reference=<path/mydroid>
>>> repo sync
>>>
>>> It will reuse the previous git objects and only download and store the
>>> new git objects. This way a lot of space is saved.
>>>
>>> Another way to get code downloaded faster is:
>>>
>>> repo init -u $MANIFEST_URL --depth=1
>>> repo sync -jX -c
>>>
>>> This way it will only download the relevant branch with only last git
>>> commit history of the project. Once this is done, you can do a repo init
>>> with "--depth" option
>>>
>> here I think it should --depth=0
>>
>>> and then repo sync -c for the relevant project you are interested in to
>>> have the complete history of that branch. The size of .repo folder was
>>> reduced to 6 GB from the original 16GB size.
>>>
>>>
>> And we can use the group option, with "-darwin,-mips,-x86" will not
>> download the toolchain binary for x86/mips, it will save us some space too.
>>
> +1. -notdefault can be included as well.
>
>>
>> --
>> Best Regards,
>> Yongqin Liu
>> ---------------------------------------------------------------
>> #mailing list
>> linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org>
>> http://lists.linaro.org/mailman/listinfo/linaro-android
>>
>
>
--
Best Regards,
Yongqin Liu
---------------------------------------------------------------
#mailing list
linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org>
http://lists.linaro.org/mailman/listinfo/linaro-android
I plan on moving gralloc for Mali into it's own repo an wondering
whereabouts in the source tree it should be placed by the manifest?
Possibilities are
/hardware/arm/mali/
/external/mali/
/mali/
Within whatever directory is chosen I plan on having source for all the
versions of mali so, e.g.
/hardware/arm/mali/r5p0-06rel0/gralloc
/hardware/arm/mali/r5p1-00rel0/gralloc
/hardware/arm/mali/r5p1-06rel1/gralloc
With the aim being that the correct one gets chosen to match whatever
driver version is in the kernel. I also plan similar for vendor tarball
contents, so hopefully we get builds where the three pieces are
guaranteed to have matching version (kernel module/gralloc/binary blob)
--
Tixy
Hi Guys,
I have been investigating this for hours and found that the "--abi"
parameter seems has been dropped from CTS console.
In the manual it says:
http://source.android.com/compatibility/android-cts-manual.pdf
--abi 32/64 On 64-bit devices, run the test against only the 32-bit or
64-bit ABI
However for the CTS package I use, whatever it comes from Linaro or Google:
http://testdata.validation.linaro.org/cts/android-cts-5.1-armv8.ziphttps://dl.google.com/dl/android/cts/android-cts-5.1_r1-linux_x86-arm.zip
it prompted that:
Failed to run command: com.android.tradefed.config.ConfigurationException:
Could not find option with name abi
I tried this on Juno in LAVA, as well as locally on my Nexus 5 phone, both
failed. So if abi selection has been dropped by Google then that manual is
outdated.
Ideas?
Thanks.
Botao