summaryrefslogtreecommitdiff
path: root/en/preparing
diff options
context:
space:
mode:
authorKarsten Merker <merker@debian.org>2014-03-20 19:29:54 +0000
committerKarsten Merker <merker@debian.org>2014-03-20 19:29:54 +0000
commitb9864636478c2d4fe1d59f7bf0e5e2b29f205e87 (patch)
treeda4eb76869a5d1600155046afaf9fea9ae1c4462 /en/preparing
parent3240732cbcf939b2448d29a60ec93764ef3c8122 (diff)
downloadinstallation-guide-b9864636478c2d4fe1d59f7bf0e5e2b29f205e87.zip
installation-guide:
Add an "ARM firmware" subsection in the "Pre-Installation Hardware and Operating System Setup" section.
Diffstat (limited to 'en/preparing')
-rw-r--r--en/preparing/bios-setup/arm.xml29
-rw-r--r--en/preparing/pre-install-bios-setup.xml1
2 files changed, 30 insertions, 0 deletions
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>