| /Linux-v4.19/Documentation/ |
| D | dell_rbu.txt | 2 Usage of the new open sourced rbu (Remote BIOS Update) driver
8 Document demonstrating the use of the Dell Remote BIOS Update driver.
9 for updating BIOS images on Dell servers and desktops.
15 It does not cover the support needed from applications to enable the BIOS to
22 the BIOS on Dell servers (starting from servers sold since 1999), desktops
28 Libsmbios can also be used to update BIOS on Dell systems go to
31 Dell_RBU driver supports BIOS update using the monolithic image and packetized
33 of physical pages having the BIOS image. In case of packetized the app
41 inform the BIOS to enable the update in the next system reboot.
43 The user should not unload the rbu driver after downloading the BIOS image
[all …]
|
| D | svga.txt | 13 allows the use of various special video modes supported by the video BIOS. Due
14 to usage of the BIOS, the selection is limited to boot time (before the
69 with VESA-compliant BIOS]) or a chipset name (e.g., Trident). Direct detection
86 on the VGA BIOS).
95 program will try to ask the BIOS for all possible video mode numbers and test
98 all consistent video modes supported by your BIOS will appear (plus maybe some
120 0x0100 to 0x017f - standard BIOS modes. The ID is a BIOS video mode number
123 0x0200 to 0x08ff - VESA BIOS modes. The ID is a VESA mode ID increased by
128 945=132x28 for the standard Video7 BIOS)
167 Allows to set _any_ BIOS mode including graphic ones and forcing specific
[all …]
|
| /Linux-v4.19/Documentation/acpi/ |
| D | osi.txt | 4 An ACPI BIOS can use the "Operating System Interfaces" method (_OSI)
5 to find out what the operating system supports. Eg. If BIOS
8 and answer YES or NO to the BIOS.
13 This document explains how and why the BIOS and Linux should use these methods.
25 So even though the BIOS may use _OSI to query what version of Windows is running,
26 only a single path through the BIOS has actually been tested.
27 Experience shows that taking untested paths through the BIOS
28 exposes Linux to an entire category of BIOS bugs.
39 using the same BIOS image? Often they need to do something different
41 Here the BIOS should ask exactly what it wants to know:
[all …]
|
| D | initrd_table_override.txt | 14 via upgrading the ACPI tables provided by the BIOS with an instrumented,
30 Complain to your platform/BIOS vendor if you find a bug which is so severe
32 allows you to upgrade the buggy tables before your platform/BIOS vendor
33 releases an upgraded BIOS binary.
35 This facility can be used by platform/BIOS vendors to provide a Linux
39 ACPI BIOS table compatibility with the Linux kernel by modifying old
|
| /Linux-v4.19/Documentation/x86/ |
| D | usb-legacy-support.txt | 7 Also known as "USB Keyboard" or "USB Mouse support" in the BIOS Setup is a
20 system crashes, because the SMM BIOS is not expecting to be in PAE mode.
24 because the SMM BIOS isn't expecting the CPU to be in 64-bit mode. The
25 BIOS manufacturers only test with Windows, and Windows doesn't do 64-bit
36 in the kernel config or USB Legacy support in the BIOS. A BIOS update
39 Problem 3) is usually fixed by a BIOS update. Check the board
41 Legacy support in the BIOS. If this alone doesn't help, try also adding
42 idle=poll on the kernel command line. The BIOS may be entering the SMM
|
| D | amd-memory-encryption.txt | 64 Linux relies on BIOS to set this bit if BIOS has determined that the reduction
82 SME can also be enabled and activated in the BIOS. If SME is enabled and
83 activated in the BIOS, then all memory accesses will be encrypted and it will
84 not be necessary to activate the Linux memory encryption support. If the BIOS
87 by supplying mem_encrypt=on on the kernel command line. However, if BIOS does
|
| D | pat.txt | 211 D E MTRR -> PAT disable Disabled BIOS
213 - np/E PAT -> PAT disable Disabled BIOS
215 E !P/E MTRR -> PAT init Disabled BIOS
216 D !P/E MTRR -> PAT disable Disabled BIOS
217 !M !P/E MTRR stub -> PAT disable Disabled BIOS
229 BIOS PAT keeps PAT MSR with BIOS setting
|
| /Linux-v4.19/Documentation/mtd/ |
| D | intel-spi.txt | 1 Upgrading BIOS using intel-spi
5 controller which is used to hold BIOS and other platform specific data.
11 allows upgrading the BIOS image directly from an OS.
20 Please keep in mind that overwriting the BIOS image on SPI serial flash
24 Below are the steps how to upgrade MinnowBoard MAX BIOS directly from
27 1) Download and extract the latest Minnowboard MAX BIOS SPI image
39 (it is named as "BIOS"):
43 mtd0: 00800000 00001000 "BIOS"
68 8) Once completed without errors you can write the new BIOS image:
73 BIOS image:
[all …]
|
| /Linux-v4.19/Documentation/fb/ |
| D | uvesafb.txt | 8 uvesafb should work with any video card that has a Video BIOS compliant
12 v86d. v86d is used to run the x86 Video BIOS code in a simulated and
33 cards, but which is ultimately limited by the Video BIOS interface.
39 with uvesafb, simply because the Video BIOS doesn't support the
42 ratio, which is what most BIOS-es are limited to.
44 Video BIOS. Note that many nVidia Video BIOS-es claim to be VBE 3.0
98 If the video BIOS of your card incorrectly determines the total
99 amount of video RAM, use this option to override the BIOS (in MiB).
117 has any effect only if the Video BIOS is VBE 3.0 compliant. Use it
120 be ignored and the refresh rate will stay at your BIOS default (60 Hz).
[all …]
|
| D | vesafb.txt | 8 of the BIOS, and use this as framebuffer device /dev/fb0, like the m68k
13 impossible; BIOS calls work in real mode only. VESA BIOS Extensions
69 If this does not work, this might be because your BIOS does not support
71 Even if your board does, it might be the BIOS which does not. VESA BIOS
109 The VESA BIOS provides protected mode interface for changing
112 seems not to work with some BIOS versions, but there are options
170 if the video BIOS of your card incorrectly determines the total
171 amount of video RAM, use this option to override the BIOS (in MiB).
|
| /Linux-v4.19/drivers/gpu/drm/amd/display/dc/bios/ |
| D | Makefile | 26 BIOS = bios_parser.o bios_parser_interface.o bios_parser_helper.o command_table.o command_table_he… macro
28 BIOS += command_table2.o command_table_helper2.o bios_parser2.o
30 AMD_DAL_BIOS = $(addprefix $(AMDDALPATH)/dc/bios/,$(BIOS))
|
| /Linux-v4.19/drivers/pnp/pnpbios/ |
| D | Kconfig | 2 # Plug and Play BIOS configuration
5 bool "Plug and Play BIOS support"
9 Linux uses the PNPBIOS as defined in "Plug and Play BIOS
18 BIOS) say Y here. Also the PNPBIOS can help prevent resource
26 bool "Plug and Play BIOS /proc interface"
|
| /Linux-v4.19/Documentation/acpi/apei/ |
| D | einj.txt | 7 You need to check whether your BIOS supports EINJ first. For that, look
12 which shows that the BIOS is exposing an EINJ table - it is the
19 don't exist: before you give up, go into BIOS setup to see if the BIOS
23 the BIOS menu.
110 this actually works depends on what operations the BIOS actually
113 BIOS versions based on the ACPI 4.0 specification have limited options
114 in controlling where the errors are injected. Your BIOS may support an
120 BIOS versions based on the ACPI 5.0 specification have more control over
144 An ACPI 5.0 BIOS may also allow vendor-specific errors to be injected.
146 from the BIOS that hopefully will allow an application wishing to use
[all …]
|
| /Linux-v4.19/Documentation/hwmon/ |
| D | nct7802 | 22 Tested Boards and BIOS Versions
26 BIOS versions.
28 Board BIOS version
|
| D | k10temp | 20 BIOS and Kernel Developer's Guide (BKDG) For AMD Family 10h Processors:
22 BIOS and Kernel Developer's Guide (BKDG) for AMD Family 11h Processors:
24 BIOS and Kernel Developer's Guide (BKDG) for AMD Family 12h Processors:
26 BIOS and Kernel Developer's Guide (BKDG) for AMD Family 14h Models 00h-0Fh Processors:
75 If the BIOS has enabled hardware temperature control, the threshold at
|
| D | sch5627 | 21 initialization most be done by the BIOS, so if the watchdog is not enabled
22 by the BIOS the sch5627 driver will not register a watchdog device.
|
| /Linux-v4.19/drivers/mtd/maps/ |
| D | Kconfig | 155 mtd0 and mtd2 are the two BIOS drives, which use the resident
158 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
192 tristate "BIOS flash chip on AMD76x southbridge"
195 Support for treating the BIOS flash chip on AMD76x motherboards
196 as an MTD device - with this you can reprogram your BIOS.
201 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
204 Support for treating the BIOS flash chip on ICHX motherboards
205 as an MTD device - with this you can reprogram your BIOS.
210 tristate "BIOS flash chip on Intel ESB Controller Hub 2"
213 Support for treating the BIOS flash chip on ESB2 motherboards
[all …]
|
| /Linux-v4.19/Documentation/scsi/ |
| D | aha152x.txt | 35 Don't test for BIOS signature (AHA-1510 or disabled BIOS)
55 When you do this, the BIOS test is skipped. Entered values have to be
107 The BIOS uses a cylinder/head/sector addressing scheme (C/H/S)
108 scheme instead. DOS expects a BIOS or driver that understands this
115 Therefore the SCSI BIOS/DOS driver has to calculate a logical/virtual
117 returned by the SCSI BIOS is a pure calculation and has nothing to
130 The AHA-1522 BIOS calculates the geometry by fixing the number of heads
138 extended translation. This means that the BIOS uses 255 for heads,
145 not be configurable in certain BIOS setups.
|
| /Linux-v4.19/Documentation/cpu-freq/ |
| D | amd-powernow.txt | 16 The drivers use BIOS supplied tables to obtain frequency and
18 Frequency transitions will be unavailable if the BIOS does
27 is available in the "BIOS and Kernel Developer's Guide", publication
30 BIOS supplied data, for powernow-k7 and for powernow-k8, may be
|
| /Linux-v4.19/Documentation/sound/hd-audio/ |
| D | models.rst | 415 auto-config reading BIOS (default)
481 auto-config reading BIOS (default)
562 BIOS setup (default)
577 BIOS setup (default)
622 BIOS setup (default)
643 BIOS setup (default)
660 Fixes with Dell BIOS setup
662 Fixes with Dell BIOS setup including analog mic
666 BIOS setup (default)
687 BIOS setup (default)
[all …]
|
| /Linux-v4.19/drivers/ntb/hw/idt/ |
| D | Kconfig | 10 by BIOS using slave-SMBus interface changing corresponding registers
25 techniques like BIOS using SMBus interface or EEPROM should be
28 be initialized within BIOS/EEPROM as well.
|
| /Linux-v4.19/Documentation/power/ |
| D | video.txt | 9 initialized by BIOS, and kernel does not have enough information to
13 This is not problem for swsusp, because during swsusp resume, BIOS is
18 We either have to run video BIOS during early resume, or interpret it
43 (2) systems where it is possible to call the video BIOS during S3
44 resume. Unfortunately, it is not correct to call the video BIOS at
49 the BIOS works well enough to be able to set video mode. Use
92 Acer Aspire 1406LC ole's late BIOS init (7), turn off DRI
133 … A31 / Type 2652-M5G s3_mode (3) [works ok with BIOS 1.04 2002-08-23, but not at all with BIO…
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-driver-ppi | 7 Presence Interface). Only if TPM is supported by BIOS, this
50 take place in order to transition to the BIOS for execution of
60 operation to be executed in the pre-OS environment by the BIOS
71 operation to be executed in the pre-OS environment by the BIOS
|
| /Linux-v4.19/drivers/pci/pcie/ |
| D | Kconfig | 98 bool "BIOS default"
101 Use the BIOS defaults for PCI Express ASPM.
108 BIOS did not.
122 Disable PCI Express ASPM L0s and L1, even if the BIOS enabled them.
|
| /Linux-v4.19/drivers/firmware/ |
| D | Kconfig | 94 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
97 Say Y or M here if you want to enable BIOS Enhanced Disk Drive
98 Services real mode BIOS calls to determine which disk
99 BIOS tries boot from. This information is then exported via sysfs.
102 obscure configurations. Most disk controller BIOS vendors do
149 tristate "BIOS update support for DELL systems via sysfs"
154 Say m if you want to have the option of updating the BIOS for your
156 supporting application to communicate with the BIOS regarding the new
|
