Please join us tomorrow (20 DEC 2012) at 11am EST in #fedora-arm on
Freenode for another Fedora ARM VFAD.
There will be a number of pre-created F18 ARM Beta TC3 images available
for testing, including: PandaBoard, Trim Slice, Versatile Express
(QEMU), and Kirkwood (GuruPlug).
All help is appreciated and we look forward to your participation.
It's time to announce a little project I've been working on for the last
few weeks: the ARMv8 bootstrap project for Fedora.
There has been a lot of interest in ARMv8 (also known as aarch64) in the
last few months since it was introduced by ARM. A 64-bit processor that
uses as little power as possible could provide an enormous cost savings
to the vast and growing data centers throughout the world.
So, even though hardware is not yet available, we have started the work
needed to bring Fedora to ARMv8. Using the ARM provided Foundation
model (a platform simulator for ARMv8), we have been building up the
packages needed to eventually get to a full native build of Fedora.
Details and current status are here:
Of the six stages needed in the bootstrap of a new architecture, we
are in the middle of stage 2; these are therefore pretty early bits.
In the interest of full transparency in what we do, and in the spirit
of release early and release often, grab a copy and have fun!
On the Fedora wiki, you will find instructions on where to find all
the bits and pieces used to construct the root file system image
that's been created so far, and how to use the ARM Foundation model
to do further work. And there is plenty to do :).
If you'd like to help, read through the wiki pages above and get
yourself to the point where you can run the ARM Foundation model
using the Fedora root file system. Then find a package needing
some love and do what needs to be done for ARMv8 (the wiki explains
And if you have questions, you can find me (ahs3) on #fedora-arm on
IRC (Freenode), or ask on this mailing list; the more, the merrier.
Red Hat, Inc.
This script assumes that the rootfs git repo has been cloned into
the same directory as the script. It also assumes that qemu is installed.
# script for creating a filesystem image for Fedora's Aarch64 port
# Copyright 2012 John Dulaney jdulaney(a)fedoraproject.org
# Licensed under the GPLv3+
# Dependancies: qemu
# Set image size
# Create image
qemu-img create rootfs.img $imgsize
# Add partitions to the image, a 50 MB DOS bootable partition for
# uboot, and the rest will be for /
parted rootfs.img mklabel msdos
parted rootfs.img mkpart primary fat16 1 50
parted rootfs.img mkpart primary ext3 50 $imgsize
parted rootfs.img set 1 boot on
# Mount the image in /tmp
sudo kpartx -a -v rootfs.img
sudo mkfs.vfat /dev/mapper/loop0p1
sudo mkfs.ext3 /dev/mapper/loop0p2
sudo mount /dev/mapper/loop0p1 /tmp/vfat
sudo mount /dev/mapper/loop0p2 /tmp/ext3
# Put uboot into the vfat partition for booting
sudo cp u-boot.bin /tmp/vfat
sudo umount /tmp/vfat
# Copy file system into image
sudo sh -c "find . -print | cpio -pdumv /tmp/ext3"
#Create /proc, /sys, /dev, etc. since Git doesn't seem to like empty directories
sudo mkdir /tmp/ext3/proc
sudo mkdir /tmp/ext3/sys
sudo mkdir /tmp/ext3/dev
sudo mkdir /tmp/ext3/tmp
sudo mkdir /tmp/ext3/var/tmp
# Create special files in /dev
sudo mknod null c 1 3
sudo mknod zero c 1 5
sudo mknod tty c 5 0
sudo mknod console c 5 1
sudo mknod sda b 8 0
sudo mknod sda1 b 8 1
sudo mknod sda2 b 8 2
sudo mknod sda3 b 8 3
sudo mknod sda4 b 8 4
sudo mknod mmcblk0 b 179 0
sudo mknod mmcblk0p1 b 179 1
sudo mknod mmcblk0p2 b 179 2
sudo mknod mmcblk0p3 b 179 3
sudo mknod mmcblk0p4 b 179 4
sudo mknod ttyO0 c 253 0
sudo mknod ttyO1 c 253 1
sudo mknod ttyO2 c 253 2
sudo mknod ttyO3 c 253 3
sudo mknod tty2 c 4 2
sudo mknod tty3 c 4 3
sudo mknod tty4 c 4 4
sudo mknod ttyS0 c 4 64
sudo mknod ttyS1 c 4 65
sudo mknod ttyS2 c 4 66
sudo mknod ttyS3 c 4 67
sudo chmod a+rw null zero
# Unmount the image.
sudo umount /tmp/ext3
-------- Original Message --------
Subject: Re: [fedora-arm] Soft-float chroot on hard-float distro and
Date: Mon, 17 Dec 2012 15:16:15 -0500 (EST)
From: Jon Masters <jcm(a)redhat.com>
To: Gordan Bobic <gordan(a)bobich.net>
Bind mount /proc, /dev, /sys, and then it'll work just fine. You need
cpuinfo visible for e.g. rpm to determine you are on a hard float system.
Sent from my phone. Please excuse formatting and brevity.
Gordan Bobic <gordan(a)bobich.net> wrote:
I've been trying to google this and I haven't been able to find a
definitive answer on the subject. I seem to recall a discussion on this
list a while back, with the general conclusion being that this is
problematic, but my googling threw up a few pages about Debian implying
that it could be made to work.
Has anybody got any words of wisdom on this subject they might care to
share? I am mainly interested in this from the point of view of running
a Fedora chroot under Android with VNC on loopback on a Nexus 10.
arm mailing list