Le 26/10/2015 20:52, Andreas Färber a écrit :
Am 18.10.2015 um 21:24 schrieb Johannes Kastl:
On 18.10.15 Frank Kunz wrote:
I am not aware that there is a Leap version for the Raspberry Pi. Not even
considered.
Is there any Leap support planned for the ARMs?
I hope there will be, once it is released and the whole process is
going.
According to Dirk, there are indeed no plans for armv7l or armv6l.
Too bad. :(
Apart from no one volunteering to bootstrap the build, e.g. using 13.2,
we are currently very limited on armv7l build power (our Arndale boards
broke, need to find time to debug) and the time before the Leap
repository gets frozen for release seems insufficient to get a full
build done under the circumstances.
We could disable armv7 Factory build for a week or so, to be able to build
Leap. That was done for previous releases.
armv6l building under linux-user emulation would be even slower
(déjà-vu: 13.2) and is getting only little love in Tumbleweed already.
armv6 is only (or almost) for RPi 1. So, Tumbleweed for this one seems ok to me.
But we support lots of armv7 boards, so not having it for leap sounds very bad.
:(
AArch64 is supported by Leap, but it seems there are not much boards available
for a reasonable price.
Tumbleweed is ok if you want to have latest and greatest, but
when an update stops the ARM board working (so seen with kernel
4.2 update) it would be better to have something more stable for
"productive" environments.
+1
A +1 does not get a stable distro release done... ;-)
You are of course free to try rebuilding Leap in a private OBS
installation and report whether everything builds and works.
It is a very big task and not very easy to do. (Is there a how-to somewhere?)
If you know companies that would sponsor more virtualization-capable
ARMv7-A hardware (Cortex-A7/-A15/-A17) or AArch32-capable ARMv8-A
hardware, ideally supported in the mainline kernel and with sufficient
RAM, feel free to reach out to them.
Cortex-A7 is designed to be low power and is not powerful. (RPi2 is a quad-core
A7 with 1 GB of RAM and using it as an OBS worker is quite bad (done in
packman).)
I use a SabreLite (iMX6) as an OBS worker for a while and it is very good.
(Stable and powerful). But this is a quad-core cortex-A9 (not
virtualization-capable).
Do you really need virtualization? If you want to run qemu (not chroot), you
could just do it on cortex-A9. No?
One solution could be to allow some ARMv7 boards to connect to OBS (using VPN).
But I think OBS worker network is closed (not able to reach Internet), for
security reasons.
Guillaume
Regards,
Andreas
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
