From 3240732cbcf939b2448d29a60ec93764ef3c8122 Mon Sep 17 00:00:00 2001 From: Karsten Merker Date: Wed, 19 Mar 2014 19:27:26 +0000 Subject: Installation guide updates: - updated supported hardware for armel and armhf - removed ia64 and s390 from the supported architecture list for Jessie - updated several common entities for Jessie - some other tiny fixes/updates for Jessie --- en/hardware/supported/arm.xml | 75 ++++++++++++++++++++++++++++++++----------- 1 file changed, 57 insertions(+), 18 deletions(-) (limited to 'en/hardware/supported/arm.xml') diff --git a/en/hardware/supported/arm.xml b/en/hardware/supported/arm.xml index f56a1ae57..b312722a3 100644 --- a/en/hardware/supported/arm.xml +++ b/en/hardware/supported/arm.xml @@ -11,7 +11,7 @@ architecture, where all systems share a common system firmware (BIOS or/and UEFI) which handles the board-specific basic hardware initialization in a standardized way. -The ARM architecture is used mainly in so-called "systems-on-chip" (SOCs). +The ARM architecture is used mainly in so-called systems-on-chip (SOCs). These SOCs are designed by many different companies with vastly varying hardware components even for the very basic functionality required to bring the system up. Systems using them usually lack a common system firmware @@ -25,7 +25,7 @@ mainboard's BIOS in the PC world. At the beginning of the ARM support in the Linux kernel, this resulted in the requirement of having a seperate kernel for each ARM system in contrast -to the "one-fits-all" kernel for PC systems. As this approach does not +to the one-fits-all kernel for PC systems. As this approach does not scale to a large number of different systems, work has started to be able to provide a single ARM kernel that can run on different ARM systems. Support for newer ARM systems gets implemented in a way that allows the use of such @@ -83,20 +83,6 @@ platform-specific kernels. - -IOP32x - - -Intel's I/O Processor (IOP) line is found in a number of products related -to data storage and processing. &debian; currently supports the IOP32x -platform, featuring the IOP 80219 and 32x chips commonly found in Network -Attached Storage (NAS) devices. &debian; explicitly supports two such -devices: the GLAN Tank from -IO-Data and the Thecus N2100. - - - - Kirkwood @@ -144,16 +130,38 @@ test and run &debian; on ARM if you don't have the hardware. +Platforms no longer supported by Debian/armel + + + +IOP32x + + +Intel's I/O Processor (IOP) line is found in a number of products +related to data storage and processing, such as the GLAN Tank from IO-Data and the +Thecus N2100. &debian; has +supported the IOP32x platform in &debian; 7, but does not support +it anymore from version 8 on due to hardware constraints of the platform +which make it unsuitable for the installation of newer &debian; releases. + + + + + + + + Platforms supported by Debian/armhf - The following platforms are supported by &debian;/armhf using the + The following systems are known to work with &debian;/armhf using the multiplatform (armmp) kernel: - Freescale MX53 Quick Start Board, Codename "LOCO" + Freescale MX53 Quick Start Board The IMX53QSB is a development board based on the i.MX53 SOC. @@ -161,8 +169,39 @@ test and run &debian; on ARM if you don't have the hardware. + + + + + + Generally, the ARM multiplatform support in the Linux kernel allows + running &d-i; on armhf systems not explicitly listed above, as long as + the kernel used by &d-i; has support for the target system's components + and a device-tree file for the target is available. In these cases, the + installer can usually provide a working userland installation, but it + probably cannot automatically make the system bootable, as doing that in + many cases requires device-specific information. + + + + When using &d-i; on such systems, you have to manually make the system + bootable at the end of the installation, e.g. by running the required + commands in a shell started from within &d-i;. + + -- cgit v1.2.3