Author: Simon Wise Date: To: dng Subject: Re: [DNG] Dng Digest, Vol 17, Issue 39
On 08/02/16 09:09, KatolaZ wrote: > On Sun, Feb 07, 2016 at 10:49:48PM +0100, Arnt Karlsen wrote:
>
> [cut]
>
>>>
>>> If it is inly a matter of recompiling for armhf with the arm6 flag,
>>> shall we try to put together a devuan for arm6?
>>
>> ..yup, and it is worth the while starting from the Raspian
>> Wheezy flavor a year ago, rather than todays Raspian Jessie.
>> I have one of each ready for guinea pig service. ;o)
>>
>
> The problem is that the old Raspbian wheezy won't boot on pi0, due to
> a firmware problem (I tried that one before trying the tainted jessie,
> obviously...). There is a workaround though, which consists on
> upgrading the firmware to the newest version from a pi1 or a pi2, but
> I haven't tried it.
>
> I really would like to have a devuan armhf port compiled for arm6, to
> get advantage of the FPU. Honestly, it has been a long time since I
> had the whole toolchain installed to cross-compile for arm, but this
> would probably be worth the effort, and convince me to travel a few
> years back in time. There are a lot of people out there using pis, and
> some are already complaining about systemd, and many would love a
> pi-vuan. Any volunteers around? :)
I have a B and a B+ here, though too busy with some other projects to dedicate
serious time to it at the moment I could set them up to build packages at least.
Now they run raspbian wheezy, the B+ with a different kernel to run a nice sound
card. Depending on the ambition simply dropping any of the systemd dependent
gnome and desktop stuff would make sense for these old models, they need a very
light desktop, preferably none. I have used them as media players, directly to
the graphics not via X. Networking is weak, the A or the zero might be better
since they do not add the crappy usb chip but rather expose the tablet-style usb
directly, so may work better with appropriate usb network dongles. But I have
not tested this, maybe I should get a zero. The new rpi2 is not useful to me
since it seems that the way the cores and threading are managed is not good for
audio throughput at all, but maybe messing around and locking cores and process
etc may achieve something???
Wheezy was set up by default to boot in a very manual way, the recommended place
to add services from was often rc.local, so maybe a similar approach was taken
in Jessie. But I have not looked at it.