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!
So I found this page searching for some stack which has Java running on
linux running on a ARM11 processor(Samsung s3c6410) to be exact. I am linux
NOOB too. From what I read I understand that I have to build the kernel
again for my target board. Is this also true for each of the binaries on the
rootfs or from the yum repository?
On 01/26/10 11:43, Somebody in the thread at some point said:
> Hi Andy,
> Thanks for sharing the info.
> More questions -
> For development, I am planning to use QEMt U to load a kernel image[so
> it would be great if you have a prebuilt kernel image for s3c6410 to
> share :) ] and use the rootfs to derisk stuff until I get my hands on a
> proper dev board.
> Is this a step in the right direction?
I don't use Qemu because I have SMDK6410, it's preferable to use a real
board all the time.
I can't give prebuilt binaries when I am not set up to also provide
source for GPL reasons.
However, if you go here
and install the cross toolchain on your Fedora host, then
git clone git://git.warmcat.com/qi
and check out the txtr branch
you should be able to build Qi, if you look in ./image/qi-s3c6410....bin
and examine 6410-partition-sd.sh you will see how to make a bootable SD
For the kernel, I used Ben Dooks' tree
git clone git://git.fluff.org/bjdooks/linux.git
there's a slightly outdated config for smdk6410 in arch/arm/configs.
In both cases, you can use the Fedora ARM Cross toolchain to build them.
Dear Fedora-Arm,I strongly recommend this website www.justdial.com. It's a world class local search service & I've always found anything I've ever wanted.You can find info on any company, product, or service in over 240 cities in India.You can also call them up 24x7, on phone (69999999), a local call in 240 Indian cities.Ask for anything, you'll get the info on the phone and/or by SMS within 30 secs, and this service is at no cost!For a change, it's an original Indian idea and an Indian company with world class service, and with a vision to spread all over the world.Be a proud Indian and forward this to every Indian you know.Best Wishes,RupakClick Here to unsubscribe.
> -----Original Message-----
> From: Amey Inamdar
> Sent: Monday, January 04, 2010 10:26 AM
> To: Prafulla Wadaskar; Piyush Shah
> Subject: FW: [fedora-arm] Sheevaplug and F12
> FYI, if you've not seen.
> > -----Original Message-----
> > From: fedora-arm-bounces(a)redhat.com
> > [mailto:firstname.lastname@example.org] On Behalf Of Quentin Armitage
> > Sent: Sunday, January 03, 2010 6:20 AM
> > To: fedora-arm(a)redhat.com
> > Subject: Re: [fedora-arm] Sheevaplug and F12
> > On Sat, 2010-01-02 at 11:08 +0000, Graeme Hilton wrote:
> > > Hi,
> > >
> > > I've got a Sheevaplug and I'm using a 4GB SD card to hold the OS.
> > >
> > > PS My environment and uBoot version are attached below.
> > >
> > > Marvell>> printenv
> > > baudrate=115200
> > > loads_echo=0
> > > ipaddr=10.4.50.165
> > > serverip=10.4.50.5
> > > rootpath=/mnt/ARM_FS/
> > > netmask=255.255.255.0
> > > console=a0000
> > > e=ttyS0,115200
> > mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
> > > CASset=min
> > > MALLOC_len=1
> > >
> > > U-Boot 1.1.4 (Sep 14 2009 - 15:36:37) Marvell version: 3.4.19
> > > Marvell>>
> > >
> > There is a bug in Sheevaplug uboot 3.4.19 which corrupts the
> > environment
> > (see console=a0000 and following line above).
> > This is now fixed in 3.4.27, but two further issues have been
> > found, and
> > pingtoo has produced fixes -see
> > http://plugcomputer.org/plugforum/index.php?topic=1134.31 .
> It appears
> > that the best uboot is 3.4.27 as patched by pingtoo,
Dear Quentin Armitage
Can you please try latest mainlined u-boot for this problem?
Prafulla . .
> > http://plugcomputer.org/plugforum/index.php?action=dlattach;to
> pic=1134.0;attach=201 .
> > Beware though, and it applies not only to 3.4.27, but also
> 3.4.19 and
> > 3.4.16 and probably earlier, that it appears there is a bug
> > in the SDHC
> > handling, and that uboot will not be able to handle offsets
> > greater than
> > 4Gb on the card; you should be safe with your 4Gb card of course.
> > Regards,
> > Quentin Armitage
> > _______________________________________________
> > fedora-arm mailing list
> > fedora-arm(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-arm
I have Fedora 12 up and running on my Nokia N900.
Status: no phone, no battery charging, but wifi works and I'm about to get X
I wrote up a mini HOWTO here: