The Fedora project provides developers with a free and open source platform tailored for a variety of hardware, cloud, and container systems. Fedora is available on Arm-based servers as well as a wide range of popular single board computers and developer devices.
The Fedora Project enables software developers and community members to build tailored solutions for their users. The Fedora community, in combination with other open source projects, enables technical features to make Linux powerful, flexible, and usable for a wide spectrum of users, administrators, and developers. Fedora creates two major releases each year.
Fedora Workstation is a reliable, user-friendly, and powerful operating system for Arm developers. The user interface is built with GNOME 3 desktop environment and comes with a wide range of tools to support developers, from hobbyists and students to professionals in corporate environments. One of the default tools in Workstation is Container Toolbox, which uses podman and OCI containers, and is a particularly useful utility for setting up multiple independent development environments.
Fedora Internet of Things
Fedora IoT is an immutable open source platform built with security in mind. Fedora IoT uses technologies such as OSTree, podman, OCI containers, greenboot, and PARSEC, to provide a secure and reliable platform that enables users to build projects ranging from home and maker through to industrial gateways and smart cities.
Fedora Server enables Arm developers to control all the infrastructure and services. Packages are grouped into modules — a representation of an application, a language runtime, or any logical group making the content more granular and easier to navigate.
Modules can be available in multiple streams, usually representing a major version of the software they include, enabling administrators (or developers) to use the right version of software they need. Installation profiles have been introduced to simplify the installation. These are package subsets representing a specific use case of a module
|Not answered||access secure generic timer||0 votes||61 views||0 replies||Started 6 days ago by armsss||Answer this|
|Not answered||How do branch instructions influence the performance of Cortex-A77?||0 votes||72 views||0 replies||Started 8 days ago by hyf_sysu||Answer this|
|Suggested answer||Getting Dummy character while receiving UART data,How to fix it ?||0 votes||445 views||2 replies||Latest 8 days ago by Jerome Decamps - 杜尚杰||Answer this|
|Suggested answer||Sht11 interfacing with lpc1758||0 votes||123 views||1 replies||Latest 12 days ago by Andy Neil||Answer this|
|Suggested answer||Arm Cortex A57 controller||0 votes||277 views||1 replies||Latest 14 days ago by Tyler_p||Answer this|
|Not answered||M7 to NIC-400 connectivity via AXIM||0 votes||76 views||0 replies||Started 18 days ago by Ramaswamy Vishwanath||Answer this|
|Not answered||access secure generic timer Started 6 days ago by armsss||0 replies 61 views|
|Not answered||How do branch instructions influence the performance of Cortex-A77? Started 8 days ago by hyf_sysu||0 replies 72 views|
|Suggested answer||Getting Dummy character while receiving UART data,How to fix it ? Latest 8 days ago by Jerome Decamps - 杜尚杰||2 replies 445 views|
|Suggested answer||Sht11 interfacing with lpc1758 Latest 12 days ago by Andy Neil||1 replies 123 views|
|Suggested answer||Arm Cortex A57 controller Latest 14 days ago by Tyler_p||1 replies 277 views|
|Not answered||M7 to NIC-400 connectivity via AXIM Started 18 days ago by Ramaswamy Vishwanath||0 replies 76 views|