[Fwd: [fedora-arm] Activity Day June 10th - ARMv7 F15 hardfp bringup]
Folks, If you're interested in getting involved in the armv7hl[0] bringup, please do subscribe to the ARM list and follow along/join us Fri for the first of what will hopefully be several sessions dedicated to bootstrap of F15 hardfp bits, followed by building the universe around those. Jon. [0] We're making a one time incompatible ABI switch in F-15 bringup to the hard float ABI defined in section 6 of the ARM AAPCS (commonly referred to as the ARM EABI - but that doesn't actually exist as a name). The procedure call standard will be ARM AAPCS vfpv3-d16, as defined in section 6 of that document. Other distros are switching and this will form the basis of any LSB standardization effort later on. Think of v7 and v5 as being different arches, which they are really. ---BeginMessage--- Hi Folks, We're planning to have an activity day of sorts on this coming Friday, the purpose of which is to sync up and co-ordinate the various efforts to achieve working ARMv7 hardfloat support for Fedora 15 bringup. The venue is #fedora-arm, and also using a dialin number (to be provided) for those who want to discuss topics over the phone. I believe most of us are geographically located in the US, so I am suggesting we could begin about 10:00EDT, which is 14:00UTC. Here's an initial agenda that I think covers some of the important stuff: 1. discuss requirements/sync up on build flags 2. current status of works in progress (DJ/Dennis/Seneca(?)?) 3. minimal dependency discussion for F15 (xdeb-graph equiv. needed) 4. plan for building/co-ordinating builds (host bits at Seneca?) 5. get stuff building (spend most time building/fixing packages) 6. status before end of day 7. plan for followup My assumption is that we'll consolidate the various activities begun so far, establish a plan for ongoing dialog, and hopefully decide on a way to host builds (pre-Koji) and so forth in a public Seneca environment. Chris seems quite amenable to allowing machines to be used to build bits, and I think I would like that in general if we can do so (perhaps setup a staging mount where people can build packages and poke at bits?) The main outcome I'm looking for is that we don't have stuff happening in different silos, know what everyone else is working on, etc. Jon. ___ arm mailing list a...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm ---End Message--- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Fwd: [fedora-arm] Activity Day June 10th - ARMv7 F15 hardfp bringup]
On Sat, 2011-06-04 at 20:53 -0400, Jon Masters wrote: [0] We're making a one time incompatible ABI switch in F-15 bringup to the hard float ABI defined in section 6 of the ARM AAPCS (commonly referred to as the ARM EABI - but that doesn't actually exist as a name). The procedure call standard will be ARM AAPCS vfpv3-d16, as defined in section 6 of that document. Other distros are switching and this will form the basis of any LSB standardization effort later on. Think of v7 and v5 as being different arches, which they are really. And to further clarify: - This is an addition, not a switch -- the intention is to continue to support armv5tel in addition to armv7hl at this time -- Tegra and Marvell Kirkwood (including plug computer) devices which do not support armv7hl will continue to work with armv5tel. - The significant incompatibility is hardfp vs. softfp ABI (moreso than v7 vs. v5). -- Chris -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Fwd: [fedora-arm] Activity Day June 10th - ARMv7 F15 hardfp bringup]
On Sat, 2011-06-04 at 21:10 -0400, Chris Tyler wrote: On Sat, 2011-06-04 at 20:53 -0400, Jon Masters wrote: [0] We're making a one time incompatible ABI switch in F-15 bringup to the hard float ABI defined in section 6 of the ARM AAPCS (commonly referred to as the ARM EABI - but that doesn't actually exist as a name). The procedure call standard will be ARM AAPCS vfpv3-d16, as defined in section 6 of that document. Other distros are switching and this will form the basis of any LSB standardization effort later on. Think of v7 and v5 as being different arches, which they are really. And to further clarify: - This is an addition, not a switch -- the intention is to continue to support armv5tel in addition to armv7hl at this time -- Tegra and Marvell Kirkwood (including plug computer) devices which do not support armv7hl will continue to work with armv5tel. - The significant incompatibility is hardfp vs. softfp ABI (moreso than v7 vs. v5). Thanks. Indeed, my separate arch comment is really that v7 (with assumed hardfp that will be the case in the form of ABI used) and v5 without hardfp do not use the same ABI calling convention. But for simplification, I called them different arches. We'll keep v5 around. I think longer term, it probably makes sense to kill it off once people have moved to newer boards/systems (like older versions of IA32 have been killed off over time). But again, that will depend on who is using v5, etc. over time. Jon. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
