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'
On Fri, Apr 29, 2016 at 3:06 PM, Riku Voipio riku.voipio@linaro.org 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?
On 29/04/16 14:06, 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:
That looks pretty good for keeping us honest!
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
Given the roles of linaro-default-settings and linaro-overlay perhaps these might want special treatment.
Should we show a file count as well? In the case of settings perhaps even count files in /etc separately to others.
Daniel.
On Fri, Apr 29, 2016 at 10:06 AM, Riku Voipio riku.voipio@linaro.org 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:
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:
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,
On Fri, Apr 29, 2016 at 10:21 AM, Nicolas Dechesne nicolas.dechesne@linaro.org wrote:
On Fri, Apr 29, 2016 at 3:06 PM, Riku Voipio riku.voipio@linaro.org 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,
On Fri, Apr 29, 2016 at 3:56 PM, Ricardo Salveti ricardo.salveti@linaro.org 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.
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.
On Fri, Apr 29, 2016 at 11:05 AM, Nicolas Dechesne nicolas.dechesne@linaro.org wrote:
On Fri, Apr 29, 2016 at 3:56 PM, Ricardo Salveti ricardo.salveti@linaro.org 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:
- 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,
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?
Hi Riku,
On 29 April 2016 at 16:06, Riku Voipio riku.voipio@linaro.org 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:
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:
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 Dev@lists.96boards.org https://lists.96boards.org/mailman/listinfo/dev
Cheers,
On 30 April 2016 at 08:25, Fathi Boudra fathi.boudra@linaro.org wrote:
Hi Riku,
On 29 April 2016 at 16:06, Riku Voipio riku.voipio@linaro.org 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:
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.
It's not a glitch, we have libbsl 1.0.2d is in 16.03 images.
Riku
On 29 April 2016 at 17:05, Nicolas Dechesne nicolas.dechesne@linaro.org wrote:
On Fri, Apr 29, 2016 at 3:56 PM, Ricardo Salveti ricardo.salveti@linaro.org 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.
Maybe with a little bit of cleanup but yes these are low hanging fruits.
wcnss-config shouldn't go upstream, imho. at least not in its current form. it does 2 things:
- 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..
The problem is common, no-one can bother an extra chip to store a mac address anymore. The ugliness tends to be board specific, so perhaps the mac address can be generated in the firmware and exported via device-tree?
Riku
On Mon, May 2, 2016 at 8:39 AM, Riku Voipio riku.voipio@linaro.org wrote:
#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..
The problem is common, no-one can bother an extra chip to store a mac address anymore. The ugliness tends to be board specific, so perhaps the mac address can be generated in the firmware and exported via device-tree?
it should be possible to do that in the open source firmware (LK), so yes, we should be able to do it, it sounds like a good idea.
nico
-
Al Stone -
Daniel Thompson -
Fathi Boudra -
Nicolas Dechesne -
Ricardo Salveti -
Riku Voipio