Arm-dev

arm-dev@lists.centos.org

686 discussions

opening up the armv7hl plague builders (was plague farm)
by Fabian Arrotin 19 May '15

19 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there ! We've all been busy on various things in parallel, but I wanted to give a status update to the list, about those armv7hl nodes that we can use to bootstrap/build CentOS 7. I just tested that the plague setup was running fine (so basically plague-server accepting jobs, and distributing those jobs amongs the builders nodes). We'd like now to open access to that plague build farm. I've just started a wiki page dedicated to this (http://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32) containing some basic info on how to install and configure plague-client. We still have to discuss a good target/mock config files naming convention, including which repo are already available for dev/users. As a reminder, those nodes are currently running Fedora 21, and as plague WebUI needed mod_python, but not available anymore, we currently have no http/web ui that people can have a look at. OTOH, plague-server now sends the build logs/reports fine, and everybody can access the repodata/files/build logs at the following location (just using mod index for now) : http://armv7.dev.centos.org/repodir (for the built packages, including repodata) http://armv7.dev.centos.org/rpmbuild (for the log files) As an example, I submitted blindly all CentOS 7.0.1406 SRPMS to plague, using a f19 as buildroot. If we consider gcc : - - build log is available at http://armv7.dev.centos.org/rpmbuild/centos-f19-7-0-arm/515-gcc-4.8.2-16.el… - - artifact/rpm[s] are available at http://armv7.dev.centos.org/repodir/centos-f19-7-0-arm/gcc/4.8.2-16.el7/arm… If you need/want access, feel free to discuss that on this list, but also to create a bug report on https://bugs.centos.org, in the Buildsys project, category "community buildsys - arm32" Let's discuss what would be the best option for the target names/mock config files, and I can then let $cfgmgmt distribute that to server/builders. Happy Monday ! :-) - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlVQmxsACgkQnVkHo1a+xU4NmACeObf3iINOAUo7sC8k99H+DmlE B6cAmwQsSsTy6+dLqI4OijOUAEpSXUqm =DXgQ -----END PGP SIGNATURE-----

5 6

best kernel for armv7hl ?
by cc35359 gma 14 May '15

14 May '15

Fabian, I dont normally travel to these CentOS mailing lists, however, I wanted to mention about how I shoved Fedora Rawhide on a number of raspberry pis, because i think it would be a highly advantageous idea to push out at least a minimal image for the raspberry pi with the armv7 release for CentOS 7. If not that, at least have a clear path for those wanting it. In my adventures with rawhide on the raspis, i've found that the best way to handle the hardware is by using the kernel actually distributed by the raspi foundation, versus compiling my own. unfortunately there are a few broadcom pieces that make it difficult. In order to get rawhide running, it was a very simple process. 1. mount the fedora image 2. make an sd card paritioned how you want it (i dont use swap on sd card, so just 500 mb for /boot, and the rest for /. 3. rsync the data to the sd card, except the boot. 4. copy the boot directory from the raspi's git with the necessary firmware. 5. copy the kernel libraries. 6. i created a dracut initrd because i needed to have dm-crypt available because i normally encrypt the / partition myself. 7. modify fstab, boot.txt, cmdline.txt as necessary 8. boot, and its magic. I dont mind repeating the process for a centos image if help is needed, perhaps creating a scripted method to generate the images for the future would be something to look into. So that was a lot of rambling, but long story short, i can assist you with a raspberry pi image based on my fedora creations if we feel that centos can provide such an image. otherwise once the armv7 packages are ready, i can create documentation and a potential "offsite" image if there are legal reasons for not supplying it. thanks for listening, -David

2 3

best kernel for armv7hl ?
by Fabian Arrotin 11 May '15

11 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, As Jim used kernel 4.0.0-1 for the aarch64 (alpha) build (announced today), I was wondering what would be the best kernel to use/target for armv7hl. Is patching the el7 kernel the way to go, or do we prefer/want to use the same one everywhere if possible (so also using 4.0.0-1, and tracking the aarch64 version). Cheers, - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlVQ5ZgACgkQnVkHo1a+xU6BFgCfbIaaP1kpWUKHTIKuW55cUiaS 4NYAn3cjUVikbTqYvXllMb4l4B9PMSZO =xI8e -----END PGP SIGNATURE-----

2 1

Release of CentOS-7 (alpha candidate) for AArch64 platforms
by Jim Perrin 11 May '15

11 May '15

We are pleased to announce the public alpha release of CentOS Linux 7 for AArch64 compatible hardware. This is the initial alpha release based on CentOS Linux 7 1503 ( Rebuilt from Red Hat Enterprise Linux 7.1 sources ), with architecture and modifications patching as necessary. Because this hardware is very new and support for it is still evolving, there is no expectation for kernel ABI compatibility. Additionally, until the alpha period ends both the OS repository and the Updates repository are subject to change. This release was built on an X-Gene system from Applied Micro. We are working to test against other platforms to ensure broad compatibility. ======== Download You can find the install tree and repositories at http://buildlogs.centos.org/centos/7/os/aarch64/ While the build is in alpha, we are not releasing full isos as you would traditionally find with the x86_64 builds. Please use the boot.iso which has been pre-configured for a network install, or pxe from a locally hosted mirror of the installation tree. We plan to make disk images available soon to help vendors bootstrap their platforms. ============ Installation Installation guides and documentation will be provided via the CentOS wiki, at http://wiki.centos.org/SpecialInterestGroup/AltArch/AArch64 Because several packages are not yet available, the group information has been reduced and the only available installation option is 'minimal'. If you perform kickstart based installs, please note the only available group is currently 'Core'. We will improve upon this throughout the alpha process. ============ Contributing The AArch64 effort is meant to be a community effort as part of the AltArch SIG (http://wiki.centos.org/SpecialInterestGroup/AltArch) and we welcome enthusiasts and vendors to contribute patches, fixes, documentation, etc. In the AArch64 Extras repository, we have provided the mock package and dependencies so that community members can more easily contribute, as well as testing their own builds locally. Please submit patches, fixes, etc to the Arm-Dev list (http://lists.centos.org/mailman/listinfo/arm-dev) for discussion and acceptance. We encourage vendors to come and join this effort, we have a lose organization focused on the alternative architectures build process and welcome interaction at the group level. Please get in touch with me (jperrin(a)centos.org) or K Singh ( kbsingh(a)centos.org ) to find out more details. The wider CentOS Ecosystem is also welcome to engage with us, both at the project and code level. If you are working with a project that interfaces, manages or develops on top of CentOS, specially in the virtualization, cloud, container and infrastructure management areas - we would love to have you guys get involved. While we don't have a lot of resources, we are working with a few vendors to build up a community resource pool that we would encourage other projects to share their development, testing and delivery around CentOS Linux for aarch64. In the next few days, we'll be adding a branch to git for modified packages so that patches are available to the community, as well as providing a repository for the debug-info packages. ================================== Coming Soon // Future Improvements * Rebase to 4.1rc kernel * Improve package and group availability * Add additional hardware support * Disk images to support install via dd -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

1 0

a plague farm ?
by Karanbir Singh 07 May '15

07 May '15

hi guys, We have a few nodes that can be used, public facing, for builds - and we have Howards's bootstrap image in place. With that in mind, can we as a group help with the wider armv7 effort at this point ? One option might be to see if we can get this image loaded onto the nodes we have from online.net ? and then get a plague builder thread on each node. We can host the plague server on a different machine, as long as network latency isnt too high we should be fine. This would then allow people to setup and submit jobs without needing the entire setup at their own place. Plague, since koji isnt suiteable here, yet. Plus we have some plague expertise already ( we still use it for CentOS-5 builds ). Regards, -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

11 39

EPEL 7 packages for arm
by Troy Dawson 06 May '15

06 May '15

I'm not sure if this question belongs here or on a fedora mailing list. Or maybe it's already been discussed somewhere and I just missed it. Is there a plan on what to do with EPEL7 packages, for arm? Is Fedora thinking of adding arm to the EPEL7 build arch? Is CentOS planning on hosting a repo that contains those? If so, will it be all EPEL7 or just a subset? Right now, if you had all the CentOS7 arm packages compiled and ready to go, you wouldn't be able to create a build/plague machine, because mock, and several of it's dependencies, are in EPEL7, and not RHEL7. Anyway, if this has already been discussed, could someone point me at it. If it hasn't, where would be the appropriate place to discuss it? Thanks Troy

4 3

32Gb mSD cards
by Robert Moskowitz 30 Apr '15

30 Apr '15

If anyone in the US needs some 32GB mSD cards, I just got this sale notice: http://view.newsletter.rakuten.com/?j=fe8815707c6d017473&m=fe8d12717c62077d… I have bought a number of items from rakuten and am happy with their service and items.

1 0

ARM Development Hardware
by Mandar Joshi 26 Apr '15

26 Apr '15

Hello everybody, I was hoping to get some suggestions from you guys about which ARM development hardware to purchase. The hardware will have just one purpose; compiling and testing CentOS. With this in mind I'm leaning towards something Quad Core, good amount of RAM,NAND Flash, SATA and that has a heatsink . Does SATA seem reasonable or will a USB HDD serve just as well? I live in Mumbai, India. So, I might not have all the options you guys have. I might be able to get Raspberry Pi, BeagleBoard, Cubie Board, Radxa, Banana Pi or Odroid from these guys https://www.crazypi.com/ or http://www.greenindiaelectronics.com/ If anyone from India is reading this, please do suggest reliable sellers. Thanks Mandar Joshi

5 9

Cross Compiling vs Native Compiling
by Mandar Joshi 16 Apr '15

16 Apr '15

Hello everybody, This part is mentioned in my GSoC proposal but I thought I should bring it up here as well. How do you feel about taking a slightly different approach to ARM development? Viz. Cross Compiling. We could use existing infrastructure x86,x86_64 servers to build packages for ARMv7. This will require writing some plugins for Yum, Mock & Koji based on work done by msalter from RedHat. I am referring to this post https://www.redhat.com/archives/fedora-buildsys-list/2009-July/msg00000.html The way I see it, cross compiling will get packages compiled faster and would be easy to setup. We won't have to rely of ARM Hardware from online.net A thing to ponder over is whether this fits in the CentOS policy. Regards Mandar Joshi

4 5

5 armv7 nodes available from online.net
by Fabian Arrotin 12 Apr '15

12 Apr '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi guys, Just to let you know that people from http://labs.online.net/ are "sponsoring" a centos account on their ARM cloud setup and we currently have 5 nodes with the following specs : - - 4-cores ARMv7 CPU : ARMv7 Processor rev 2 (v7l), Marvell Armada 370/XP (Device Tree) - - 2GB of RAM - - 1 Gbit/s network link - - 50GB local storage (seems to be in fact a ndb device served from a storage node using SSD disks) The nodes are installed with their Fedora 21 custom image. We're all busy with the CentOS 7 (tag 1503) rebuild and QA tests, but we'd have to discuss the best way to use those armv7 nodes. I'll also try to see what would be the best option for a central storage, but probably nfs is the only option, or iscsi lun served from one of those nodes, acting as both the admin node and jump host (only one public/reserved IP in our current account, but we can then reach the other nodes, so not a real issue) Thanks to Online.net for that account ! - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlUUCuEACgkQnVkHo1a+xU47LgCfVbGVuIvSj59aBeWGcW4ARGi1 lEIAni+Ah+LnuspY2Db2hoBGbD1sRGey =j876 -----END PGP SIGNATURE-----

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev