From Fedora Project Wiki

< Architectures‎ | ARM

Revision as of 04:35, 22 June 2011 by Jcm (talk | contribs)


[ARM] Fedora15 HardFP Bootstrap Virtual FAD - 2011/06/22

We wish to accelerate the bringup of Fedora 15 on ARMv7 systems running with hardware floating point (hardfp). To that end, we are running regular bootstrap days, during which we will meet in a virtual capacity (on IRC, and over the phone) to build up through cross-compilation (and other means) the core packages required for Fedora 15 to become self-hosting on ARMv7 with hardware floating point.

When and Where

14:00 UTC, Wednesday June 22nd 2011

IRC: #fedora-arm on irc.freenode.net

Phone: Access code: 1236987415

Toll Free Dial-In Number (US & Canada): (800) 451-8679

Etherpad: http://www.tinyurl.com/fedora-arm (including full list of international dialin numbers)

Event owners

Attendees

Summary

Program

  • Recap from the June 10th Fedora Activity Day
  • Approach to today's activities is to continue with the instructions in Architectures/ARM/Fedora15 HardFP Bootstrap (make sure you do your work on a armv7hl-YOUR_FAS_USERNAME or a group named branch so that we can track who is doing what and back out changes if we discover a problem with your setup later, etc.)
  • Summary of events and plan for next VFAD
  • Plan is for the next event to be in a regular Friday slot (perhaps Friday afternoons?)

Requirements

  • Internet connection to log into IRC, and phone if possible (phone not essential)
  • A supported ARMv7 target board
  • Lots of coffee

Setup

  • A pre-requisite is a working ARMv7-compatible supported target board, such as a BeagleBoard or a PandaBoard.
    • You can find out more from the main Fedora ARM pages about obtaining a pre-built rootfs (no installer yet)
    • We now have some Fedora ARM kernel packages for OMAP-based boards
  • Follow the instructions for setting up a chroot using the Architectures/ARM/Fedora15 HardFP Bootstrap armv7hl rootfs in the Fedora ARM git repository (make sure you do your work on a armv7hl-YOUR_FAS_USERNAME or a group named branch so that we can track who is doing what and back out changes if we discover a problem with your setup later, etc.)