From b9864636478c2d4fe1d59f7bf0e5e2b29f205e87 Mon Sep 17 00:00:00 2001
From: Karsten Merker <merker@debian.org>
Date: Thu, 20 Mar 2014 19:29:54 +0000
Subject: installation-guide:

Add an "ARM firmware" subsection in the "Pre-Installation
Hardware and Operating System Setup" section.
---
 en/preparing/bios-setup/arm.xml         | 29 +++++++++++++++++++++++++++++
 en/preparing/pre-install-bios-setup.xml |  1 +
 2 files changed, 30 insertions(+)
 create mode 100644 en/preparing/bios-setup/arm.xml

(limited to 'en/preparing')

diff --git a/en/preparing/bios-setup/arm.xml b/en/preparing/bios-setup/arm.xml
new file mode 100644
index 000000000..24c2a0818
--- /dev/null
+++ b/en/preparing/bios-setup/arm.xml
@@ -0,0 +1,29 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- $Id: sparc.xml 43641 2006-12-29 05:23:38Z fjp $ -->
+
+
+  <sect2 arch="arm" id="arm-firmware-overview"><title>ARM firmware</title>
+
+    <para>
+      As already mentioned before, there is unfortunately no standard for
+      system firmware on ARM systems.  Even the behaviour of different
+      systems which use nominally the same firmware can be quite different. 
+      This results from the fact that a large part of the devices using the
+      ARM architecture are embedded systems, for which the manufacturers
+      usually build heavily customized firmware versions and include
+      device-specific patches.  Unfortunately the manufacturers often do not
+      submit their changes and extensions back to the mainline firmware
+      developers, so their changes are not integrated into newer versions of
+      the original firmware.
+    </para>
+    <para>
+      As a result even newly sold systems often use a firmware that is based
+      on a years-old manufacturer-modified version of a firmware whose
+      mainline codebase has evolved a lot further in the meantime and offers
+      additional features or shows different behaviour in certain aspects. 
+      In addition to that, the naming of onboard devices is not consistent
+      between different manufacturer-modified versions of the same firmware,
+      therefore it is nearly impossible to provide usable
+      product-independend instructions for ARM-based systems.
+    </para>
+  </sect2>
diff --git a/en/preparing/pre-install-bios-setup.xml b/en/preparing/pre-install-bios-setup.xml
index 1146432c1..32e3611e4 100644
--- a/en/preparing/pre-install-bios-setup.xml
+++ b/en/preparing/pre-install-bios-setup.xml
@@ -18,6 +18,7 @@ hardware; it is most critically invoked during the bootstrap process
 &bios-setup-powerpc.xml;
 &bios-setup-sparc.xml;
 &bios-setup-s390.xml;
+&bios-setup-arm.xml;
 
   <sect2 arch="x86;powerpc" id="hardware-issues">
   <title>Hardware Issues to Watch Out For</title>
-- 
cgit v1.2.3