/Linux-v5.10/Documentation/admin-guide/ |
D | dell_rbu.rst | 2 Dell Remote BIOS Update driver (dell_rbu) 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.rst | 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 16 booted through BIOS firmware (as opposed to through UEFI, kexec, etc.). 70 with VESA-compliant BIOS]) or a chipset name (e.g., Trident). Direct detection 87 on the VGA BIOS). 96 program will try to ask the BIOS for all possible video mode numbers and test 99 all consistent video modes supported by your BIOS will appear (plus maybe some 121 0x0100 to 0x017f - standard BIOS modes. The ID is a BIOS video mode number 124 0x0200 to 0x08ff - VESA BIOS modes. The ID is a VESA mode ID increased by 129 945=132x28 for the standard Video7 BIOS) [all …]
|
/Linux-v5.10/Documentation/firmware-guide/acpi/ |
D | osi.rst | 7 An ACPI BIOS can use the "Operating System Interfaces" method (_OSI) 8 to find out what the operating system supports. Eg. If BIOS 11 and answer YES or NO to the BIOS. 16 This document explains how and why the BIOS and Linux should use these methods. 28 So even though the BIOS may use _OSI to query what version of Windows is running, 29 only a single path through the BIOS has actually been tested. 30 Experience shows that taking untested paths through the BIOS 31 exposes Linux to an entire category of BIOS bugs. 42 using the same BIOS image? Often they need to do something different 44 Here the BIOS should ask exactly what it wants to know: [all …]
|
/Linux-v5.10/Documentation/x86/ |
D | usb-legacy-support.rst | 11 Also known as "USB Keyboard" or "USB Mouse support" in the BIOS Setup is a 24 system crashes, because the SMM BIOS is not expecting to be in PAE mode. 28 because the SMM BIOS isn't expecting the CPU to be in 64-bit mode. The 29 BIOS manufacturers only test with Windows, and Windows doesn't do 64-bit 42 in the kernel config or USB Legacy support in the BIOS. A BIOS update 46 is usually fixed by a BIOS update. Check the board 48 Legacy support in the BIOS. If this alone doesn't help, try also adding 49 idle=poll on the kernel command line. The BIOS may be entering the SMM
|
D | amd-memory-encryption.rst | 70 Linux relies on BIOS to set this bit if BIOS has determined that the reduction 89 SME can also be enabled and activated in the BIOS. If SME is enabled and 90 activated in the BIOS, then all memory accesses will be encrypted and it will 91 not be necessary to activate the Linux memory encryption support. If the BIOS 94 by supplying mem_encrypt=on on the kernel command line. However, if BIOS does
|
D | pat.rst | 218 D E MTRR -> PAT disable Disabled BIOS 220 - np/E PAT -> PAT disable Disabled BIOS 222 E !P/E MTRR -> PAT init Disabled BIOS 223 D !P/E MTRR -> PAT disable Disabled BIOS 224 !M !P/E MTRR stub -> PAT disable Disabled BIOS 238 BIOS PAT keeps PAT MSR with BIOS setting
|
/Linux-v5.10/Documentation/driver-api/mtd/ |
D | intel-spi.rst | 2 Upgrading BIOS using intel-spi 6 controller which is used to hold BIOS and other platform specific data. 12 allows upgrading the BIOS image directly from an OS. 21 Please keep in mind that overwriting the BIOS image on SPI serial flash 25 Below are the steps how to upgrade MinnowBoard MAX BIOS directly from 28 1) Download and extract the latest Minnowboard MAX BIOS SPI image 40 (it is named as "BIOS"):: 44 mtd0: 00800000 00001000 "BIOS" 69 8) Once completed without errors you can write the new BIOS image: 74 BIOS image:: [all …]
|
/Linux-v5.10/Documentation/fb/ |
D | uvesafb.rst | 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 101 vtotal:n If the video BIOS of your card incorrectly determines the total 102 amount of video RAM, use this option to override the BIOS (in MiB). 119 has any effect only if the Video BIOS is VBE 3.0 compliant. Use it 122 be ignored and the refresh rate will stay at your BIOS default [all …]
|
D | vesafb.rst | 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 74 If this does not work, this might be because your BIOS does not support 76 Even if your board does, it might be the BIOS which does not. VESA BIOS 114 The VESA BIOS provides protected mode interface for changing 117 seems not to work with some BIOS versions, but there are options 181 vtotal:n If the video BIOS of your card incorrectly determines the total 182 amount of video RAM, use this option to override the BIOS (in MiB).
|
/Linux-v5.10/Documentation/firmware-guide/acpi/apei/ |
D | einj.rst | 10 You need to check whether your BIOS supports EINJ first. For that, look 15 which shows that the BIOS is exposing an EINJ table - it is the 22 don't exist: before you give up, go into BIOS setup to see if the BIOS 26 the BIOS menu. 118 this actually works depends on what operations the BIOS actually 121 BIOS versions based on the ACPI 4.0 specification have limited options 122 in controlling where the errors are injected. Your BIOS may support an 128 BIOS versions based on the ACPI 5.0 specification have more control over 152 An ACPI 5.0 BIOS may also allow vendor-specific errors to be injected. 154 from the BIOS that hopefully will allow an application wishing to use [all …]
|
/Linux-v5.10/drivers/pnp/pnpbios/ |
D | Kconfig | 3 # Plug and Play BIOS configuration 6 bool "Plug and Play BIOS support" 10 Linux uses the PNPBIOS as defined in "Plug and Play BIOS 19 BIOS) say Y here. Also the PNPBIOS can help prevent resource 27 bool "Plug and Play BIOS /proc interface"
|
/Linux-v5.10/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-v5.10/Documentation/hwmon/ |
D | nct7802.rst | 27 Tested Boards and BIOS Versions 31 BIOS versions. 34 Board BIOS version
|
D | dell-smm-hwmon.rst | 14 On many Dell laptops the System Management Mode (SMM) BIOS can be 38 pwm1_enable WO Enable or disable automatic BIOS fan 46 Disabling automatic BIOS fan control 49 On some laptops the BIOS automatically sets fan speed every few 53 There is experimental support for disabling automatic BIOS fan 56 (writing ``2`` enables automatic BIOS control again). Even if you have 62 enabling and disabling automatic BIOS fan control are not whitelisted 80 probe the BIOS on your machine and discover the appropriate codes. 146 | +-------------------------------------- 2. BIOS version 149 A negative value, for example -22, indicates that the BIOS doesn't
|
D | sch5627.rst | 25 initialization most be done by the BIOS, so if the watchdog is not enabled 26 by the BIOS the sch5627 driver will not register a watchdog device.
|
D | k10temp.rst | 41 BIOS and Kernel Developer's Guide (BKDG) For AMD Family 10h Processors: 45 BIOS and Kernel Developer's Guide (BKDG) for AMD Family 11h Processors: 49 BIOS and Kernel Developer's Guide (BKDG) for AMD Family 12h Processors: 53 BIOS and Kernel Developer's Guide (BKDG) for AMD Family 14h Models 00h-0Fh Processors: 118 If the BIOS has enabled hardware temperature control, the threshold at
|
/Linux-v5.10/drivers/mtd/maps/ |
D | Kconfig | 188 mtd0 and mtd2 are the two BIOS drives, which use the resident 191 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL. 225 tristate "BIOS flash chip on AMD76x southbridge" 228 Support for treating the BIOS flash chip on AMD76x motherboards 229 as an MTD device - with this you can reprogram your BIOS. 234 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5" 237 Support for treating the BIOS flash chip on ICHX motherboards 238 as an MTD device - with this you can reprogram your BIOS. 243 tristate "BIOS flash chip on Intel ESB Controller Hub 2" 246 Support for treating the BIOS flash chip on ESB2 motherboards [all …]
|
/Linux-v5.10/sound/soc/intel/ |
D | Kconfig | 91 in the BIOS then enable this option by saying Y or m. 100 enabled in the BIOS then enable this option by saying Y or m. 109 enabled in the BIOS then enable this option by saying Y or m. 118 enabled in the BIOS then enable this option by saying Y or m. 127 enabled in the BIOS then enable this option by saying Y or m. 136 enabled in the BIOS then enable this option by saying Y or m. 145 enabled in the BIOS then enable this option by saying Y or m. 154 enabled in the BIOS then enable this option by saying Y or m. 182 GeminiLake or CannonLake platform with the DSP enabled in the BIOS
|
/Linux-v5.10/Documentation/scsi/ |
D | aha152x.rst | 46 Don't test for BIOS signature (AHA-1510 or disabled BIOS) 69 When you do this, the BIOS test is skipped. Entered values have to be 126 The BIOS uses a cylinder/head/sector addressing scheme (C/H/S) 127 scheme instead. DOS expects a BIOS or driver that understands this 134 Therefore the SCSI BIOS/DOS driver has to calculate a logical/virtual 136 returned by the SCSI BIOS is a pure calculation and has nothing to 149 The AHA-1522 BIOS calculates the geometry by fixing the number of heads 157 extended translation. This means that the BIOS uses 255 for heads, 164 not be configurable in certain BIOS setups.
|
/Linux-v5.10/Documentation/sound/hd-audio/ |
D | models.rst | 420 auto-config reading BIOS (default) 486 auto-config reading BIOS (default) 567 BIOS setup (default) 582 BIOS setup (default) 627 BIOS setup (default) 648 BIOS setup (default) 665 Fixes with Dell BIOS setup 667 Fixes with Dell BIOS setup including analog mic 671 BIOS setup (default) 692 BIOS setup (default) [all …]
|
/Linux-v5.10/Documentation/admin-guide/acpi/ |
D | initrd_table_override.rst | 12 via upgrading the ACPI tables provided by the BIOS with an instrumented, 35 Complain to your platform/BIOS vendor if you find a bug which is so severe 37 allows you to upgrade the buggy tables before your platform/BIOS vendor 38 releases an upgraded BIOS binary. 40 This facility can be used by platform/BIOS vendors to provide a Linux 44 ACPI BIOS table compatibility with the Linux kernel by modifying old
|
/Linux-v5.10/drivers/mtd/spi-nor/controllers/ |
D | Kconfig | 40 and is used to hold BIOS and other persistent settings. Using 41 this driver it is possible to upgrade BIOS directly from Linux. 56 Intel hardware and is used to hold BIOS and other persistent 57 settings. Using this driver it is possible to upgrade BIOS
|
/Linux-v5.10/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-v5.10/Documentation/power/ |
D | video.rst | 10 initialized by BIOS, and kernel does not have enough information to 14 This is not problem for swsusp, because during swsusp resume, BIOS is 19 We either have to run video BIOS during early resume, or interpret it 44 (2) systems where it is possible to call the video BIOS during S3 45 resume. Unfortunately, it is not correct to call the video BIOS at 50 the BIOS works well enough to be able to set video mode. Use 95 Acer Aspire 1406LC ole's late BIOS init (7), turn off DRI 148 BIOS 1.04 2002-08-23, but not at all with 149 BIOS 1.11 2004-11-05 :-(]
|
/Linux-v5.10/Documentation/admin-guide/pm/ |
D | cpufreq_drivers.rst | 32 The drivers use BIOS supplied tables to obtain frequency and 34 Frequency transitions will be unavailable if the BIOS does 43 is available in the "BIOS and Kernel Developer's Guide", publication 46 BIOS supplied data, for powernow-k7 and for powernow-k8, may be 163 the system with a single call to the BIOS. 190 However, it is possible to disable this interface via a BIOS setting. In 223 frequencies need to be listed because the BIOS will try to achieve any 237 conditions are met the BIOS can achieve a slightly higher speed than requested 245 nominal frequency from the BIOS, sometimes, the values displayed by
|