similar to: CentOS-7 disk images for AArch64 Platforms

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

On Thu, 2015-05-14 at 14:25 -0500, Jim Perrin wrote: > We've produced a disk image intended to help hardware vendors and > enthusiasts who are interested in bringing CentOS to their AArch64 based > platform. This allows a vendor to bypass the installer or to edit the > disk image before booting in order to test kernel modules or options. It > is intended for development purposes

On Thu, 2015-05-14 at 13:51 -0700, John R Pierce wrote: > On 5/14/2015 1:39 PM, Always Learning wrote: > > Does this mean it may be possible to run basic version of C5, C6 and C7 > > on Arm64* CPU systems ? Presumably this will include the Raspberry Pi ? > is the rasberry pi ARMv8 (arm64) ? I thought it was v7 (32bit only) ~~~~~~~~~~ Raspberry Pi 2 Model B is the second

It would be great if anyone can share your thoughts about the cause and possibly fix of the error below ? I would like to know why it is caused and how it can be fixed (if possible) ? The error message is: ~/llvm/build/install_android/linux-x86/clang-3688880/bin/ld.lld: error: external/boringssl/linux-aarch64/crypto/sha/sha1-armv8.S:1202: can't create dynamic relocation R_AARCH64_PREL64

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

On 23 March 2017 at 21:35, Peter Smith <peter.smith at linaro.org> wrote: > Hello Min, > > This error message occurs when the linker would have to create a > dynamic relocation in a read-only part of the program, which isn't > usually allowed when making a position independent shared-library or > position independent executable. In practice this usually means that >

On 5/14/2015 1:39 PM, Always Learning wrote: > Does this mean it may be possible to run basic version of C5, C6 and C7 > on Arm64* CPU systems ? Presumably this will include the Raspberry Pi ? is the rasberry pi ARMv8 (arm64) ? I thought it was v7 (32bit only) -- john r pierce, recycling bits in santa cruz

We are pleased to announce the public beta release of CentOS Linux 7 for AArch64 compatible hardware. We've addressed a number of issues discovered from the previous 2 weeks of alpha testing, and feel that the release is stable enough to transition to beta. Improvements from Alpha ======================= Improved package selection: A number of additional packages have been added, including

OS: EL6 - sometimes I use kpartx -a /mnt/.../lvdisk.img to map the partitions and mount them via /dev/mapper/loop0pX After using the disk (unmounting it) I noticed that detaching such mapping via kpartx -d does not result in freeing up the loop devices. Results: System reboots shows that the filesystem where lvdisk.img is located can't be unmounted. lsof, fuser, ps does not show

The RSEL Project has working builds of EL6 and 7 out for embedded ARM devices like the raspberry pi. http://www.redsleeve.org You need to dig through their wiki four instructions your several devices. Am 14.05.2015 23:46 schrieb "Johnny Hughes" <johnny at centos.org>: > On 05/14/2015 04:19 PM, Always Learning wrote: > > > > On Thu, 2015-05-14 at 13:51 -0700, John R

Hello, I would like to know which ARM processors does CentOS support? Does it support Freescale/NXP? Thanks and regards Jay

Hi all, A bunch of us met at EuroLLVM to discuss the planned merge of the two current AArch64 backends in the tree. The primary question was which backend should form the basis of the merge (since the core .td files aren't directly mergeable), with code being cherry-picked from the other on a case-by-case basis. There were factors to consider both ways, but I think the key points of interest

Hi Tim, 2014-06-25 15:26 GMT+08:00 Tim Northover <t.p.northover at gmail.com>: > Hi Kevin, > > I assume you've looked at the GCC documentation in this area, since > your ideas are very similar: > https://gcc.gnu.org/onlinedocs/gcc/AArch64-Options.html. I actually > think that looks like a rational set of conventions too. > > The main difference appears to be

We are pleased to announce the second public beta release of CentOS Linux 7 for the AArch64 platform. This release contains fixes and code updates provided in the RHELSA source code recently published to git.centos.org as well as rolling previous updates into the installer. We intend to have a 'Gold' release very soon unless a blocker bugs are reported, so please test this release.

On 04/02/2015 01:28 PM, Phelps, Matthew wrote: > > Soliciting our feedback *before* changing everything regarding release > names would > have been nice. We did. http://lists.centos.org/pipermail/centos-devel/2015-February/012873.html -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

On 03/07/2018 04:48 AM, Leon Fauster wrote: > OS: EL6 - sometimes I use > > kpartx -a /mnt/.../lvdisk.img > > to map the partitions and mount them via > > /dev/mapper/loop0pX > > After using the disk (unmounting it) I noticed that > detaching such mapping via kpartx -d does not result > in freeing up the loop devices. Results: System reboots > shows

Hi, Is there any information available on porting Syslinux to 64bit ARM? Specifically, I have a Cavium ThunderX board (Gigabyte R120-T30) which boots using UEFI - b2b.gigabyte.com/products/product-page.aspx?pid=5864#ov I'd be very interested in getting this to work, as currently the only option for booting on this platform is Grub 2 or EFI Stub. If anyone can point me in the right

On 05/14/2015 04:19 PM, Always Learning wrote: > > On Thu, 2015-05-14 at 13:51 -0700, John R Pierce wrote: >> On 5/14/2015 1:39 PM, Always Learning wrote: >>> Does this mean it may be possible to run basic version of C5, C6 and C7 >>> on Arm64* CPU systems ? Presumably this will include the Raspberry Pi ? > >> is the rasberry pi ARMv8 (arm64) ? I thought

On 05/14/2015 03:51 PM, John R Pierce wrote: > On 5/14/2015 1:39 PM, Always Learning wrote: >> Does this mean it may be possible to run basic version of C5, C6 and C7 >> on Arm64* CPU systems ? Presumably this will include the Raspberry Pi ? > > is the rasberry pi ARMv8 (arm64) ? I thought it was v7 (32bit only) > You are correct, the Pi is not armv8. This is for

Hi All: We have some patches to port klibc to ArmV8. The first set of patches from Neil Williams fixes the build issues. The second set of patches from Anil Singhar fixes functionalities. The following files have changed in the second set of patches ------------------------------------------------------------------------------------------ usr/include/arch/aarch64/klibc/archconfig.h