summaryrefslogtreecommitdiff
path: root/en
diff options
context:
space:
mode:
authorCyril Brulebois <kibi@debian.org>2023-01-30 05:31:33 +0100
committerCyril Brulebois <kibi@debian.org>2023-01-30 05:31:33 +0100
commit2b19f0b8fe5bf1bcecb033c0d6fcccfd51d5e171 (patch)
treee47f6871169f86992d0c9703bd810d821281865b /en
parent45705e21578a61406d79406afd4a38b47417bc92 (diff)
downloadinstallation-guide-2b19f0b8fe5bf1bcecb033c0d6fcccfd51d5e171.zip
Delete section about https://packages.debian.org/search?keywords=firmware
Given the way debian-cd's make-firmware-image works, it seems quite unlikely (even if always possible, lots of changes there lately!) that we would be missing actual firmware packages, i.e. packages which have a good-looking name *and* actual firmware files in the expected location. Sending users on a wild goose chase seems like a waste of everyone's time.
Diffstat (limited to 'en')
-rw-r--r--en/using-d-i/loading-firmware.xml14
1 files changed, 0 insertions, 14 deletions
diff --git a/en/using-d-i/loading-firmware.xml b/en/using-d-i/loading-firmware.xml
index fe9eae9fd..c16922532 100644
--- a/en/using-d-i/loading-firmware.xml
+++ b/en/using-d-i/loading-firmware.xml
@@ -79,20 +79,6 @@ the file system on the medium.
</para><para>
-If the firmware you need is not included in the tarball, you can also
-download specific firmware packages from the (non-free section of the)
-archive. The following overview should list most available firmware
-packages but is not guaranteed to be complete and may also contain
-non-firmware packages:
-
-<itemizedlist>
-<listitem><para>
-<ulink url="&url-firmware-packages;"/>
-</para></listitem>
-</itemizedlist>
-
-</para><para>
-
It is also possible to copy individual firmware files to the medium. Loose
firmware could be obtained for example from an already installed system or
from a hardware vendor.