Architectures/MIPS

Fedora MIPS

This is the starting page for the Fedora port to the MIPS architecture.

Goals and Objectives

The primary goal of this project is to provide support for MIPS as a secondary architecture in Fedora.

Just like the ARM port, our secondary goal is to enable derivative distributions based on the Fedora package collection and repository that are more suitably optimized for embedded and mobile use-cases.

CPU and Architecture Target

Currently we have chosen to support Loongson 2F, but in time we will also support other MIPS-compatible processors.

Information of Loongson CPU can be found on http://www.linux-mips.org/wiki/Loongson, http://www.loongson.cn/ and forum http://bbs.lemote.com/.

Fedora MIPS Repositories

Test Release: Fedora 12

This is a new release for MIPS N32 ABI based on Fedora 12 GA

• Not yet a completed release, just enough for GNOME desktop and development tools
  • http://lazyfai.dyndns.org/Fedora-12-RPMS-MIPS/
  • http://files.mips101.org/Fedora-12-RPMS-MIPS/
• Modified Source RPMs are here:
  • http://lazyfai.dyndns.org/Fedora-12-SRPMS-MIPS/
  • http://files.mips101.org/Fedora-12-SRPMS-MIPS/
• Tarball for root filesystem and QEMU-mips64el runnable image can be found here:
  • http://lazyfai.dyndns.org/Fedora-12-rootfs-MIPS/
  • http://files.mips101.org/Fedora-12-rootfs-MIPS/

(Default root password is "fedora")

Older releases

See this page

How to get in touch?

• The Fedora-MIPS mailing list is available for both user and developer discussions.
• We have an IRC channel: #fedora-mips on Freenode
• Frequent updates about the effort are available at the Fedora-MIPS blog

Bugs and issues

Bug or other issues you encounter can be issued at our Trac instance https://fedorahosted.org/mips/.

Issues we currently have with building are decribed on the page Architectures/MIPS/BuildIssues

Maintainer Team

• Gerard Braad (team lead) (Fedora Account: gbraad)
• XinZhen (co-lead) (Fedora Account: lonestar)
• FaiWong (tech lead) (Fedora Account: lazyfai)

Interested in joining our team? Contact us in the IRC channel.