Searched full:update (Results 1 – 25 of 493) sorted by relevance
12345678910>>...20
| /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
16 update itself with the image downloaded in to the memory.
21 This driver works with Dell OpenManage or Dell Update Packages for updating
26 OpenManage and Dell Update packages (DUP).
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
41 inform the BIOS to enable the update in the next system reboot.
54 The driver supports two types of update mechanism; monolithic and packetized.
55 These update mechanism depends upon the BIOS currently running on the system.
[all …]
|
| /Documentation/driver-api/pldmfw/ |
| D | index.rst | 4 PLDM Firmware Flash Update Library
8 the PLDM for Firmware Update standard
9 <https://www.dmtf.org/documents/pmci/pldm-firmware-update-specification-100>.
22 implementing device flash update based on firmware files following the PLDM
33 firmware indicates that the update may be performed, the firmware data is
54 Performing a flash update
57 To perform a flash update, the ``pldmfw`` module performs the following
67 indication of whether the update is suitable or not. If any component is
68 not suitable, the update is canceled.
72 actions to finalize the update.
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-intel-wmi-sbl-fw-update | 6 Allow user space entities to trigger update of Slim
8 of 0 and userspace can signal SBL to update firmware,
12 * 0 -> Skip firmware update while rebooting
13 * 1 -> Attempt firmware update on next reboot
|
| D | sysfs-driver-intel-m10-bmc-sec-update | 1 What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/sr_root_entry_hash
11 What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/pr_root_entry_hash
21 What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/bmc_root_entry_hash
31 What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/sr_canceled_csks
39 What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/pr_canceled_csks
47 What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/bmc_canceled_csks
55 What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/flash_count
59 Description: Read only. Returns number of times the secure update
|
| D | sysfs-driver-qat_rl | 7 The supported operations are: add, update, rm, rm_all, and get.
25 * update: Updates the SLA with new values set in the following attributes
80 This is valid only for the following operations: update, rm,
87 * WRITE: rm and update operations
118 Write to this file before sending an "add/update" sla_op, to set
123 * WRITE: add and update operations
152 Write to this file before sending an "add/update" sla_op, to set
157 * WRITE: add and update operations
188 * WRITE: add and update operations
|
| D | sysfs-secvar | 49 What: /sys/firmware/secvar/vars/<variable_name>/update
80 written to an update file as writes can contain more than
81 object data, you should use the size of the update file for
115 supports for signed update of objects, represented as a 16 byte
|
| /Documentation/driver-api/nvdimm/ |
| D | security.rst | 28 update <old_keyid> <new_keyid> - enable or update passphrase.
33 master_update <keyid> <new_keyid> - enable or update master passphrase.
69 5. Update
71 When doing an update, it is expected that the existing key is removed from
74 keyid when doing the update operation. It is also expected that the new key
76 document. The update command written to the sysfs attribute will be with
78 update <old keyid> <new keyid>
118 10. Master Update
120 The command format for doing a master update is:
121 update <old keyid> <new keyid>
[all …]
|
| /Documentation/sound/soc/ |
| D | jack.rst | 20 snd_soc_jack_pins representing DAPM endpoints to update and blocks of
26 connected and so will want to make sure to update both speaker and
41 These represent a DAPM pin to update depending on some of the status
53 input to the system and update a jack by calling snd_soc_jack_report(),
54 specifying a subset of bits to update. The jack detection code should
56 update and the set of things to report when the jack is connected.
71 the list of pins to update then set up one or more jack detection
72 mechanisms to update that jack based on their current status.
|
| /Documentation/networking/devlink/ |
| D | devlink-flash.rst | 11 networking locks in the kernel to perform the flash update. Example use::
17 user space about the progress of the update operation.
41 are provided, it is expected that the device only update firmware binaries
43 preserved across the update. A device may not support every combination and
68 automated firmware update facilities.
83 The firmware update agent is supposed to be able to follow this simple
84 algorithm to update firmware contents, regardless of the device vendor:
94 # Update flash if necessary
102 # Update on-disk file if necessary
|
| /Documentation/arch/x86/ |
| D | usb-legacy-support.rst | 42 in the kernel config or USB Legacy support in the BIOS. A BIOS update
43 could help, but so far no such update exists.
46 is usually fixed by a BIOS update. Check the board
47 manufacturers web site. If an update is not available, disable USB
|
| D | microcode.rst | 21 The kernel can update microcode very early during boot. Loading
117 The microcode engine which receives the microcode update is shared
119 the update is executed on one SMT thread of the core, the sibling
120 "automatically" gets the update.
122 Since the microcode can "simulate" MSRs too, while the microcode update
161 automatically. OS can turn off MCIP at the end of the update for that
167 SMIs are also broadcast to all CPUs in the platform. Microcode update
181 When thread0 of a core is doing the microcode update, if thread1 is
197 Consider, for example, a CPU has patch level 1 and the update is to
204 For instance, say MSR_X is no longer available after an update,
[all …]
|
| /Documentation/trace/ |
| D | events-power.rst | 74 The PM QoS events are used for QoS add/update/remove request and for
75 target/flags update.
83 The third parameter is the current QoS value to update.
85 There are also events used for device PM QoS add/update/remove request.
92 The first parameter gives the device name which tries to add/update/remove
97 And, there are events used for CPU latency QoS add/update/remove request.
|
| /Documentation/filesystems/ |
| D | ocfs2.rst | 59 noatime Do not update access time.
60 relatime(*) Update atime if the previous atime is older than
62 strictatime Always update atime, but the minimum update interval
64 atime_quantum=60(*) OCFS2 will not update atime unless this number
65 of seconds has passed since the last update.
66 Set to zero to always update atime. This option need
|
| /Documentation/devicetree/bindings/riscv/ |
| D | extensions.yaml | 178 as ratified at commit 4a69197e5617 ("Update to ratified state") of
184 is supported as ratified at commit 5059e0ca641c ("update to
283 floating-point instructions, as ratified in commit 64074bc ("Update
290 in commit 64074bc ("Update version numbers for Zfh/Zfinx") of
431 instructions, as ratified in commit 56ed795 ("Update
437 instructions, as ratified in commit 56ed795 ("Update
485 instructions, as ratified in commit 56ed795 ("Update
491 ratified in commit 56ed795 ("Update riscv-crypto-spec-vector.adoc")
497 ratified in commit 56ed795 ("Update riscv-crypto-spec-vector.adoc")
503 multiply instructions, as ratified in commit 56ed795 ("Update
[all …]
|
| /Documentation/crypto/ |
| D | devel-algos.rst | 182 .init() -> .update() -> .final() ! .update() might not be called
188 .init() -> .update() -> .finup() ! .update() may not be called
205 v v ! .update() may not be called
206 .setkey() -> .init() -> .update() -> .export() at all in this scenario.
214 .import -> .update() -> .final() ! .update() may not be called
225 - call .init() and then (as many times) .update()
230 to .init() or .update(), since there might be no chance to free them.
|
| /Documentation/driver-api/firmware/ |
| D | fw_upload.rst | 120 update could take milliseconds or minutes.
124 * status - provides an indication of the progress of a firmware update
125 * error - provides error information for a failed firmware update
126 * remaining_size - tracks the data transfer portion of an update
127 * cancel - echo 1 to this file to cancel the update
|
| /Documentation/bpf/ |
| D | map_hash.rst | 59 parameter can be used to control the update behaviour:
61 - ``BPF_ANY`` will create a new element or update an existing element
64 - ``BPF_EXIST`` will update an existing element
171 This example shows how to create or update hash values using atomic
231 of the map is reached. There are various steps that the update algorithm
251 :alt: Diagram outlining the LRU eviction steps taken during map update.
253 LRU hash eviction during map update for ``BPF_MAP_TYPE_LRU_HASH`` and
258 either a successful update or a failure with various error codes. The key in
261 contention may impact update operations, though the map type and flags may
|
| D | map_devmap.rst | 18 pairs to update the maps with new net devices.
100 - ``BPF_ANY``: Create a new element or update an existing element.
102 - ``BPF_EXIST``: Update an existing element.
199 The following code snippet shows how to update a devmap called ``tx_port``.
209 fprintf(stderr, "Failed to update devmap_ value: %s\n",
216 The following code snippet shows how to update a hash_devmap called ``forward_map``.
227 fprintf(stderr, "Failed to update devmap_ value: %s\n",
|
| D | map_sockmap.rst | 40 in having multiple parser programs the update will return an EBUSY error.
128 Add an entry to, or update a ``map`` referencing sockets. The ``skops`` is used
132 - ``BPF_ANY``: Create a new element or update an existing element.
134 - ``BPF_EXIST``: Update an existing element.
148 Add an entry to, or update a sockhash ``map`` referencing sockets. The ``skops``
153 - ``BPF_ANY``: Create a new element or update an existing element.
155 - ``BPF_EXIST``: Update an existing element.
278 Add or update a socket entry in a sockmap or sockhash.
282 - BPF_ANY: Create a new element or update an existing element.
284 - BPF_EXIST: Update an existing element.
[all …]
|
| /Documentation/devicetree/bindings/pwm/ |
| D | microchip,corepwm.yaml | 37 microchip,sync-update-mask:
48 Each bit of "microchip,sync-update-mask" corresponds to a PWM channel & represents
79 microchip,sync-update-mask = /bits/ 32 <0>;
|
| /Documentation/arch/arm/omap/ |
| D | omap.rst | 11 v4.3+ Update is needed for custom .config files to make sure
15 v4.18+ Update is needed for custom .config files to make sure
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | dlg,da9150-fuel-gauge.yaml | 19 dlg,update-interval:
47 dlg,update-interval = <10000>;
|
| /Documentation/ABI/stable/ |
| D | sysfs-class-ubi | 160 if it is corrupted (e.g., due to an interrupted volume update).
207 Contains ASCII "0\n" if the update marker is not set for this
208 volume, and "1\n" if it is set. The update marker is set when
209 volume update starts, and cleaned when it ends. So the presence
210 of the update marker indicates that the volume is being updated
211 at the moment of the update was interrupted. The later may be
|
| /Documentation/translations/zh_CN/mm/ |
| D | hmm.rst | 165 take_lock(driver->update);
167 release_lock(driver->update);
171 /* Use pfns array content to update device page table,
172 * under the update lock */
174 release_lock(driver->update);
178 driver->update 锁与驱动程序在其 invalidate() 回调中使用的锁相同。该锁必须在调用
|
| /Documentation/RCU/ |
| D | checklist.rst | 38 1. Does the update code have proper mutual exclusion?
68 rcu_read_lock_sched(), or by the appropriate update-side lock.
84 3. Does the update code tolerate concurrent accesses?
91 a. Use the RCU variants of the list and hlist update
120 see valid data at all phases of the update. This is often
159 perfectly legal (if redundant) for update-side code to
274 it usually results in simpler code. So, unless update
288 code using call_rcu() should explicitly limit update rate in
303 One way to stall the updates is to acquire the update-side
313 b. Limiting update rate. For example, if updates occur only
[all …]
|
12345678910>>...20