arm November 2009

arm@lists.fedoraproject.org

8 participants
4 discussions

Fedora ARM 12 on IGEPv2 (Beagle Board clone)
by Matthew Wilson 02 Jan '16

02 Jan '16

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=4… [2] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0344j/Beihgi…

11 15

prebuilt kernel 2.6.31.6 for Kirkwood available
by Dan Horák 11 Dec '09

11 Dec '09

Hello, I have built kernel 2.6.31.6 with modules and a generic ramdisk that works for some combinations of Kirkwood-based devices (Sheevaplug and QNAP TS-[12]19) and devices carrying the root filesystem. They are available together with my build scripts at http://fedora.danny.cz/arm/ Changes: - kernel config now sets CONFIG_LSM_MMAP_MIN_ADDR=4096 (adviced by Eric Paris) - the ramdisk is now generated with dracut instead of mkinitrd Using dracut for preparing the ramdisk has many advantages: - one ramdisk works on a whole platform, but creating host-specific ramdisks is still possible - allows to explicitly specify block device drivers and filesystems that are included, that sets the array of allowed block device and filesystem type combinations for the root filesystem - allows to enable features like RAID and crypto for root - root filesystem device is set on the kernel command line only, it's not hardcoded anywhere, but the drawback is it needs to be set in the uboot environment via console - no hand-coded hacks are needed Dan

1 3

Fedora-ARM 12
by Kedar Sovani 19 Nov '09

19 Nov '09

Hi all, Fedora-ARM 12 is now available! The RFS is available at: http://ftp.linux.org.uk/pub/linux/arm/fedora/rootfs/rootfs-f12.tar.bz2 The following package groups are available: Base, Core, Base-X, GNOME-Desktop, XFCE-Desktop, Java, Java-Development, Admin-Tools, System-Tools, Web Server, and commonly used embedded packages. As usual it is built for ARMv5 EABI, soft-float, little endian. For more details head to: http://fedoraproject.org/wiki/Architectures/ARM Cheers, Kedar.

4 4

my email id
by sanjat panigrahi 16 Nov '09

16 Nov '09

sanjat.panigrahi(a)gmail.com -- Sanjat

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm November 2009