Re: [Dev] Developer Reference Platform 16.03 differences compared to Debian
Hi Riku, On 29 April 2016 at 16:06, Riku Voipiowrote: > One of the goals of RPB is to follow that our changes go back > upstream. For the next RPB release, a more polished report is planned. > But to get things started, here's a sample - and to use as baseline to > compare progress for the 16.06 release. The list of packages is > collected from db410/alip image with distrodelta script[1]. This lists > the packages that do not become from Debian (Jessie release) or Debian > backports: There's a few glitches that we need to sort out. For example, we carry 1.0.2g (not 1.0.2d) which has a patch to use arm64 assembly. > New packages not in Debian: > > 96boards-artwork: 0.6-0linaro1 > 96boards-tools: 0.5 > optee-client: 1.0.1+git5+g89f25ce-1.linarojessie.1 > glshim: 0.41+git20150911.42a7739-0.linarojessie.1 > linaro-artwork: 0.6-0linaro1 > linaro-default-settings: 0.3-0linaro1 > linaro-overlay: 1112.8 > wcnss-config: 1.8 > > Changed packages: > > alsa-lib: 1.0.28-1+linaro1.linarojessie.1 >* add UCM config file for HDMI and HiFi on DB410c >* add UCM config file for HDMI on IFC6410 > > chromium-browser: 47.0.2526.16-1.6.linarojessie.1 >* seccomp and namespace fixes >* patches to compile on arm64/armhf > > firmware-nonfree: 20160110-1.linarojessie.1 >* ti-connectivity (updates for HiKey): > - Include wl18xx-fw-4 firmware > - Add TIInit_11.8.32.bts for bluetooth support > > isc-dhcp: 4.3.3-8~linaro1 >* Reverting requirement for debhelper >= 9.20151220 >* Upload to make it work with latest systemd: > - https://bugs.96boards.org/show_bug.cgi?id=271 > > linux: 4.4.0.linaro.104-1.linarojessie.1 >* See kernel changes report (TBD) > > No-changes Backports: > > apparmor: 2.10-2.linarojessie.1 > binutils: 2.25.90.20160101-1.linarojessie.1 > gdb: 7.10-1.linarojessie.1 > gyp: 0.1+20150913git1f374df9-1.linarojessie.1 > java-common: 2:1.8-53.linarojessie.1 > nodejs: 4.2.2~dfsg-1.1.linarojessie.1 > openssl: 1.0.2d-1.linarojessie.1 > systemd: 228-2.4.linarojessie.3 > sysvinit: 2.88dsf-59.2.linarojessie.1 > util-linux: 2.27.1-1.linarojessie.1 > x265: 1.7-4~bpo8+1.linarojessie.1 > xorg: 1:7.7+11.linarojessie.1 > xorg-server: 2:1.17.3-2.linarojessie.2 > xserver-xorg-video-fbdev: 1:0.4.4-1.linarojessie.1 > xserver-xorg-video-freedreno: 1.4.0-1.linarojessie.1 > > > [1] https://github.com/suihkulokki/distrodelta with command > distrodelta -o Debian 'Debian Backports' > ___ > Dev mailing list > d...@lists.96boards.org > https://lists.96boards.org/mailman/listinfo/dev Cheers, -- Fathi Boudra Engineering Manager | Builds and Baselines, Release Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
[IMPORTANT] Regression after android-review.linaro.org upgrade to Gerrit 2.12.2
Hello, Summary: Your SSH username on https://android-review.linaro.org will now match Linaro username (first.last) after the next login. You local repository clones need to be updated for new username. Detailed description: https://android-review.linaro.org was the first Gerrit server in Linaro, when there were no central LDAP user database yet. As a result, there were free-form SSH usernames used, instead of the later standard first.last as used on all the other Gerrit servers. This inconsistency was a subject of background concern for Systems team, but of course not something having enough priority to "fix". However, Gerrit 2.12.2 upgrade started tonight uncovered following issue: Gerrit tries to synchronize its SSH username setting with LDAP, and fails, as Gerrits own rules disallow changing of username. The symptom of this is error "Authentication temporary unavailable" when a user with "old" SSH username tries to login via browser. While this can be classified as a Gerrit bug (and previous versions were smart enough), we'll unlikely find any timely solution to keep things as they are. So, it makes sense to take a chance of cleaning up username and making this server follow standard username conventions. Consequently: 1. All usernames which don't match "first.last" pattern are reset. 2. If you are affected, you won't be able to perform SSH operations (like git clone/push) until you login via web interface. 3. On the next login via web interface, it will be set to LDAP's "first.last" value. 4. You will need to update remotes of your existing git clones to new username (or alternatively, re-clone). 5. If you already use "first.last" SSH username, you're unaffected. The list of users affected is given below. While it seems long, majority of enrties there are for people no longer at Linaro, or for community accounts (which didn't work since we switched to LDAP anyway). If you need further assistance, please open a ticket at https://servicedesk.linaro.org/servicedesk/customer/portal/4 . Thanks, Paul username:Ng username:pfefferz username:asac username:james_w username:fgiff username:jserv username:mabac username:deeptik username:cyang username:mpoirier username:ndec username:mwaddel username:mansson username:Sachin username:vishalbhoj username:suapapa username:fabo username:pabhishek username:cnxsoft username:amitdanielk username:patrikryd username:sangwook username:ericm username:pundiramit username:glandium username:eazyigz username:tixy username:danilo username:john username:nytowl username:tony_tu username:Sangwook username:StefanEkenberg username:uichi username:plars username:zyga username:ruppi username:ebenpor username:jhkim username:Annamalai username:markoncomputer username:Claude username:tianhongwang username:rchand00 username:omarrmz username:aviksil username:nvl1109 username:a0132810 username:pelya username:krtaylor username:developer4563 username:yusufbu username:dzinman username:arussello username:mdupuy username:williamcharles username:aorth username:lanaczko username:rmcc username:kcrudup username:kelvin username:angelsl username:unixmanlinuxboy username:Quiter username:sourxsunny username:pbeeler username:anmar username:wucongdonglai username:bambi username:rperier username:sgt username:roalex username:vishveshwarbhat username:therbom username:rajagopalvenkat username:winner00 username:ramesh username:abelloni username:sparksco username:fahadkdi username:ryanharkin username:axelfagerstedt username:nocoast username:milo username:fcarpenter username:hongbozhang username:fahadk username:pelya2 username:janjic username:dpervushin username:qoowater username:cerial username:tinojantony username:stephan username:kishoreboddu username:nuclearmistake username:SanjasdfsafsffaySinghsdfasfRawat username:donvigo username:tinojgit username:afarah username:mechmetal username:akbennett username:c username:sikuner username:wasungkim username:stevanr username:deqiang username:anilkumar username:willnewton username:codeart username:lrabiet username:Bintian username:bintian username:vishalbhoj2 username:tusharbehera username:jbergsag username:tgall username:amitkhare username:neo username:paramanands username:sumit username:danielt username:help username:XavierHsu username:Serban username:Z username:koenkooi (127 rows) -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Developer Reference Platform 16.03 differences compared to Debian
On 04/29/2016 07:06 AM, Riku Voipio wrote: > One of the goals of RPB is to follow that our changes go back > upstream. For the next RPB release, a more polished report is planned. > But to get things started, here's a sample - and to use as baseline to > compare progress for the 16.06 release. The list of packages is > collected from db410/alip image with distrodelta script[1]. This lists > the packages that do not become from Debian (Jessie release) or Debian > backports: > [snip...] Interesting. When can we expect to see a similar list for CentOS and/or Fedora? -- ciao, al --- Al Stone Software Engineer Linaro Enterprise Group al.st...@linaro.org --- ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [Dev] Developer Reference Platform 16.03 differences compared to Debian
On Fri, Apr 29, 2016 at 11:05 AM, Nicolas Dechesnewrote: > On Fri, Apr 29, 2016 at 3:56 PM, Ricardo Salveti > wrote: >> >>> wcnss-config: 1.8 >>> optee-client: 1.0.1+git5+g89f25ce-1.linarojessie.1 >>> glshim: 0.41+git20150911.42a7739-0.linarojessie.1 >> >> We should be able to get these in debian. > > wcnss-config shouldn't go upstream, imho. at least not in its current > form. it does 2 things: > 1. create a single WLAN mac address based on some pseudo unique ID > available on the board > 2. loads/starts WLAN and BT > > #1 is not strictly needed, as the driver would default to using a > random MAC. and I don't think what we do is nice enough to be > upstream... we can discuss more.. > > #2 we at least need to wait for the underlying kernel drivers to reach > mainline before we upstream (which should be soon), the method to > start/load the firmware will change. That is true, forgot this package was mainly responsible for setting up the mac address for the board. >>> Changed packages: >>> >>> alsa-lib: 1.0.28-1+linaro1.linarojessie.1 >>>* add UCM config file for HDMI and HiFi on DB410c >>>* add UCM config file for HDMI on IFC6410 >> >> Good one for upstreaming. >> >> Nico, did you get to send those to the upstream alsa/ucm project? > > yeah, we talked about that. Fathi said he will take care of it, he was > planning to submit the config files for Bugglegum, we will do them at > the same time. We might need some clean up first though. Great, thanks for the update. Cheers, -- Ricardo Salveti ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [Dev] Developer Reference Platform 16.03 differences compared to Debian
On Fri, Apr 29, 2016 at 3:56 PM, Ricardo Salvetiwrote: > >> wcnss-config: 1.8 >> optee-client: 1.0.1+git5+g89f25ce-1.linarojessie.1 >> glshim: 0.41+git20150911.42a7739-0.linarojessie.1 > > We should be able to get these in debian. wcnss-config shouldn't go upstream, imho. at least not in its current form. it does 2 things: 1. create a single WLAN mac address based on some pseudo unique ID available on the board 2. loads/starts WLAN and BT #1 is not strictly needed, as the driver would default to using a random MAC. and I don't think what we do is nice enough to be upstream... we can discuss more.. #2 we at least need to wait for the underlying kernel drivers to reach mainline before we upstream (which should be soon), the method to start/load the firmware will change. > >> Changed packages: >> >> alsa-lib: 1.0.28-1+linaro1.linarojessie.1 >>* add UCM config file for HDMI and HiFi on DB410c >>* add UCM config file for HDMI on IFC6410 > > Good one for upstreaming. > > Nico, did you get to send those to the upstream alsa/ucm project? yeah, we talked about that. Fathi said he will take care of it, he was planning to submit the config files for Bugglegum, we will do them at the same time. We might need some clean up first though. ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [Dev] Developer Reference Platform 16.03 differences compared to Debian
On Fri, Apr 29, 2016 at 10:21 AM, Nicolas Dechesnewrote: > On Fri, Apr 29, 2016 at 3:06 PM, Riku Voipio wrote: >> One of the goals of RPB is to follow that our changes go back >> upstream. For the next RPB release, a more polished report is planned. >> But to get things started, here's a sample - and to use as baseline to >> compare progress for the 16.06 release. The list of packages is >> collected from db410/alip image with distrodelta script[1]. This lists >> the packages that do not become from Debian (Jessie release) or Debian >> backports: > > good stuff. Can this be added to Jenkins as part of the images builds? > or does it have to run on the target after the fact? That would indeed be quite cool to have! Cheers, -- Ricardo Salveti ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [Dev] Developer Reference Platform 16.03 differences compared to Debian
On Fri, Apr 29, 2016 at 10:06 AM, Riku Voipiowrote: > One of the goals of RPB is to follow that our changes go back > upstream. For the next RPB release, a more polished report is planned. > But to get things started, here's a sample - and to use as baseline to > compare progress for the 16.06 release. The list of packages is > collected from db410/alip image with distrodelta script[1]. This lists > the packages that do not become from Debian (Jessie release) or Debian > backports: Thanks for doing and publishing the report. > New packages not in Debian: > > 96boards-artwork: 0.6-0linaro1 > 96boards-tools: 0.5 > linaro-artwork: 0.6-0linaro1 > linaro-default-settings: 0.3-0linaro1 > linaro-overlay: 1112.8 Expect these ones to be in our repo for a bit more. Tools might be useful outside of it, but the others are custom related artwork and settings. > wcnss-config: 1.8 > optee-client: 1.0.1+git5+g89f25ce-1.linarojessie.1 > glshim: 0.41+git20150911.42a7739-0.linarojessie.1 We should be able to get these in debian. > Changed packages: > > alsa-lib: 1.0.28-1+linaro1.linarojessie.1 >* add UCM config file for HDMI and HiFi on DB410c >* add UCM config file for HDMI on IFC6410 Good one for upstreaming. Nico, did you get to send those to the upstream alsa/ucm project? > chromium-browser: 47.0.2526.16-1.6.linarojessie.1 >* seccomp and namespace fixes >* patches to compile on arm64/armhf What is the upstreaming state here? > firmware-nonfree: 20160110-1.linarojessie.1 >* ti-connectivity (updates for HiKey): > - Include wl18xx-fw-4 firmware https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816350 > - Add TIInit_11.8.32.bts for bluetooth support Got in contact with the maintainer, and there is no interest in pushing this to the upstream linux-firmware tree. We could try doing that, otherwise it might need to end up in a different package. > isc-dhcp: 4.3.3-8~linaro1 >* Reverting requirement for debhelper >= 9.20151220 >* Upload to make it work with latest systemd: > - https://bugs.96boards.org/show_bug.cgi?id=271 > > linux: 4.4.0.linaro.104-1.linarojessie.1 >* See kernel changes report (TBD) This will always be around, used for development. > No-changes Backports: > > apparmor: 2.10-2.linarojessie.1 > binutils: 2.25.90.20160101-1.linarojessie.1 > gdb: 7.10-1.linarojessie.1 > gyp: 0.1+20150913git1f374df9-1.linarojessie.1 > java-common: 2:1.8-53.linarojessie.1 > nodejs: 4.2.2~dfsg-1.1.linarojessie.1 > openssl: 1.0.2d-1.linarojessie.1 > systemd: 228-2.4.linarojessie.3 > sysvinit: 2.88dsf-59.2.linarojessie.1 > util-linux: 2.27.1-1.linarojessie.1 > x265: 1.7-4~bpo8+1.linarojessie.1 > xorg: 1:7.7+11.linarojessie.1 > xorg-server: 2:1.17.3-2.linarojessie.2 > xserver-xorg-video-fbdev: 1:0.4.4-1.linarojessie.1 > xserver-xorg-video-freedreno: 1.4.0-1.linarojessie.1 Thanks, -- Ricardo Salveti ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [Dev] Developer Reference Platform 16.03 differences compared to Debian
On Fri, Apr 29, 2016 at 3:06 PM, Riku Voipiowrote: > One of the goals of RPB is to follow that our changes go back > upstream. For the next RPB release, a more polished report is planned. > But to get things started, here's a sample - and to use as baseline to > compare progress for the 16.06 release. The list of packages is > collected from db410/alip image with distrodelta script[1]. This lists > the packages that do not become from Debian (Jessie release) or Debian > backports: good stuff. Can this be added to Jenkins as part of the images builds? or does it have to run on the target after the fact? ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Developer Reference Platform 16.03 differences compared to Debian
One of the goals of RPB is to follow that our changes go back upstream. For the next RPB release, a more polished report is planned. But to get things started, here's a sample - and to use as baseline to compare progress for the 16.06 release. The list of packages is collected from db410/alip image with distrodelta script[1]. This lists the packages that do not become from Debian (Jessie release) or Debian backports: New packages not in Debian: 96boards-artwork: 0.6-0linaro1 96boards-tools: 0.5 optee-client: 1.0.1+git5+g89f25ce-1.linarojessie.1 glshim: 0.41+git20150911.42a7739-0.linarojessie.1 linaro-artwork: 0.6-0linaro1 linaro-default-settings: 0.3-0linaro1 linaro-overlay: 1112.8 wcnss-config: 1.8 Changed packages: alsa-lib: 1.0.28-1+linaro1.linarojessie.1 * add UCM config file for HDMI and HiFi on DB410c * add UCM config file for HDMI on IFC6410 chromium-browser: 47.0.2526.16-1.6.linarojessie.1 * seccomp and namespace fixes * patches to compile on arm64/armhf firmware-nonfree: 20160110-1.linarojessie.1 * ti-connectivity (updates for HiKey): - Include wl18xx-fw-4 firmware - Add TIInit_11.8.32.bts for bluetooth support isc-dhcp: 4.3.3-8~linaro1 * Reverting requirement for debhelper >= 9.20151220 * Upload to make it work with latest systemd: - https://bugs.96boards.org/show_bug.cgi?id=271 linux: 4.4.0.linaro.104-1.linarojessie.1 * See kernel changes report (TBD) No-changes Backports: apparmor: 2.10-2.linarojessie.1 binutils: 2.25.90.20160101-1.linarojessie.1 gdb: 7.10-1.linarojessie.1 gyp: 0.1+20150913git1f374df9-1.linarojessie.1 java-common: 2:1.8-53.linarojessie.1 nodejs: 4.2.2~dfsg-1.1.linarojessie.1 openssl: 1.0.2d-1.linarojessie.1 systemd: 228-2.4.linarojessie.3 sysvinit: 2.88dsf-59.2.linarojessie.1 util-linux: 2.27.1-1.linarojessie.1 x265: 1.7-4~bpo8+1.linarojessie.1 xorg: 1:7.7+11.linarojessie.1 xorg-server: 2:1.17.3-2.linarojessie.2 xserver-xorg-video-fbdev: 1:0.4.4-1.linarojessie.1 xserver-xorg-video-freedreno: 1.4.0-1.linarojessie.1 [1] https://github.com/suihkulokki/distrodelta with command distrodelta -o Debian 'Debian Backports' ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: JITs and 52-bit VA
For info Google v8 Javascript uses the bottom bit to tag pointers. One problem with this mechanism though is that the pointers can only be used directly with unscaled offset memory access instructions (LDUR/STUR). So in particular, no LDP/STP. On 28 April 2016 at 22:41, Wookeywrote: > +++ Adhemerval Zanella [2016-04-28 12:07 -0300]: > > I do not think this issue is inherent to all JIT implements, but rather > to > > luajit with its NaN-tagging scheme [1] which packs different types of > objects > > in a 8-byte. > > Other jits use the same/similar schemes (mozilla's ionmonkey is one > AIUI). Not sure how many others do this, or how many JITs do it a > different way. BUt it is certainly wider than just luajit. > > Wookey > -- > Principal hats: Linaro, Debian, Wookware, ARM > http://wookware.org/ > > ___ > linaro-dev mailing list > linaro-dev@lists.linaro.org > https://lists.linaro.org/mailman/listinfo/linaro-dev > > -- Alexandre Rames +44 1223 400 25452 ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev