On Sun, 10 Apr 2016, Gregory Nowak wrote:

> My concern here is that packages compiled for armv6 wouldn't take
> full advantage of the rpi2 CPU, in the same way that packages
> compiled for the rpi2 don't take full advantage of the rpi3 CPU. Is
> this concern valid? If yes, then I'm against making such a move, and
> suggest that if possible, we stick to separate packages for rpi0/1,
> rpi2, and rpi3. I understand this will take extra build cycles and
> extra storage, but I personally think that's worth it. Just my
> $0.01.

we will likely have optimized builds at least specific for rpi2 and
rpi3. Parazyd's SD image is a good preview for what beta will look
like, while on the mid-long term we are working on a CI that will
targed native builds for all most popular embedded devices.

here my current wishlist:

cubieboard2 efikamx mini-x trimslice riot odroid-w-devkit nanopi2
chromebook-arm-veyron bbb cubox luna rpi-tft odroid-xu odroid-u2
chromebook-arm-exynos banana-pro cubox-i utilite rpi odroid-xu3
odroid-c chromebook-arm-acer banana-pi cubietruck usbarmory rpi2
odroid-w odroid-c2

there is some excellent work on Kali Linux that covers these targets,
integration of their kernel configs and patches in the devuan-sdk has
already started.

ciao