↑ arvau

Wikipedia / List of Linux-supported computer architectures

The basic components of the Linux family of operating systems, which are based on the Linux kernel, the GNU C Library, BusyBox or forks thereof like μClinux and uClibc, have been programmed with a certain level of abstraction in mind. Also, there are distinct code paths in the assembly language or C source code which support certain hardware. Therefore, the source code can be successfully compiled onor cross-compiled fora great number of computer architectures.

Furthermore, the required free and open-source software has also been developed to interface between Linux and the hardware Linux is to be executed on. For example, compilers are available, e.g. GNU Compiler Collection (GCC) and LLVM/Clang. For cross-compilation a number of complete toolchains are available, like GNU toolchain, OpenWrt (Buildroot), and OpenEmbedded. The Yocto Project is targeted at embedded use cases.

The portability section of the Linux kernel article contains information and references to technical details.

Note that further components like a windowing system, or programs like Blender, can be present or absent. Fundamentally any software has to be ported, i.e. specifically adapted, to any kind of hardware it is supposed to be executed on. The level of abstraction that has been kept in mind while programming that software in the first place dictates the necessary effort.

The relevant term is of the porting target is computer architecture; it comprises the instruction set(s) and the microarchitecture(s) of the processor(s), at least of the CPU. The target also comprises the "system design" of the entire system, be it a supercomputer, a desktop computer or some SoC, e.g. in case some unique bus is being used. In former times, the memory controller was part of the chipset on the motherboard and not on the CPU-die.

Although the support of a specific instruction set is the task of the compiler, the software must be written with a certain level of abstraction in mind to make this portability possible. Any code written in Assembly language will be specific to the instruction set.

The support of a specific microarchitecture includes optimizations for the CPU cache hierarchy, the TLB, etc.

Releases

ARM family of instruction sets (32- and 64-bit) (arm and arm64):

Loongson

  • LoongArch32 (loongarch32)

  • LoongArch64 (loongarch64)

Freescale's (formerly Motorola's) 68k architecture (68020, 68030, 68040, 68060) (m68k):

MIPS architecture (mips):

OpenRISC (openrisc)

PowerPC architecture (powerpc):

SuperH (sh)

SPARC (sparc)

SPARC (32-bit):

UltraSPARC (64-bit):

x86 architecture (x86):

IBM PC compatibles using IA-32 and x86-64 processors:

VIA Technologies Eden (Samuel II), VIA C3, and VIA C7 processors (all 32-bit) and VIA Nano (x86-64)

Additional processors (particularly Freescale's 68000 and ColdFire) are supported by the MMU-less μClinux variant.

Formerly supported

Dropped in 6.15

Dropped in 6.7

Dropped in 5.19

Dropped in 5.18

Dropped in 5.12

Dropped in 5.9

Dropped in 4.17

Dropped in 4.12

Dropped in 3.14

Dropped in 3.8

Dropped in 3.5

Dropped in 2.6.27

See also

References