I would like to introduce myself to the group. I have recently
received an IGEPv2 board , which is based on the Beagle Board, but
with wifi, bluetooth, ethernet, and more RAM. I'm still at the "wow,
it's tiny and it runs Linux" stage. I should get a bit more time over
the next month and Christmas to play around properly with it.
I'm new to embedded development, but neither new to Linux nor ARM
(writing my first ARM assembly some 15 years ago). However, for the
past 6 years I've not even built a Linux kernel, preferring to use the
default kernel in Fedora for simplicity :)
Firstly, a thank you to those involved in Fedora ARM for getting it to
this stage. If I get the time, I'd really like to contribute some
(probably small) effort to help get Fedora ARM working well on the
IGEPv2 and Beagle Board. As I progress, I'd like to know what I can
do to help.
In the meantime, I have some questions. Apologies in advance if these
1) There are various different kernels from different sources. I'm
used to there being a small set of "right" kernels (that is, Fedora's
idea of "right") for x86. I fully appreciate that different ARM-based
boards are quite different in capabilities (like different instruction
a) Is there likely to be some standardised vanilla Fedora ARM kernel
source? (Or is that simply the source RPM available for Fedora?)
Then patches /could/ be offered for the more common systems (e.g.
Beagle Board & clones, SheevaPlug).
b) Would it then make sense to offer these as pre-built RPMs for common systems?
c) Is there any guidance on which version is good to use as a base?
I've seen quite different kernel versions being used (from 2.6.27 to
2) I understand a little bit about the different calling conventions,
FP differences (e.g. soft FPU versus VFP), and instruction set
differences (v5 versus v7).
a) Can the kernel can be safely built with a different instruction set
targeted? (I know there are different optimisation options passed to
GCC. Apologies if this seems a bit newbie-ish.)
b) For FP-heavy programs (e.g. ogg encoding), is it possible to build
the packages with VFP/NEON but still get them to work in a soft FPU
system? I'd imagine any call to an external library would have to
somehow be defined to use a different calling standard.
3) There seem to be some missing dependencies in the packages in the
current Fedora ARM repository. For example, emacs is requiring
libotf, which doesn't seem to be there in the repository. And
likewise with the xorg-x11-font* packages needing ttmkdir. I'm
confused as to how the RPM could have been successfully built without
it. What am I missing?
4) I see there has been some discussion over unaligned data access.
(Oh, I remember that from the ARM2 days.) It seems as if the
Cortex-A8 cores allow unaligned data access when set up to do so .
Does this, in any way, help with the compatibility of packages
5) I've managed to get various source packages missing from the Fedora
ARM repositories to compile successfully (natively). I guess there is
a reason why there are not in the repos right now -- is that reason
down to time and priorities, or is there some blocking bugs with many
of these packages?
I look forward to being able to contribute something back into Fedora!
I know it was discussed a while ago how the USB storage on PandaBoards
was slow, not sure what the resolution was but saw this article on LWN
that looks like our problem there for those that might not have seen
the post elsewhere and are interested.
On Thu, Mar 22, 2012 at 02:02:26PM -0600, Orion Poplawski wrote:
> On 03/22/2012 01:30 PM, Brendan Conoboy wrote:
> >On 03/22/2012 11:10 AM, Orion Poplawski wrote:
> >>I started looking at:
> >>VM starts okay in F16 with setsebool -P virt_use_execmem=on
> >>But the image is a Fedora 12 system. Any updated images out there?
> >You should be able to use the F17 alpha 1 image. The pointer is it:
> >We'll have the document updated for this soon. I've set reply-to to the arm
> >list since the responsible parties are all there.
> Sorry, still very green with vm wrangling. How do I take the rootfs
> tarball and make a qemu image I can use with libvirt?
I've not actually tried it for this situation, but virt-make-fs can
turn a tarball into a disk image.
Probably something like this:
virt-make-fs -s 1G -t ext3 -F raw --partition=mbr rootfs.tar disk.img
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://libguestfs.org
Acording to the documentation on raspberrypi.org, it would seem that
Raspberry Pi are dropping Ubuntu in favour of Fedora because Ubuntu is
dropping support for ARMv5/ARMv6 (yay!).
Also, according to the Raspberry Pi wiki, they expect that Eclipse will
work. That doesn't appear to be the case at the moment. Has anybody
managed to get Eclipse to build on ARM recently? Or has Eclipse ARM port
been given up on?
I've put together a script to create up-to-date F17 snapshot images and
am storing the result on my people page. These are based on Peter's F17
alpha1 images with the following changes:
There is a tarball without any kernels included.
There is a tarball with uBoot-wrapped kernels included (should have
everything you need without messy mkimage commands). The armhfp version
includes tegra, omap and imx kernels. The arm version includes kirkwood.
There are bzcat+dd images for Tegra and OMAP- no partitioning necessary
to get started. These decompress to 8GB- if you have a larger storage
device resize2fs is your friend.
The files are currently uploading and will be entirely there in a few
more minutes. You can get the latest at:
This is very much a work in progress, completely unofficial, largely
untested, but hopefully useful. Feel free to send me feedback. Enjoy,
Brendan Conoboy / Red Hat, Inc. / blc(a)redhat.com