Arm-dev August 2017

arm-dev@lists.centos.org

14 participants
15 discussions

Gigabyte MP30-AR0
by Gordan Bobic 12 Nov '19

12 Nov '19

Hi, I am toying with the idea of getting a Gigabyte MP30-AR0 board (despite the insanely exorbitant price tag). Has anyone got the aarch64 CentOS working on one of those? Any special instructions? Also, if I get the ISO, is it bootable on aarch64? Does the installer work? Or does the image have to be used like on 32-bit ARM? Thanks. Gordan

10 197

Request for a new package: raspberrypi-vc
by Jordi Sanfeliu 13 Sep '17

13 Sep '17

Hello, Following the Fabian Arrotin recommendation, I open here the request to include the 'raspberrypi-vc' package into the CentOS 7 EPEL repository, or in the main tree. This package includes a command called 'vcgencmd' which offers a set of interesting values of the Raspberry Pi board; e.g. its temperature. Check here <http://www.elinux.org/RPI_vcgencmd_usage> for more information. I've downloaded the SRPM package from here <http://www.squeezecommunity.org/repo/fedora/24/pi/SRPMS/raspberrypi-vc-2016…>, and I realized that it was pretty easy to build on a full-updated CentOS 7 (kernel 4.4.14-v7). The following are the small modifications I made on the .spec file to accomplish it: --- raspberrypi-vc.spec 2016-07-05 23:23:13.000000000 +0200 +++ raspberrypi-vc.spec.ok 2016-07-13 12:14:39.494059817 +0200 @@ -21,12 +21,12 @@ Patch1: raspberrypi-vc-EGL-dep.patch # dtoverlay -BuildRequires: libfdt-devel >= 1.4.1-501.gitbeef80b%{?dist} +##BuildRequires: libfdt-devel >= 1.4.1-501.gitbeef80b%{?dist} Requires: libfdt >= 1.4.1-501.gitbeef80b%{?dist} BuildRequires: cmake, gcc-c++ -ExclusiveArch: armv6hl armv7hnl +ExclusiveArch: armv7hl %description Libraries, utilities and demos for the Raspberry Pi BCM2835/6 SOC GPU @@ -34,7 +34,7 @@ %package libs Summary: Libraries for accessing the Raspberry Pi GPU -Requires: %{name}-firmware >= 20150212git47bd0f0-501 +##Requires: %{name}-firmware >= 20150212git47bd0f0-501 #Provides: libEGL.so #Provides: libGLESv1_CM.so The build generated successfully the following packages: [root@rpi3 rpmbuild]# l -R RPMS/ RPMS/: total 8 drwxr-xr-x 2 root root 4096 Jul 26 15:59 armv7hl drwxr-xr-x 2 root root 4096 Jul 13 12:23 noarch RPMS/armv7hl: total 1352 -rw-r--r-- 1 root root 552156 Jul 13 12:22 raspberrypi-vc-libs-20160705-501.git0b8c195.el7.centos.armv7hl.rpm -rw-r--r-- 1 root root 340184 Jul 13 12:22 raspberrypi-vc-libs-devel-20160705-501.git0b8c195.el7.centos.armv7hl.rpm -rw-r--r-- 1 root root 244960 Jul 13 12:23 raspberrypi-vc-static-20160705-501.git0b8c195.el7.centos.armv7hl.rpm -rw-r--r-- 1 root root 241332 Jul 13 12:23 raspberrypi-vc-utils-20160705-501.git0b8c195.el7.centos.armv7hl.rpm RPMS/noarch: total 30688 -rw-r--r-- 1 root root 31420584 Jul 13 12:23 raspberrypi-vc-demo-source-20160705-501.git0b8c195.el7.centos.noarch.rpm The installation worked finely: # [root@rpi3 armv7hl]# rpm -ivh raspberrypi-vc-utils-20160705-501.git0b8c195.el7.centos.armv7hl.rpm raspberrypi-vc-libs-20160705-501.git0b8c195.el7.centos.armv7hl.rpm Preparing... ################################# [100%] Updating / installing... 1:raspberrypi-vc-libs-20160705-501.################################# [ 50%] 2:raspberrypi-vc-utils-20160705-501################################# [100%] Then a simple command to get the temperature: [root@rpi3 ~]# vcgencmd measure_temp temp=47.2'C Thanks. -- Jordi Sanfeliu FIBRANET Network Services Provider http://www.fibranet.cat

4 5

CentOS 7.4.1708 rebuild status
by Fabian Arrotin 08 Sep '17

08 Sep '17

Hi guys, You're probably aware that upstream RHEL 7.4 was released last week, so the x86_64 rebuild started in the following days (https://seven.centos.org/2017/08/centos-linux-7-1708-based-on-rhel-7-4-sour…) On the armv7hl/armhfp side I started (as usual) to rebuild gcc, wait (long time), then glibc. Those rebuilds finished on saturday morning, so since that day, the armhfp builders have been busy rebuilding the 700+ SRPMs. At this stage, more than 530 pkgs were already rebuilt (https://armv7.dev.centos.org/built.html), and some are excluded as not covered for armhfp, which is always expected But this time, we have packages that have failures where they were able to build fine, or other new issues. Example of package failing now to build is mariadb : it builds, but it fails at the tests stage in mariadb itself, so we'll probably need to verify what/why/how Other new "interesting" issue is that some pkg are now relying on external BuildRequires, like devtools-6 package set. As Johnny explained it in his blog post for x86_64, it was built for x86_64, so there is no issue at all. But on the armhfp side, it wasn't, and worse, it will not work : https://armv7.dev.centos.org/rpmbuild/c71708-pass-1/19769-devtoolset-6-gcc-… => "*** Configuration armv7hl-redhat-linux-gnu7E not supported" Any help on trying to solve those issues is welcome PS : myself being busy on my SysAdmin job, so not having a lot of time to spend on armhfp, and also diving into "Summer Holidays without internet connectivity" mode soon ... -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

5 12

java-1.8.0 not building on armv5
by Jacco Ligthart 02 Sep '17

02 Sep '17

Hi Fabian, I fail to build java-1.8.0-openjdk on armv5. I get errors regarding gdb: + gdb -q /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.141-2.b16.el7.arm/openjdk/build/jdk8.build/images/j2sdk-image/bin/java + tee gdb.out Reading symbols from /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.141-2.b16.el7.arm/openjdk/build/jdk8.build/images/j2sdk-image/bin/java...done. (gdb) Signal Stop Print Pass to program Description SIGSEGV No No Yes Segmentation fault (gdb) Signal Stop Print Pass to program Description SIGILL No No Yes Illegal instruction (gdb) (gdb) Breakpoint 1 (javaCalls.cpp:1) pending. (gdb) >>>(gdb) Starting program: /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.141-2.b16.el7.arm/openjdk/build/jdk8.build/images/j2sdk-image/bin/java -version No source file named javaCalls.cpp. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". warning: Probes-based dynamic linker interface failed. Reverting to original interface. Cannot access memory at address 0xc2400000 Missing separate debuginfos, use: debuginfo-install glibc-2.17-157.el7.4.redsleeve.armv5tel libgcc-4.8.5-11.el7.armv5tel zlib-1.2.7-17.el7.armv5tel (gdb) quit A debugging session is active. This is all related to a new section about gdb in the SPEC-file: # Make sure gdb can do a backtrace based on line numbers on libjvm.so gdb -q "$JAVA_HOME/bin/java" <<EOF | tee gdb.out handle SIGSEGV pass nostop noprint handle SIGILL pass nostop noprint set breakpoint pending on break javaCalls.cpp:1 commands 1 backtrace quit end run -version EOF grep 'JavaCallWrapper::JavaCallWrapper' gdb.out Now my question, does this build on armv7 ? Jacco

2 7

Kernel ?
by Nicolas 01 Sep '17

01 Sep '17

Hi Does someone use a bananapi on centos ? I'm using it for a long time, and I'm still on 4.2 kernel. Every time I try to install a newer I got a lot of errors during install, or yum get stuck on "cleaning..". The last time I success to install it, it's not very stable... So if someone got feedback, or feedback about any card on an uptodate kernel ? Thanks Nicolas

8 17

add support PMU ver 3 and apei initial support for aarch64
by Khuong Dinh 30 Aug '17

30 Aug '17

Hi Jim, In addition to the patches that I just recently sent, can you please help to integrate the attached patches to sig-altarch7-aarch64. + 1041-misc-PMU-fix-and-add-support-PMU-ver3.patch This is a roll up of the following upstreamed patch for adding miscellaneous fix for PMU and add PMU ver 3 c0f7f7a : perf: xgene: Add support for SoC PMU version 3. e35e0a0 : perf: xgene: Move PMU leaf functions into function pointer structure. 838955e : perf: xgene: Parse PMU subnode from the match table. + 1042-apei-initial-support-aarch64.patch This is a roll up of the following upstreamed patch for adding APEI support for aarch64. - ACPI/APEI: Handle GSIV and GPIO notification types: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/patch/d… - ACPI / APEI: Add missing synchronize_rcu() on NOTIFY_SCI removal: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/patch/d… - ACPICA: ACPI 6.1: Updates for the HEST ACPI table: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/patch/i… - 9f9a35a : ACPI / APEI / ARM64: APEI initial support for ARM64. + config-centos-sig-enable-initial-apei-support-for-aarch64.patch Enable CONFIG_ACPI_APEI, CONFIG_ACPI_APEI_GHES, CONFIG_ACPI_HED Best regards, Khuong Dinh

2 2

-29.el7 in GIT
by Phong Vo 25 Aug '17

25 Aug '17

Hi Jim, It looks like aarch64 CentOS kernel has been updated to -29.el7. Can we get the source tree updated in GIT also? Thanks, -Phong

1 0

Re: [Arm-dev] owncloud on armv7hl
by Nicolas Repentin 18 Aug '17

18 Aug '17

Hi ;) If you wan, you can add the following repo file with wget to /etc/yum.repos.d/ http://repo.shivaserv.fr/centos/7/shivaserv-various.repo It's my own repo, I've put php70w on it ;) The upload is not very big (above 6Mbits/s), but packages are not big. If it works I can tell you how to compile. Le 07/08/2017 à 22:01, Robert Moskowitz a écrit : > Much appreciated. Do I erase the php 5.4 I installed? > > On 08/07/2017 03:58 PM, Nicolas Repentin wrote: >> I will check tomorrow if i can try to compile some php7 packages and >> if it works i will give it to you. >> I just need to restart my pi2 on centos :p >> >> >> Le 7 août 2017 21:56:14 GMT+02:00, Robert Moskowitz >> <rgm(a)htt-consult.com> a écrit : >> >> >> >> On 08/07/2017 03:53 PM, Nicolas Repentin wrote: >>> I got my packages for amd64 from webtatic : >>> https://mirror.webtatic.com/yum/el7/ >>> >>> They provides srpm packages, maybe you can compil arm version >>> from srpm with rpmbuild.. i've done it a lot for other packages >>> (http://repo.shivaserv.fr) >> >> And you are a better one than I. Pretty much any time I try for >> an rpmbuild it is a bit of a disaster. >> >> If I don't get some reasonable answers, I will punt over to F26 >> for my cloud work for now. >> >>> >>> >>> Le 7 août 2017 21:41:23 GMT+02:00, Robert Moskowitz >>> <rgm(a)htt-consult.com> a écrit : >>> >>> It wasn't until F21 that there were standard build process >>> for Fedora-arm. From 18 - 20, they were all custom builds. >>> And F20: >>> >>> http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/20/Ever… >>> >>> Has php 5.5 >>> >>> I just went looking for Centos 7.4, but >>> http://mirror.centos.org/centos/ only has to 7.3... >>> >>> Bob >>> >>> On 08/07/2017 02:17 PM, Nicolas Repentin wrote: >>>> I don't know :s does the arm package exists on f19 ? I >>>> think centos 7 is based on f19. >>>> >>>> >>>> >>>> Le 7 août 2017 19:42:29 GMT+02:00, Robert Moskowitz >>>> <rgm(a)htt-consult.com> a écrit : >>>> >>>> >>>> >>>> On 08/07/2017 01:27 PM, Nicolas Repentin wrote: >>>>> Oh, yes >>>>> On my amd64 centos i have added php70 from another >>>>> repo. Maybe try to check if there is the same for arm? >>>> >>>> I suspect I could get it from a Fedora-arm repo, but >>>> other than being compiled on armv7hl, will it cause >>>> other problems with components? >>>> >>>> I see that F26 has php 7.1: >>>> >>>> http://mirrors.kernel.org/fedora/releases/26/Server/armhfp/os/Packages/p/ >>>> >>>> But is ok to install this? What other challenges might >>>> it cause? >>>> >>>>> >>>>> >>>>> >>>>> Le 7 août 2017 19:22:09 GMT+02:00, Robert Moskowitz >>>>> <rgm(a)htt-consult.com> a écrit : >>>>> >>>>> On 08/06/2017 02:40 PM, Nicolas Repentin wrote: >>>>> >>>>> Hi Don't bother with the package, install a >>>>> web and database server, and install owncloud >>>>> or nextcloud directly with the tar.gz from the >>>>> site. It will be easier, and you will be able >>>>> to update easily from the web interface to the >>>>> futures versions after. >>>>> >>>>> >>>>> >>>>> nextcloud needs PHP7 not the PHP5.4 in Centos7. >>>>> >>>>> At >>>>> https://docs.nextcloud.com/server/11/admin_manual/installation/php_55_insta… >>>>> >>>>> It says that Nextcloud 11 supports 5.4, but recommends 5.5 and how to >>>>> get it from the SCL library. Is this working for armv7hl? >>>>> >>>>> Nextcloud 12 requires php 5.6. >>>>> >>>>> Ouch. >>>>> >>>>> Bob >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Nicolas >>>> >>>> >>>> -- >>>> Nicolas >>> >>> >>> -- >>> Nicolas >> >> >> -- >> Nicolas >

3 10

xgene, xgene-v2 ethernet, pcc, apei driver update
by Khuong Dinh 17 Aug '17

17 Aug '17

Hi Jim, In addition to the patches that I recently sent, can you please help to integrate the attached patches to sig-altarch7-aarch64. + 1043-update-xgene-xgene-v2-ethernet-pcc-apei-driver.patch This is a roll up of the following upstreamed patch for updating - xgene ethernet: 326dde3: xgene: Check all RGMII phy mode variants 32d0f78: phy: Add helper function to check phy interface mode 8aba847: drivers: net: xgene: Fix redundant prefetch buffer cleanup 61c759c: drivers: net: xgene: Workaround for HW errata 10GE_10/ENET_15 eaef62a: drivers: net: xgene: Add frame recovered statistics counter for errata 10GE_8/ENET_11 a844e7d: drivers: net: xgene: Workaround for HW errata 10GE_4 ca6d550: drivers: net: xgene: Add rx_overrun/tx_underrun statistics 2d07d8e: drivers: net: xgene: Extend ethtool statistics 6f22a7a: drivers: net: xgene: Remove unused macros 089f97c: drivers: net: xgene: Refactor statistics error parsing code 3f5a2ef: drivers: net: xgene: Remove redundant local stats d09d362: drivers: net: xgene: Use rgmii mdio mac access 8ec7074: drivers: net: phy: xgene: Add lock to protect mac access ae1aed9: drivers: net: xgene: Protect indirect MAC access 4902a92: drivers: net: xgene: Add workaround for errata 10GE_8/ENET_11 7eac928: drivers: net: xgene: Add workaround for errata 10GE_1 0a0400c: drivers: net: xgene: Fix Rx checksum validation logic 11623fc: drivers: net: xgene: Fix wrong logical operation e026e70: drivers: net: xgene: Fix hardware checksum setting 4b72436: drivers: net: phy: xgene: Fix mdio write 9aea777: drivers: net: xgene: Fix crash on DT systems - xgene-v2 ethernet drivers: net: xgene-v2: Fix compile warning. This patch is to fix the compile warning in kernel 4.5 when backporting xgene-v2 ethernet from upstream to CentOS 7.3. - pcc: ecfc159: mailbox: pcc: Fix crash when request PCC channel 0 - APEI: bdb9458: ACPI: APEI: Enable APEI multiple GHES source to share a single external IRQ. acpi: Fix proper return code for function acpi_gsi_to_irq. This patch is backported from: upstreamed patch 1dc482b: ACPI / irq: Fix return code of acpi_gsi_to_irq() to CentOS. It was also been ACKed in : https://patchwork.kernel.org/patch/8075651/ Best regards, Khuong Dinh

2 1

Fwd: Re: Does openssl pick low level interface or high level interface to do encrypt?
by Robert Moskowitz 11 Aug '17

11 Aug '17

How does OpenSSL work on ARM? Do any arms have hardware crypto? thanks -------- Forwarded Message -------- Subject: Re: [openssl-users] Does openssl pick low level interface or high level interface to do encrypt? Date: Thu, 10 Aug 2017 15:16:09 +0000 From: Salz, Rich via openssl-users <openssl-users(a)openssl.org> Reply-To: Salz, Rich <rsalz(a)akamai.com>, openssl-users(a)openssl.org To: openssl-users(a)openssl.org <openssl-users(a)openssl.org> What OpenSSL does is not necessarily obvious. The INSTALL document talks about the no-asm configuration option. Details about what the assembler code does in terms of optimization are only available by reading the source code comments in the various Perl files that generate the assembler, mostly. On x86, the assembly code uses the CPUID instruction (see the OPENSSL_ia32cap.pod manpage) to determine if various instructions (AES, SSE, MMX, etc) are available and will use them if so. For other processors, similar tests are performed if at all possible. I have added this to the FAQ -- Senior Architect, Akamai Technologies Member, OpenSSL Dev Team IM: richsalz(a)jabber.at Twitter: RichSalz *From:*- JinsongJi [mailto:jjsbear@hotmail.com] *Sent:* Wednesday, August 09, 2017 9:09 AM *To:* openssl-users(a)openssl.org *Subject:* [openssl-users] Does openssl pick low level interface or high level interface to do encrypt? Hi, For one simple operation: openssl enc -aes-256-cbc -salt -in foo.txt -out foo.enc Does openssl pick classic implementation or AES-NI implementation to do this encrypt? Does any user/application always pick classic implementation for AES operation regardless of AES-NI improves speed much? Is there any document about this interface selection? Thanks, Jinsong

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev August 2017