NetBSD ARM64 Images Now Available with SMP for Raspberry Pi 3, Some NanoPi Boards, and Pine64 Boards

ROCK64 NetBSD ARM64

NetBSD on Arm started in 2014 with the release of version 7.0, and last year device tree support was implemented and tested on some Allwinner H3 boards. But apparently, so far NetBSD only supported 32-bit Arm, with initial support for 64-bit Arm (ARM64) committed last April, but good progress has been made, and NetBSD ARM64 bootable firmware images are now available with SMP (multi-core) support. Eight different NetBSD ARM64 images can be downloaded: Generic NetBSD 64-bit image for Raspberry Pi 3 and NVIDIA Tegra X1 Two images for FriendlyELEC boards namely NanoPi NEO2 and NEO Plus2 boards Five images for the following Pine64 boards and hardware platforms Pine A64/A64+ Pine A64-LTS / Sopine with baseboard Pine H64 Pinebook laptop ROCK64 (ROCK64Pro not yet supported) The supported hardware matrix shows most features are supported, but there are still a few things missing such as GPU, crypto and MIPI CSI on all platforms, USB OTG is still experimental, and PCIe support is …

Red Hat Enterprise Linux 7.4 Now Fully Supports Arm servers

When hardware vendors announced Arm based servers they also claim support for operating systems such as Ubuntu 16.04 LTS and Red Hat Enterprise Linux, so I assumed software support was more or less where it needed to be with regards to Arm server. But apparently, it may not have been so, as Red Hat only announced full support for Arm servers in Red Hat Enterprise Linux for ARM a few days ago. It also started with SBSA (Server Base System Architecture) specifications in 2014, that aimed to provide a single operating platform that works across all 64-bit ARMv8 server SoCs that complies with the said specification. Red Hat then released a developer preview of the OS for silicon and OEM vendors in 2015, and earlier this week, the company released Red Hat Enterprise Linux 7.4 for Arm, the first commercial release for this architecture. RHEL 7.4 for Arm come with Linux 4.11 kernel and support networking drivers from various vendors …

MACCHIATOBin based DIY ARM Desktop, DragonBoard 820c based DIY ARM Laptop (Video)

2017 may be the year of the (ARM based) Linux desktop, sort of. We’ve already seen GIGABYTE ARM development PC powered by a Socionext SC2A11 Synquacer 24-core ARM Cortex A53 processor that will be available in December, and apparently working fairly well already. But there are even more options, as Bernhard Rosenkränzer (Bero) from the Linaro Mobile Group, and unofficial Linaro superstar, has decided to create his own ARM based desktop and laptop, based on respectively MACCHIATOBin board with a Marvell ARMADA 8040 quad core Cortex  A72 processor, and DragonBoard 820c board with a Qualcomm Snapdragon 820 quad core Krait processor. Since MACCHIATOBin board complies with mini-ITX form factor, he could simply use off the shelf parts with a standard desktop case with power supply, NVIDIA or AMD Radeon graphics card, 16GB memory modules, and a 2 TB SSD drive. The AMD Radeon card fried due to overheating, so the demo was made with an NVIDIA card driven by Nouveau …

GIGABYTE SynQuacer 96Boards Enterprise Platform is Powered by SocioNext SC2A11 24-core ARMv8 SoC

GIGABYTE, Socionext and Linaro have partnered to design a software development platform compliant with 96Boards Enterprise specifications, with GIGABYTE taking care of manufacturing the hardware based on Socionext SC2A11 processor, while Linaro will provide support via 96Boards community. GIGABYTE SynQuacer platform preliminary specifications (based on photos and SC2A11 specifications): SoC – Socionext SynQuacer SC2A11 24x ARM Cortex-A53 MPCore cores @ up to 1GHz, with 32KB/32KB I/D L1 cache, 256 KB L2 cache, and 4MB L3 cache (5W power consumption) System Memory – 4x DIMM slots for 64-bit DDR4-2133Mbps with ECC up to 64GB Storage – 32GB Samsung KLMBG2JENB-B041 eMMC 5.1 flash + 2x SATA interfaces Connectivity – 2x Gigabit Ethernet (RJ45) with IPSec Network Offload Engine USB – 2x USB 3.0 ports on motherboard (via Renesas D720201), 4x USB ports on front panel via expansion board Audio – 1x microphone input, 1x speaker output on front panel Expansion – 1x PCie x16 slot (limited to 4-lanes), 2x PCIe x4 slots, other …

How ARM Nerfed NEON Permute Instructions in ARMv8

This is a guest post by blu about an issue he found with a specific instruction in ARMv8 NEON. He previously wrote an article about OpenGL ES development on Ubuntu Touch, and one or two other posts. This is not a happy-ending story. But as with most unhappy-ending stories, this is a story with certain moral for the reader. So read on if you appreciate a good moral. Once upon a time there was a very well-devised SIMD instruction set. Its name was NEON, or formally — ARM Advanced SIMD — ASIMD for short (most people still called it NEON). It was so nice, that veteran coders versed in multiple SIMD ISAs often wished other SIMD ISAs were more like NEON. NEON had originated as part of the larger ARM ISA version 7, or ARMv7, for short. After much success in the mobile and embedded domains, ARMv7 was superseded by what experts acknowledged as the next step in the evolution …

SolidRun MACCHIATOBin is Another Marvell ARMADA 8040 Networking Mini-ITX Board

We’ve already seen SolidRun is working on a Marvell ARMADA 8040 quad core Cortex A72 community board for networking and storage applications, but based on a picture taken at Linaro Connect, the company is also working on a similar board with extra connectivity options called MACCHIATOBin. Apart from the picture, there’s no info on the web about this board, so we’ll have to derive specs from the photo, the community board features, and info provided by Marcin Juszkiewicz, so all details are preliminary and subject to change: SoC – ARMADA 8040 (88F8040) quad core Cortex A72 processor @ up to 2.0 GHz System Memory – 1x DDR4 DIMM up to 16GB RAM Storage – 3x SATA 3.0 port + micro SD slot Connectivity – 1x Gigabit RJ45 port, 1x SFP SGMII @ 2.5Gbps, 2x 10Gbps copper (RJ45) with auto switchover to dual SFP+ Expansion – 1x PCIe-x4 3.0 slot, Marvell TDM module header USB – 1x USB 3.0 port, 1x …

How to Run Ubuntu 16.04 Aarch64 (64-bit ARM) Cloud Images on Your Intel/AMD Linux Computer with QEMU

With the recent launch of several low cost Cortex A53 development boards, 64-bit ARM hardware is now pretty common and inexpensive, but if you want to run 64-bit ARM code on your x86 Linux computer, Riku Voipio, a software engineer working for Linaro, wrote some instructions to run Ubuntu 16.04 Aarch64 Cloud image in QEMU. Ubuntu cloud images are “the official Ubuntu images and are pre-installed disk images that have been customized by Ubuntu engineering to run on public clouds that provide Ubuntu Certified Images, Openstack, LXD, and more. ”  So the instructions are also useful if you want to easily try such packages on 64-bit ARM platform. I’ve tried those instructions myself on my Ubuntu 14.04 machine with and AMD FX8350 processor, and they worked pretty well, and the only things I had to find out by myself was to install a recent version of qemu. First, we’ll need to install qemu & cloud-utils, and download QEMU EFI firmware  …

64-bit ARM (Aarch64) Instructions Boost Performance by 15 to 30% Compared to 32-bit ARM (Aarch32) Instructions

Yesterday was quite an eventful day with the launch of two low cost 64-bit ARM development boards, namely Raspberry Pi 3 and ODROID-C2, and as usual there were some pretty interesting discussions related to the launch of the boards in the comments section. One of the subject that came is that while Raspberry Pi 3 board is using a 64-bit processor, the operating systems are still compiled with 32-bit instructions (Aarch32) and even optimized for ARMv6, and they intend to keep it that way according to Eben Upton interview: Eben readily admits that not all the capabilities of the new parts are going to be used at launch, however. “Although it is a 64‑bit core, we’re using it as just a faster 32-bit core,” he reveals about the Pi 3’s central processing unit. “I can imagine there’d be some real benefits [to 64-bit code]. The downside is that you do really create a separate world. To access that benefit, you’d …