Arm-dev

arm-dev@lists.centos.org

1 participants
685 discussions

misc support for watchdog amba-pl011 cppc
by Khuong Dinh 21 Jul '17

21 Jul '17

Hi Jim, Can you please help to integrate the attached patches to sig-altarch7-aarch64. + 1040-misc-support-watchdog-amba-pl011-cppc.patch This is a roll up of the following upstreamed patch for adding miscellaneous support and fix for watchdog, amba-pl011, cppc. c3c1e29 : watchdog: sbsa: Set WDOG_HW_RUNNING, when watchdog is already running. e05e80e : watchdog: sbsa: Use max_hw_heartbeat_ms instead of max_timeout. 3fbfe92 : watchdog: change watchdog_need_worker logic. ee14288 : watchdog: Introduce WDOG_HW_RUNNING flag. 664a392 : watchdog: Introduce hardware maximum heartbeat in watchdog core. fb32e9b : watchdog: Make set_timeout function optional. 7d05587 : tty: amba-pl011: Fix spurious TX interrupts. 5448f14 : ACPI / CPPC: Don't return on CPPC probe failure. Best regards, Khuong Dinh

1 0

Rebasing the Qualcomm QDF2400 Networking Patch
by Brian Stinson 19 Jul '17

19 Jul '17

Hi folks, Attached is a rebase of a patch submitted to arm-dev that adds support for the networking devices in the QDF2400. It appears that this patch didn't make it into the previous build of the ARM kernel. This patch should apply to HEAD on https://git.centos.org/log/sig-altarch!kernel.git/sig-altarch7-aarch64 Any chance we can get this built and included in a set of install media soon? This patch mentions a lack of hardware for testing the option CONFIG_NET_VENDOR_QUALCOMM, how would we test this? Cheers! -- Brian Stinson

1 1

Sun8i h3 ott
by omar laureano 19 Jul '17

19 Jul '17

Hello Im new to this forum and i have an ottv bix brabd ghia model gac 303 is a h3 board and say its name is dolphin i want to instal centos but i cant make it boot any advice it uses uboot

1 0

systemd-networkd and DHCP v6
by Ian Pilcher 11 Jul '17

11 Jul '17

Is anyone using the $SUBJECT combination? I have a CentOS 7 (userland)/Banana Pi firewall, and I've been having an issue where dhclient fails to renew my IPv6 address. The root cause seems to be that the initial lease is obtained before the B'Pi syncs its system time, and ISC dhclient is unable to deal with large wall clock changes: https://bugzilla.redhat.com/show_bug.cgi?id=1093803 (I haven't seen this problem with IPv4. It seems like there's some sort of workaround for this issue in the IPv4 case somewhere in the network scripts, chrony, or dhclient itself.) I just tried using systemd-networkd, instead of the legacy network service, but it appears that systemd-networkd-219-30.el7.9.armv7hl will never send a "dhcp6 solicit" packet, even when "DHCP=yes" (or "DHCP=ipv6") is set in the relevant .network file. I've verified with tcpdump that a RHEL 7 x86_64 VM *does* send a dhcp6 solicit, but there is absolutely no IPv6 UDP traffic coming from the Banana Pi. I'm back to the legacy network service for now, with a workaround to forcibly renew the IPv6 lease once chrony has synced the time. This is my home firewall, so opportunity for messing around with the network configuration is limited. I am wondering, though, if anyone at all is using systemd-networkd with DHCPv6 on CentOS 7 ARM? -- ======================================================================== Ian Pilcher arequipeno(a)gmail.com -------- "I grew up before Mark Zuckerberg invented friendship" -------- ========================================================================

2 1

kernel-debug-debuginfo missmatch?
by Richard Henwood 11 Jul '17

11 Jul '17

Hi All, I was looking for kernel-debug-debuginfo and I noticed that the most recent version available for AArch64 is 4.5.0-23 [1], but my kernel is on 4.5.0-25. I have worked around on this occation (by just renaming the /usr/src/debug directory,) but I wanted to raise it here in case it is a previosly unknown issue (or an opportunity for me to understand better how things work). Best regards,Richard 1. http://debuginfo.centos.org/7/aarch64/kernel-debug-debuginfo-4.5.0-23.el7.a…

2 4

Success with Avnet PicoZed (Xilinx Zynq), Suggestions for building python-matplotlib
by Paul Graham 06 Jul '17

06 Jul '17

Hi, I wanted to let you know that I have had success with running the CentOS 7 userland on an Avnet PicoZed module using the Xilinx-provided source for the kernel and U-Boot available on their GitHub project (using the "xilinx-v2016.1.01" tag for the kernel source and the "xilinx-v2016.1" tag for U-Boot). We have been running Fedora 20 ARM on these modules (with the same kernel and version of U-Boot) for a little while and thought we would try out CentOS for various reasons (longer term support, similarity to RHEL 7, etc.). One challenge I have run into, though, is that our software depends on "python-matplotlib" and a few other packages that haven't been prebuilt for CentOS 7 (but were available under Fedora 20 ARM). I was able to successfully build a number of these packages from source RPMs, but building "python-matplotlib" is starting to get a bit complicated, especially, with what appears to be some circular build dependencies among the source packages. For example, here is one set of dependencies leading to what appears to be a circular dependency: python-matplotlib -> gtk2-devel gtk2 SRPM (for gtk2-devel) -> pango-devel pango SRPM (for pango-devel) -> harfbuzz-devel harfbuzz SRPM (for harfbuzz-devel) -> graphite2-devel graphite2 SRPM (for graphite2-devel) -> asciidoc asciidoc SRPM (for asciidoc) -> graphviz graphviz SRPM (for graphviz)-> gtk2-devel, pango-devel, etc. Similarly, there is also the following circular dependency, starting with asciidoc: ... asciidoc -> dblatex dblatex SRPM (for dblatex) -> texlive-collection-xetex texlive SRPM (for texlive-collection-xetex) -> gtk2-devel, pango-devel, etc. Any suggestions for how to deal with these apparent circular dependencies? I have been building the RPMs by hand with "rpmbuild --rebuild <source RPM>" trying to work through the dependencies and installing as many binary packages as are available. Clearly, there must be some way to deal with this since these packages have been built successfully for other architectures. Thanks, Paul

1 0

/boot full!
by Robert Moskowitz 05 Jul '17

05 Jul '17

My /boot is full! I had left it at the 'default' of 524MB and after all the kernel updates, it is finally full. I would say this is a bug in update-boot, not to trim down /boot old images. So I had to delete the 201 and 202 files out of /boot to install this latest 4.9.34-203. But what about removing the directories: dtb-4.4.34-201.el7.armv7hl dtb-4.4.42-202.el7.armv7hl Can those also just be deleted? thanks

2 2

Building CentOS7 userland for ARM64 server boards
by Scott Branden 29 Jun '17

29 Jun '17

Hello, I'm new to CentOS and looking for any useful instructions/documentation to read up on. I would like to learn about how the rootfs has been generated for CentOS. The Alternative Architecture Centos SIG already prepared a tar archive containing a CentOS 7 userland for ARM64 server boards: curl -sSL -o CentOS-7-aarch64-rootfs-7.3.1611.tar.xz http://mirror.centos.org/altarch/7/isos/aarch64 Could someone provide instructions on the steps take to build this exact image? Thanks, Scott

2 5

Grub not updating boot configs
by Mike Calderwood 27 Jun '17

27 Jun '17

Hey guys. This is probably going to be a really dumb question, but a) I only have limited familiarity with Grub2 and b) I really don't want to have to rebuild my SD card image from scratch...again. I have a Pine64 running 7.3.1611 aarch64, and it started out on kernel 3.10.101. I've issued yum update after yum update, and it finally dawned on me that it wasn't ever booting into the new kernels I was installing. I have 5 of the 4.x kernels installed, but it's never even attempted to boot into them. I've dug around a little bit, and here's what I can see so far: 1) By RPM list, I don't even have a 3.x kernel installed anywhere. It was installed during the initial system image in some way outside of RPM/yum, and it hasn't been removed in the time since. 2) I don't have a grub2.cfg file like my x86_64 systems have. I have a symlink at /etc/grub2-efi.cfg that is supposed to point to ../boot/efi/EFI/centos/grub.cfg, but that doesn't exist either. 3) If I run grub2-mkconfig, I can get a seemingly-valid grub2.cfg file that only references the 4.x kernels I have installed. I put that file at the symlink target from #2 and rebooted, but it apparently had zero impact. It rebooted just fine...into 3.10.101. So my question boils down to this: what exactly am I missing here that's preventing this from updating kernels correctly? Thanks for the help. Mike

3 3

add support mpt3sas 33xx 32xx chipsets and miscellaneous fix for pca955x, pm80xx, mpt3sas
by Khuong Dinh 22 Jun '17

22 Jun '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. + 1038-add-support-mpt3sas-33xx-32xx-chipsets.patch This patch is to add LSI vendor ID and device ID for LSI 33xx and LSI 32xx SAS IO controllers. This will also enable mpt3sas driver to support these chipsets. This patch was partially backport for Centos 7.3 to enable those pciids and we don't need other code. (Ref: b130b0d mpt3sas: Added support for high port count HBA variants) + 1039-misc-fix-pca955x-pm80xx-mpt3sas.patch This is a roll up of the following upstreamed patch for adding miscellaneous fix for pca955x, pm80xx, mpt3sas. aace34c leds: pca955x: Correct I2C Functionality. e83596b pm80xx: Remove bogus address masking in pm8001_ioremap(). 83c3d34 mpt3sas: Fix panic when aer correct error occurred. The following are additional fix for mpt3sas. scsi: mpt3sas: Fix BDI reregistration race with sas3ircu utility. Best regards, Khuong Dinh

2 1

← Newer
1
...
24
25
26
27
28
29
30
...
69
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev