Hi all,
I would like to introduce myself to the group. I have recently
received an IGEPv2 board [1], 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
seem simple.
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
set variants).
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.6.31).
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 [2].
Does this, in any way, help with the compatibility of packages
targetting Cortex-A8?
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!
Kind regards,
Matthew
[1] http://www.igep-platform.com/index.php?option=com_content&view=article&id...
[2] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0344j/Beih...

Hey All,
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.
https://lwn.net/Articles/457145/
Peter

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?
Gordan

Hi all,
I ran Dan Horák's koji-compare.py script from
http://fedora.danny.cz/tmp/koji-compare.py against arm koji for f17 we
got at the end
statistics: {'older': 1979, 'local_only': 11, 'remote_only': 1428,
'same': 7873, 'newer': 37, 'total_missing_builds': 6014}
the older builds are things that we have an older build of, local_only
are arm only builds, remote_only are things we dont have built in arm
koji but are built on primary, same is where the nvr we have matches
primary, newer means our nvr is newer than primary, and the
total_missing_builds is the count of all builds missing which means if
there are 4 newer builds of libfoo on primary we count that 4 times.
Dennis

I am trying to start a project involving ARM and Fedora. I read the page http://fedoraproject.org/wiki/Architectures/ARM, and downloaded the file http://fedora.roving-it.com/rootfs-f15-sfp-alpha1.tar.bz2 which was labeled as "Fedora 15 Alpha 1 release for
ARMv5tel <http://fedora.roving-it.com/rootfs-f15-sfp-alpha1.tar.bz2>". I am still waiting for an ARM board, so I installed qemu-system-arm in Fedora 16 x86_64. After reading http://fedoraproject.org/wiki/Architectures/ARM/HowToQemu, I prepared an ext3
filesystem image, unzipped the downloaded file into it, and attempted to boot with the following command:
qemu-system-arm -m 256 -M versatilepb -kernel boot/vmlinuz-2.6.41.6-1.fc15.armv5tel -initrd boot/initramfs-2.6.41.6-1.fc15.armv5tel.img -hda fedora-15-arm.img -net nic -net user -append "console=ttyS0 root=LABEL=rootfs rw"
No matter how many variations of this I try, I get a black screen in the qemu video console. On the qemu serial console, I get "Uncompressing Linux... done, booting the kernel.", and no further output. The qemu-system-arm process gets stuck at 100% CPU.
Other options for -M either behave the same, or do not even display the "Uncompressing..." message.
I do not get enough information to even guess whether the kernel will see the hard disk image or not.
What is exactly what I am doing wrong? Did I download the wrong image?