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.
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?
f15stats.html :: Mon Jan 30 13:05:02 UTC 2012 -- Tue Jan 31 13:05:01 UTC 2012
Errors Unbuilt Different Working Built
594 [-30] 661 [-7] 294 [+4] 2 [+2] 8864 [+31]
f17stats.html :: Mon Jan 30 13:05:02 UTC 2012 -- Tue Jan 31 13:05:02 UTC 2012
Errors Unbuilt Different Working Built
9 [+1] 5584 [-12] 71 [-1] 3 [+1] 5191 [+16]
* "Different" contains packages that are built but have a varying ENVR to that of PA-Koji
* "Working" lists any packages currently being built
* The numbers in the brackets show the difference recorded in the counts since the script was last run
Aloha my fine Fedora'ed friends,
I know Peter was looking at Snowballs as devices, and thought it prudent
to let you know that we at openSUSE have run into a little issue with
them. Don't get me wrong, they're a lovely board but as with most things
in the weird universe of ARM there are un-necessary hurdles.
As it stands now, there is no framebuffer based graphics driver for the
Snowball in the upstream kernel. The only one is in the Igloo Community
git repo so if like us you are using a single source for all
architectures, you may have an issue. They are working on getting KMS
support but I'm not sure how long that will take. they are also working
on a Wayland driver which should have an alpha release soon.
The reasoning they gave for the fb driver not being upstreamed is that
the code was in a heck of a state and would not be accepted upstream,
they are also hoping to move to KMS based instead and as such are
spending their effort there rather than tidying up the mess.
Hope this helps you, and if any of you are at FOSDEM let me know it
would be good to catch up in person :-)
I would like to remind you that the next (quarterly) "Connect" event
from Linaro is taking place in Redwood City, California next week:
Some of us will be there in person, but it is also possible to register
to attend remotely via IRC and dialin. You may be interested in
investigating this option if you are not attending in person.