Zodiac1111 (talk | contribs) m (需要翻译) |
Zodiac1111 (talk | contribs) m (简单翻译,需要审核) |
||
Line 3: | Line 3: | ||
Moving to ARM - A secret decoder ring for Fedora users wishing to learn more about Fedora on ARM processors. | Moving to ARM - A secret decoder ring for Fedora users wishing to learn more about Fedora on ARM processors. | ||
* [http://piratepad.net/L1jH2TLCBO Original Document] | * [http://piratepad.net/L1jH2TLCBO Original Document] | ||
== | ==简介== | ||
ARM chips are the most widely-produced processor family in the world; they have historically been used in cell phones and embedded applications, but were originally designed as desktop processors, and are increasingly used in tablet devices and low-power-consumption servers. | ARM chips are the most widely-produced processor family in the world; they have historically been used in cell phones and embedded applications, but were originally designed as desktop processors, and are increasingly used in tablet devices and low-power-consumption servers. | ||
The Fedora-ARM project is an initiative to bring Fedora to this processor family. | The Fedora-ARM project is an initiative to bring Fedora to this processor family. | ||
==== | ====为什么选择 ARM?==== | ||
* Low Power Consumption / Better efficiencies | * Low Power Consumption / Better efficiencies | ||
* High levels of device integration -- "system on a chip" designs, with reduced space and cooling requirements | * High levels of device integration -- "system on a chip" designs, with reduced space and cooling requirements | ||
Line 18: | Line 18: | ||
* Growing user base | * Growing user base | ||
== | ==理解ARM== | ||
* The history of the ARM architecture - [http://en.wikipedia.org/wiki/ARM_architecture#History here] | * The history of the ARM architecture - [http://en.wikipedia.org/wiki/ARM_architecture#History here] | ||
* Different ARM cores - [http://en.wikipedia.org/wiki/List_of_ARM_microprocessor_cores here] | * Different ARM cores - [http://en.wikipedia.org/wiki/List_of_ARM_microprocessor_cores here] | ||
Line 44: | Line 44: | ||
* Hyperscale Server Systems (Calxeda Highbank) | * Hyperscale Server Systems (Calxeda Highbank) | ||
=== | ===另外的ARM技术=== | ||
* [http://en.wikipedia.org/wiki/ARM_architecture#Thumb Thumb(2,EE)] | * [http://en.wikipedia.org/wiki/ARM_architecture#Thumb Thumb(2,EE)] | ||
* [http://www.arm.com/products/processors/technologies/jazelle.php Jazelle] | * [http://www.arm.com/products/processors/technologies/jazelle.php Jazelle] | ||
Line 52: | Line 52: | ||
* [http://www.arm.com/products/processors/technologies/biglittleprocessing.php big.LITTLE Processing] | * [http://www.arm.com/products/processors/technologies/biglittleprocessing.php big.LITTLE Processing] | ||
=== | ===U-Boot是什么=== | ||
U-Boot -the Universal Boot Loader is the firmware used on embedded systems such as ARM, MIPS and Embedded Power architectures. It performs the task of other bootloader's by loading the Linux kernel and operating system into memory for execution, but is also responsible for hardware initialization comparable to the BIOS on X86 hardware. | U-Boot -the Universal Boot Loader is the firmware used on embedded systems such as ARM, MIPS and Embedded Power architectures. It performs the task of other bootloader's by loading the Linux kernel and operating system into memory for execution, but is also responsible for hardware initialization comparable to the BIOS on X86 hardware. | ||
* Additional information on [http://www.denx.de/wiki/U-Boot U-Boot] | * Additional information on [http://www.denx.de/wiki/U-Boot U-Boot] | ||
==== | ====为什么选择U-Boot?==== | ||
The Basic Input/Output System (BIOS) is exclusively available on x86 systems and performs a variety of tasks outside of just loading the kernel into memory. While BIOS on ARM is feasible, development costs exceed the potential benefits and ARM systems use the faster bootloader approach. The Unified Extensible Firmware Interface (UEFI) is replacing the BIOS on modern computers and is also compatible with the ARM architecture. | The Basic Input/Output System (BIOS) is exclusively available on x86 systems and performs a variety of tasks outside of just loading the kernel into memory. While BIOS on ARM is feasible, development costs exceed the potential benefits and ARM systems use the faster bootloader approach. The Unified Extensible Firmware Interface (UEFI) is replacing the BIOS on modern computers and is also compatible with the ARM architecture. | ||
* There are many variations of U-Boot which includes - vboot, aboot, hboot. | * There are many variations of U-Boot which includes - vboot, aboot, hboot. | ||
Line 62: | Line 62: | ||
===Generating addresses for kernel/initrd/dtb=== | ===Generating addresses for kernel/initrd/dtb=== | ||
== | ==快速入门== | ||
===What's the quickest way to get Fedora on my device?=== | ===What's the quickest way to get Fedora on my device?=== | ||
Download the pre-built images corresponding to your device and following the instructions for writing the image to your media. | Download the pre-built images corresponding to your device and following the instructions for writing the image to your media. | ||
==== | ====Fedora支持的平台==== | ||
* [[Architectures/ARM/F18/Pandaboard|Pandaboard]] | * [[Architectures/ARM/F18/Pandaboard|Pandaboard]] | ||
* [[Architectures/ARM/F18/Trimslice|Trimslice]] | * [[Architectures/ARM/F18/Trimslice|Trimslice]] | ||
Line 75: | Line 75: | ||
* [[Architectures/ARM/F18/Versatile_Express|Versatile Express]] | * [[Architectures/ARM/F18/Versatile_Express|Versatile Express]] | ||
==== | ====Fedora Remixes支持的平台==== | ||
* XO 1.75 | * XO 1.75 | ||
* OpenBlocks AX3 | * OpenBlocks AX3 | ||
Line 82: | Line 82: | ||
* [[Architectures/ARM/F18/Remixes#Raspberry_Pi |Raspberry Pi]] | * [[Architectures/ARM/F18/Remixes#Raspberry_Pi |Raspberry Pi]] | ||
=== | ===一旦我的设备运行的是Fedora,我怎么得到开发/推动的Fedora ARM?=== | ||
* Introduce yourself on the mailing list | * Introduce yourself on the mailing list | ||
** Mailing list: {{fplist|arm}} ([http://lists.fedoraproject.org/pipermail/arm/ archives]) | ** Mailing list: {{fplist|arm}} ([http://lists.fedoraproject.org/pipermail/arm/ archives]) | ||
Line 96: | Line 96: | ||
* <b>Developers</b> - Ensure patches are going upstream! | * <b>Developers</b> - Ensure patches are going upstream! | ||
=== | ===理解Fedora工具=== | ||
====Koji==== | ====Koji==== | ||
Koji is the software that builds [http://koji.fedoraproject.org/koji/ RPM packages for the Fedora project]. It uses [http://fedoraproject.org/wiki/Projects/Mock Mock] to create chroot environments to perform builds. To download the source code, report bugs, join the mailing list etc., see the [https://fedorahosted.org/koji/wiki Koji project website] . | Koji is the software that builds [http://koji.fedoraproject.org/koji/ RPM packages for the Fedora project]. It uses [http://fedoraproject.org/wiki/Projects/Mock Mock] to create chroot environments to perform builds. To download the source code, report bugs, join the mailing list etc., see the [https://fedorahosted.org/koji/wiki Koji project website] . | ||
Line 105: | Line 105: | ||
Koji-Shadow is a script that is used by secondary architectures to 'follow' package builds performed on the primary architecture (PA) [[http://koji.fedoraproject.org Koji instance]]. When a build is submitted on PA, the script will pick it up and submit the build for completion on the secondary architecture. This ensures secondary architectures build the same packages used in primary within a reasonable time frame, developers need to only submit their package once, and it is propagated to all secondary architectures running Koji-Shadow. Koji-Shadow is included in the 'koji-utils' package. | Koji-Shadow is a script that is used by secondary architectures to 'follow' package builds performed on the primary architecture (PA) [[http://koji.fedoraproject.org Koji instance]]. When a build is submitted on PA, the script will pick it up and submit the build for completion on the secondary architecture. This ensures secondary architectures build the same packages used in primary within a reasonable time frame, developers need to only submit their package once, and it is propagated to all secondary architectures running Koji-Shadow. Koji-Shadow is included in the 'koji-utils' package. | ||
===== | =====关于Koji更多的信息===== | ||
* [[koji/ServerHowTo| Run Your Own Koji Build Server]] | * [[koji/ServerHowTo| Run Your Own Koji Build Server]] | ||
* [[koji/KojiLiveCDHowTo| Building Images in Koji]] | * [[koji/KojiLiveCDHowTo| Building Images in Koji]] |
Revision as of 05:24, 27 July 2013
Secret Decoder Ring
Moving to ARM - A secret decoder ring for Fedora users wishing to learn more about Fedora on ARM processors.
简介
ARM chips are the most widely-produced processor family in the world; they have historically been used in cell phones and embedded applications, but were originally designed as desktop processors, and are increasingly used in tablet devices and low-power-consumption servers.
The Fedora-ARM project is an initiative to bring Fedora to this processor family.
为什么选择 ARM?
- Low Power Consumption / Better efficiencies
- High levels of device integration -- "system on a chip" designs, with reduced space and cooling requirements
- Readily available from multiple vendors
- Low cost
Why does Fedora care about ARM?
- Emerging technology (as a general purpose computing platform)
- Growing user base
理解ARM
Software floating point vs. Hardware floating point
Fedora currently offers two flavours of ARM - 'arm(sfp)' and 'armhfp'. This is a reference to whether floating point values are passed to functions via CPU registers (sfp) or FPU registers (hfp); note that both API variants can use the FPU to perform arithmetic.
Here is the background: In older ARM chips (prior to ARM v7 "Application Profile"), the floating point unit (FPU, typically a vector floating point unit or "VFP") was optional. Therefore, function arguments were passed in the CPU registers or on the stack. However, when an FPU is available, moving floating-point values from the CPU registers to the FPU registers and back again has a significant cost which negates some of the advantage of having the additional arithmetic hardware. When the FPU became mandatory with ARMv7, it made sense to pass floating-point arguments directly in FPU registers. This is an incompatible ABI change, so programs which pass value in the CPU registers are incompatible with libraries that pass values in the FPU registers (and vice versa).
Currently-Supported ARM Architectures
armv7hl - 32-bit, little-endian, hfp for ARM v7 processors. Supported from F15 onwards.
armv5tel - 32-bit, little-endian, sfp for ARM v5 to v7 processors. Supported until F18 (including F18 updates).
(Community builds: Seneca is building for the armv6hl architecture specifically for the Architectures/ARM/F18/Remixes#Raspberry_Pi Raspberry Pi)
Future ARM Architectures
aarch64 - 64-bit (little-endian and hfp are assumed) for ARMv8+ processors. This is currently being bootstrapped.
ARM Form Factors
Being the most popular architecture in the world, ARM processors can be found in a variety of form factors that include:
- Tablets/Notebooks (Google Chromebook)
- Development Boards (Pandaboard, Beagleboard, Trimslice)
- Hyperscale Server Systems (Calxeda Highbank)
另外的ARM技术
U-Boot是什么
U-Boot -the Universal Boot Loader is the firmware used on embedded systems such as ARM, MIPS and Embedded Power architectures. It performs the task of other bootloader's by loading the Linux kernel and operating system into memory for execution, but is also responsible for hardware initialization comparable to the BIOS on X86 hardware.
- Additional information on U-Boot
为什么选择U-Boot?
The Basic Input/Output System (BIOS) is exclusively available on x86 systems and performs a variety of tasks outside of just loading the kernel into memory. While BIOS on ARM is feasible, development costs exceed the potential benefits and ARM systems use the faster bootloader approach. The Unified Extensible Firmware Interface (UEFI) is replacing the BIOS on modern computers and is also compatible with the ARM architecture.
- There are many variations of U-Boot which includes - vboot, aboot, hboot.
Generating addresses for kernel/initrd/dtb
快速入门
What's the quickest way to get Fedora on my device?
Download the pre-built images corresponding to your device and following the instructions for writing the image to your media.
Fedora支持的平台
For virtualization through QEMU:
Fedora Remixes支持的平台
- XO 1.75
- OpenBlocks AX3
- Allwinner A10-based devices
- Samsung Chromebook
- Raspberry Pi
一旦我的设备运行的是Fedora,我怎么得到开发/推动的Fedora ARM?
- Introduce yourself on the mailing list
- Hang out in the IRC channel
- IRC: #fedora-arm[?] on http://freenode.net
- Join our weekly meeting:
- IRC: #fedora-meeting-1[?] each Wednesday at 20:00 UTC (4PM EDT) on http://freenode.net (archives)
- Help fix packages that are failing to build on ARM
- Ask questions, and help make this documentation better
- Developers - Ensure patches are going upstream!
理解Fedora工具
Koji
Koji is the software that builds RPM packages for the Fedora project. It uses Mock to create chroot environments to perform builds. To download the source code, report bugs, join the mailing list etc., see the Koji project website .
- Koji Overview
- Using the Koji build system (includes cli and web interface. Use of fedpkg)
Koji-shadow
Koji-Shadow is a script that is used by secondary architectures to 'follow' package builds performed on the primary architecture (PA) [Koji instance]. When a build is submitted on PA, the script will pick it up and submit the build for completion on the secondary architecture. This ensures secondary architectures build the same packages used in primary within a reasonable time frame, developers need to only submit their package once, and it is propagated to all secondary architectures running Koji-Shadow. Koji-Shadow is included in the 'koji-utils' package.
关于Koji更多的信息
Bodhi
Bodhi pronounced as bo-dee is a buddhist term for the wisdom by which one attains enlightenment. Bodhi is a modular web-based system that facilitates the process of publishing package updates for Fedora. It maintains a single stage of repositories by adding/updating/removing packages.
- For more information on Bodhi
The Future of Fedora and the ARM Architecture
Promotion to a Primary Architecture
ARM is currently considered a Secondary Architecture in Fedora and would greatly benefit from being promoted to a primary architecture, a detailed draft proposal can be found here.
Future Boot Options
- Grub2