Hi@all,
the release of A20_SDK_V2.9.5 happened … Don’t forget to do a make mrproper && make init_sdk … also do a make get_toolchain … it is updated to the latest void-linux versions.
Cheers
Thorsten
Hi@all,
the release of A20_SDK_V2.9.5 happened … Don’t forget to do a make mrproper && make init_sdk … also do a make get_toolchain … it is updated to the latest void-linux versions.
Cheers
Thorsten
Hi@all,
the release of A20_SDK_V2.9.4 happened … Don’t forget to do a make mrproper && make init_sdk … also do a make get_toolchain … it is updated to the latest void-linux versions.
Note, that i deprecate some devices, namely Nanopi, Bananapi-Pro and the Olimex. The reason is, that they have contact looses and/or already died.
Also Note, that there`s no base and full image anymore, but not all scripts are fully migrated. As a workaround i would suggest to name the rootfs tarball you want (for example a20_sdk_musl_rootfs.tgz) to a20_sdk_rootfs.tgz and then use a20_sdk_make_sdcard.sh as always. This will be fixed with the next release!
Cheers
Thorsten
There`s an updated version for the a20_sdk toolchain available (see https://sourceforge.net/projects/a20devices/files/). It reflects the latest void-linux (https://voidlinux.org/) changes. This is the first step for the upcoming next release A20_SDK_V2.9.4.
It will be also the first release of the migration path from only glibc based images to glibc and musl images. With A20_SDK_V2.9.5, the split of base and full image will be removed (see also https://tjohann.wordpress.com/2020/11/16/rework-on-a20_sdk-images/)
So stay tuned … a lot of new cool stuff will come 🙂
Cheers
Thorsten
I will rework the actual images to support also musl as an image. The plan is to remove the full images and make the base image to a glibc image. Then add a new musl based image. In the end i will support 2 different libc.
Convert images (from to)
Full Image -> remove
Base Image -> glibc
The new Image -> musl
The change will happen during the next weeks. So with A20_SDK_V2.9.4 the conversion will start.
Cheers
Thorsten
The images for A20_SDK_V2.9.3 are available @sourceforge (https://sourceforge.net/projects/a20devices/)
Cheers & have fun
Thorsten
Hi@all,
the release of A20_SDK_V2.9.3 happened … Don’t forget to do a make mrproper && make init_sdk … also do a make get_toolchain … it is updated to the latest void-linux versions.
Cheers
Thorsten
Hi@all,
i released A20_SDK_V2.9.2 wich support a new device -> https://linux-sunxi.org/Sinovoip_Banana_Pi_M3 . This release also included some bug fixes in the supporter scripts.
Images are uploaded, binpkgs with emacs-gtk* packages are also uploaded.
Normally a new device would lead to a A20_SDK_V2.10.0, but i will also add another device -> https://linux-sunxi.org/Xunlong_Orange_Pi_Zero . The reason for this is the good support of jailhouse hypervisor.
So the update to A20_SDK_V2.10.0 will happen when the Orange Pi Zero is included.
So stay tuned …
Thorsten
I have updated the measurements of the kernel build time on my baalue cluster (see Baalue-Distcc-Repo ).
The linux kernel build config is based on my a20 devices. The only difference between the 2 runs is, that it compiles a kernel on a A20 (Cubietruck) and on a A83T (Cubiertuck-Plus) as the master node. The Cluster (8 A20@Bananapi) is the same, so it`s interesting to see how the master node effects the overall performance.
Cubietruck-Plus:
make CC=distcc -j32 LOADADDR=0x40008000 uImage modules dtbs
real 15m56,545s
user 79m49,928s
sys 20m4,033s
Cubietruck:
make CC=distcc -j32 LOADADDR=0x40008000 uImage modules dtbs
real 68m48,674s
user 81m58,231s
sys 44m3,516s
It`s quite impressing to see the difference. The reason is, that the master node is under full load, because it has to distribute the jobs into the cluster. This takes computation time and therefore the cluster nodes are NOT under full load.
see:
Hi@all,
i released A20_SDK_V2.9.1 wich includes first parts for a new device https://linux-sunxi.org/Sinovoip_Banana_Pi_M3 . Images will follow at the weekend.
Why Bananapi-M3? Because it`s one of the out-of-the-box devices in FreeBSD 🙂
Cheers
Thorsten
Hi@all,
all of my basic integrationstest finished with positive results.
Some common hints:
Cheers
Thorsten