s/u-boot/U-Boot/g across all files

3 files changed, 35 insertions, 35 deletions

diff --git a/po/da/boot-installer.po b/po/da/boot-installer.po
index 9a8eab0f7..bf6933fb4 100644
--- a/po/da/boot-installer.po
+++ b/po/da/boot-installer.po
@@ -82,10 +82,10 @@ msgstr ""
 #: boot-installer.xml:47
 #, fuzzy, no-c-format
 #| msgid ""
-#| "uImage/uInitrd are image formats designed for the u-boot firmware that is "
-#| "used on many ARM-based systems. Older u-boot versions can only boot files "
+#| "uImage/uInitrd are image formats designed for the U-Boot firmware that is "
+#| "used on many ARM-based systems. Older U-Boot versions can only boot files "
 #| "in uImage/uInitrd format, so these are often used on older armel systems. "
-#| "Newer u-boot versions can - besides booting uImages/uInitrds - also boot "
+#| "Newer U-Boot versions can - besides booting uImages/uInitrds - also boot "
 #| "standard Linux kernels and ramdisk images, but the command syntax to do "
 #| "that is slightly different from that for booting uImages."
 msgid ""
@@ -96,10 +96,10 @@ msgid ""
 "Linux kernels and ramdisk images, but the command syntax to do that is "
 "slightly different from that for booting uImages."
 msgstr ""
-"uImage/uInitrd er aftryksformater designet for firmwaren u-boot, som bruges "
-"på mange ARM-baserede systemer. Ældre versioner af u-boot kan kun opstarte "
+"uImage/uInitrd er aftryksformater designet for firmwaren U-Boot, som bruges "
+"på mange ARM-baserede systemer. Ældre versioner af U-Boot kan kun opstarte "
 "filer i uImage/uInitrd-formatet, så de bruges ofte på ældre armel-systemer. "
-"Nyere versioner af u-boot kan - udover opstarte uImages/uInitrds - også "
+"Nyere versioner af U-Boot kan - udover opstarte uImages/uInitrds - også "
 "opstarte standardkerner med Linux og ramdisk-aftryk, men kommandosyntaksen "
 "til dette er en smule anderledes end at starte fra uImages."
 
@@ -189,15 +189,15 @@ msgstr ""
 #. Tag: title
 #: boot-installer.xml:108
 #, fuzzy, no-c-format
-#| msgid "TFTP-booting in u-boot"
+#| msgid "TFTP-booting in U-Boot"
 msgid "TFTP-booting in U-Boot"
-msgstr "TFTP-opstart i u-boot"
+msgstr "TFTP-opstart i U-Boot"
 
 #. Tag: para
 #: boot-installer.xml:109
 #, fuzzy, no-c-format
 #| msgid ""
-#| "Network booting on systems using the u-boot firmware consists of three "
+#| "Network booting on systems using the U-Boot firmware consists of three "
 #| "steps: a) configuring the network, b) loading the images (kernel/initial "
 #| "ramdisk/dtb) into memory and c) actually executing the previosly loaded "
 #| "code."
@@ -206,7 +206,7 @@ msgid ""
 "steps: a) configuring the network, b) loading the images (kernel/initial "
 "ramdisk/dtb) into memory and c) actually executing the previosly loaded code."
 msgstr ""
-"Netværksopstart på systemer, der bruger firmwaren u-boot, består af tre "
+"Netværksopstart på systemer, der bruger firmwaren U-Boot, består af tre "
 "trin: a) konfiguration af netværket, b) indlæsning af aftrykket (kerne/"
 "initiel ramdisk/dtb) i hukommelsen og c) faktisk kørsel af den tidligere "
 "indlæste kode."
@@ -269,7 +269,7 @@ msgstr ""
 #: boot-installer.xml:132
 #, fuzzy, no-c-format
 #| msgid ""
-#| "On some systems, u-boot predefines a set of environment variables with "
+#| "On some systems, U-Boot predefines a set of environment variables with "
 #| "suitable load addresses: kernel_addr_r, ramdisk_addr_r and fdt_addr_r. "
 #| "You can check whether they are defined by running "
 #| "<informalexample><screen>\n"
@@ -290,7 +290,7 @@ msgid ""
 "name <quote>sun4i</quote> or the Allwinner A20, architecture name "
 "<quote>sun7i</quote>), you can e.g. use the follwing values:"
 msgstr ""
-"På nogle systemer, prædefinerer u-boot et sæt af miljøparametre med egnede "
+"På nogle systemer, prædefinerer U-Boot et sæt af miljøparametre med egnede "
 "indlæsningsadresser: kernel_addr_r, ramdisk_addr_r og fdt_addr_r. Du kan "
 "kontrollere om de er defineret ved at køre <informalexample><screen>\n"
 "printenv kernel_addr_r ramdisk_addr_r fdt_addr_r\n"
@@ -391,7 +391,7 @@ msgstr "bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}"
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Note: When booting standard linux images, it is important to load the "
-#| "initial ramdisk image after the kernel and the dtb as u-boot sets the "
+#| "initial ramdisk image after the kernel and the dtb as U-Boot sets the "
 #| "filesize variable to the size of the last file loaded and the bootz "
 #| "command requires the size of the ramdisk image to work correctly. In case "
 #| "of booting a platform-specific kernel, i.e. a kernel without device-tree, "
@@ -405,7 +405,7 @@ msgid ""
 "the ${fdt_addr_r} parameter."
 msgstr ""
 "Bemærk: Når der opstartes standardaftryk for Linux, så er det vigtigt at "
-"indlæse det oprindelige ramdisk-aftryk efter kernen og dtb'en, da u-boot "
+"indlæse det oprindelige ramdisk-aftryk efter kernen og dtb'en, da U-Boot "
 "angiver filstørrelsesvariablen til størrelsen på den sidst indlæste fil og "
 "kommandoen bootz kræver størrelsen af ramdisk-aftrykket for at fungere "
 "korrekt. I tilfælde hvor der opstartes en platformspecifik kerne, d.v.s. en "
@@ -466,15 +466,15 @@ msgstr ""
 #. Tag: title
 #: boot-installer.xml:206
 #, fuzzy, no-c-format
-#| msgid "Booting from a USB stick in u-boot"
+#| msgid "Booting from a USB stick in U-Boot"
 msgid "Booting from a USB stick in U-Boot"
-msgstr "Opstart fra et USB-hukommelsesdrev i u-boot"
+msgstr "Opstart fra et USB-hukommelsesdrev i U-Boot"
 
 #. Tag: para
 #: boot-installer.xml:207
 #, fuzzy, no-c-format
 #| msgid ""
-#| "Many modern u-boot versions have USB support and allow booting from USB "
+#| "Many modern U-Boot versions have USB support and allow booting from USB "
 #| "mass storage devices such as USB sticks. Unfortunately the exact steps "
 #| "required to do that can vary quite a bit from device to device."
 msgid ""
@@ -482,7 +482,7 @@ msgid ""
 "storage devices such as USB sticks. Unfortunately the exact steps required "
 "to do that can vary quite a bit from device to device."
 msgstr ""
-"Mange moderne u-boot-versioner har USB-understøttelse og tillader opstart "
+"Mange moderne U-Boot-versioner har USB-understøttelse og tillader opstart "
 "fra USB-lagerenheder såsom USB-drev. Desværre er de præcise trin krævet for "
 "dette forskellige fra enhed til enhed."
 
@@ -508,8 +508,8 @@ msgstr ""
 #| msgid ""
 #| "To build a bootable USB stick for installing &debian;, unpack the hd-"
 #| "media tarball (see <xref linkend=\"where-files\"/>) onto a USB stick "
-#| "formatted with a filesystem supported by the u-boot version on your "
-#| "device. For modern u-boot versions, any of FAT16 / FAT32 / ext2 / ext3 / "
+#| "formatted with a filesystem supported by the U-Boot version on your "
+#| "device. For modern U-Boot versions, any of FAT16 / FAT32 / ext2 / ext3 / "
 #| "ext4 usually works. Then copy the ISO image file of the first &debian; "
 #| "installation CD or DVD onto the stick."
 msgid ""
@@ -522,8 +522,8 @@ msgid ""
 msgstr ""
 "For at bygge et USB-drev, der kan startes op fra, til installation af "
 "&debian; udpakkes hd-media-tarball'en (se <xref linkend=\"where-files\"/>) "
-"til et USB-drev formateret med et filsystem, der understøtter u-boot-"
-"versionen på din enhed. For moderne u-boot-versioner, fungerer enhver FAT16/"
+"til et USB-drev formateret med et filsystem, der understøtter U-Boot-"
+"versionen på din enhed. For moderne U-Boot-versioner, fungerer enhver FAT16/"
 "FAT32/ext2/ext3/ext4 normalt. Kopier så ISO-aftryksfilen fra den første "
 "&debian;-installations-cd eller dvd til drevet."
 
@@ -531,12 +531,12 @@ msgstr ""
 #: boot-installer.xml:233
 #, fuzzy, no-c-format
 #| msgid ""
-#| "The autoboot framework in modern u-boot versions works similar to the "
+#| "The autoboot framework in modern U-Boot versions works similar to the "
 #| "boot ordering options in a PC BIOS, i.e. it checks a list of possible "
 #| "boot devices for a valid boot image and starts the first one it finds. If "
 #| "there is no operating system installed, plugging in the USB stick and "
 #| "powering up the system should result in starting the installer. You can "
-#| "also initiate the USB-boot process any time from the u-boot prompt by "
+#| "also initiate the USB-boot process any time from the U-Boot prompt by "
 #| "entering the <quote>run bootcmd_usb0</quote> command."
 msgid ""
 "The autoboot framework in modern U-Boot versions works similar to the boot "
@@ -547,7 +547,7 @@ msgid ""
 "the USB-boot process any time from the U-Boot prompt by entering the "
 "<quote>run bootcmd_usb0</quote> command."
 msgstr ""
-"Autoboot-rammen i moderne u-boot-versioner fungerer på samme måde som "
+"Autoboot-rammen i moderne U-Boot-versioner fungerer på samme måde som "
 "indstillingerne for opstartsrækkefølgen i en PC BIOS, dvs. den kontrollerer "
 "en liste over mulige opstartsenheder for et gyldigt opstartsaftryk og starer "
 "den første den finder. Hvis der ikke er et operativsystem installeret, vil "
@@ -561,15 +561,15 @@ msgstr ""
 #| msgid ""
 #| "One problem that can come up when booting from a USB stick while using a "
 #| "serial console can be a console baudrate mismatch. If a console variable "
-#| "is defined in u-boot, the &d-i; boot script automatically passes it to "
+#| "is defined in U-Boot, the &d-i; boot script automatically passes it to "
 #| "the kernel to set the primary console device and, if applicable, the "
 #| "console baudrate. Unfortunately the handling of the console variable "
 #| "varies from platform to platform - on some platforms, the console "
 #| "variable includes the baudrate (as in <quote>console=ttyS0,115200</"
 #| "quote>), while on other platforms the console variable contains only the "
 #| "device (as in <quote>console=ttyS0</quote>). The latter case leads to a "
-#| "garbled console output when the default baudrate differs between u-boot "
-#| "and the kernel. Modern u-boot versions often use 115200 baud while the "
+#| "garbled console output when the default baudrate differs between U-Boot "
+#| "and the kernel. Modern U-Boot versions often use 115200 baud while the "
 #| "kernel still defaults to the traditional 9600 baud. If this happens, you "
 #| "should manually set the console variable to contain the correct baudrate "
 #| "for your system and then start the installer with the <quote>run "
@@ -592,7 +592,7 @@ msgid ""
 msgstr ""
 "Et problem som kan fremkomme, når der startes op fra et USB-drev, mens der "
 "anvendes en seriel konsol er en konsols baudhastighedsforskel. Hvis en "
-"konsolvariabel er defineret i u-boot, sender &d-i;-opstartskriptet "
+"konsolvariabel er defineret i U-Boot, sender &d-i;-opstartskriptet "
 "automatisk den til kernen for at sætte den primære konsolenhed og, hvis "
 "anvendelig, konsollens baudhastighed. Desværre varierer håndteringen af "
 "konsollens variabler fra platform til platform - på nogle platforme "
@@ -600,7 +600,7 @@ msgstr ""
 "<quote>console=ttyS0,115200</quote>), mens på andre platforme indeholder "
 "konsolvariablen kun enheden (som i <quote>console=ttyS0</quote>). Det sidste "
 "tilfælde fører til et forvansket konsolresultat, når standardbauthastigheden "
-"er forskellig mellem u-boot og kernen. Moderen u-boot-versioner bruger ofte "
+"er forskellig mellem U-Boot og kernen. Moderen U-Boot-versioner bruger ofte "
 "115200 baud mens kernen stadig har en standard å de traditionelle 9600 baud. "
 "Hvis dette opstår, så skal du manuelt sætte konsolvariablen til at indeholde "
 "den korrekte baudhastighed for dit system og så starte "
diff --git a/po/da/hardware.po b/po/da/hardware.po
index f4c673dfe..422c6dd7c 100644
--- a/po/da/hardware.po
+++ b/po/da/hardware.po
@@ -891,7 +891,7 @@ msgstr ""
 #| msgid ""
 #| "Using a local display is technically possible without native display "
 #| "drivers via the <quote>simplefb</quote> infrastructure in the mainline "
-#| "kernel, which relies on the <quote>u-boot</quote> bootloader for "
+#| "kernel, which relies on the <quote>U-Boot</quote> bootloader for "
 #| "initializing the display hardware, but this is not supported by the u-"
 #| "boot version in &debian; 8."
 msgid ""
@@ -902,8 +902,8 @@ msgid ""
 msgstr ""
 "Brug af en lokal skærm er teknisk muligt uden standarddrivere for skærmen "
 "via infrastrukturen <quote>simplefb</quote> i hovedlinjekernen, som afhænger "
-"af opstartsindlæseren <quote>u-boot</quote> for initialisering af "
-"skærmudstyret, men dette er ikke understøttet af u-boot-versionen i &debian; "
+"af opstartsindlæseren <quote>U-Boot</quote> for initialisering af "
+"skærmudstyret, men dette er ikke understøttet af U-Boot-versionen i &debian; "
 "8."
 
 #. Tag: term
diff --git a/po/da/using-d-i.po b/po/da/using-d-i.po
index a286b9247..d4b3c80b8 100644
--- a/po/da/using-d-i.po
+++ b/po/da/using-d-i.po
@@ -5135,12 +5135,12 @@ msgstr ""
 #: using-d-i.xml:3118
 #, no-c-format
 msgid ""
-"For ARM systems that use u-boot as their system firmware and boot the kernel "
+"For ARM systems that use U-Boot as their system firmware and boot the kernel "
 "and the initial ramdisk from external storage media (such as MMC/SD-cards, "
 "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an "
 "appropriate boot script to allow autobooting without user interaction."
 msgstr ""
-"For ARM-systemer som bruger u-boot som deres systemfirmware og starter "
+"For ARM-systemer som bruger U-Boot som deres systemfirmware og starter "
 "kernen og den oprindelige ramdisk fra ekstern lagermedie (såsom MMC/SD-kort, "
 "USB-masselagerenheder eller IDE/SATA-harddiske), opretter flash-kernel et "
 "passende opstartsskript så der automatisk kan startes op uden "