Lines Matching full:is
18 Determine whether a given device path is valid.
23 @retval TRUE DevicePath is valid.
24 @retval FALSE DevicePath is NULL.
25 @retval FALSE Maxsize is less than sizeof(EFI_DEVICE_PATH_PROTOCOL).
26 @retval FALSE The length of any node node in the DevicePath is less
28 @retval FALSE If MaxSize is not zero, the size of the DevicePath
30 @retval FALSE If PcdMaximumDevicePathNodeCount is not zero, the node
45 If Node is NULL, then ASSERT().
63 If Node is NULL, then ASSERT().
80 Node is not required to be aligned on a 16-bit boundary, so it is recommended
84 If Node is NULL, then ASSERT().
102 If Node is NULL, then ASSERT().
116 Determines if a device path node is an end node of a device path.
120 Determines if the device path node specified by Node is an end node of a device path.
123 then TRUE is returned. Otherwise, FALSE is returned.
125 If Node is NULL, then ASSERT().
129 @retval TRUE The device path node specified by Node is an end node of a device path.
130 @retval FALSE The device path node specified by Node is not an end node of a device path.
140 Determines if a device path node is an end node of an entire device path.
142 Determines if a device path node specified by Node is an end node of an entire device path.
143 If Node represents the end of an entire device path, then TRUE is returned.
144 Otherwise, FALSE is returned.
146 If Node is NULL, then ASSERT().
150 @retval TRUE The device path node specified by Node is the end of an entire device path.
151 @retval FALSE The device path node specified by Node is not the end of an entire device path.
161 Determines if a device path node is an end node of a device path instance.
163 Determines if a device path node specified by Node is an end node of a device path instance.
164 If Node represents the end of a device path instance, then TRUE is returned.
165 Otherwise, FALSE is returned.
167 If Node is NULL, then ASSERT().
171 @retval TRUE The device path node specified by Node is the end of a device path instance.
172 @retval FALSE The device path node specified by Node is not the end of a device path instance.
185 by NodeLength. NodeLength is returned. Node is not required to be aligned on
186 a 16-bit boundary, so it is recommended that a function such as WriteUnaligned16()
189 If Node is NULL, then ASSERT().
207 Fills in all the fields of a device path node that is the end of an entire device path.
210 the end of an entire device path. The Type field of Node is set to
211 END_DEVICE_PATH_TYPE, the SubType field of Node is set to
212 END_ENTIRE_DEVICE_PATH_SUBTYPE, and the Length field of Node is set to
213 END_DEVICE_PATH_LENGTH. Node is not required to be aligned on a 16-bit boundary,
214 so it is recommended that a function such as WriteUnaligned16() be used to set
217 If Node is NULL, then ASSERT().
233 If DevicePath is NULL or invalid, then 0 is returned.
237 @retval 0 If DevicePath is NULL or invalid.
251 DevicePath is NULL, then NULL is returned. If the memory is successfully allocated, then the
253 is returned. Otherwise, NULL is returned.
254 The memory for the new device path is allocated from EFI boot services memory.
255 It is the responsibility of the caller to free the memory allocated.
259 @retval NULL DevicePath is NULL or invalid.
274 SecondDevicePath is retained. The newly created device path is returned.
275 If FirstDevicePath is NULL, then it is ignored, and a duplicate of SecondDevicePath is returned.
276 If SecondDevicePath is NULL, then it is ignored, and a duplicate of FirstDevicePath is returned.
277 If both FirstDevicePath and SecondDevicePath are NULL, then a copy of an end-of-device-path is
279 If there is not enough memory for the newly allocated buffer, then NULL is returned.
280 The memory for the new device path is allocated from EFI boot services memory. It is the
286 @retval NULL If there is not enough memory for the newly allocated buffer.
287 @retval NULL If FirstDevicePath or SecondDevicePath is invalid.
304 The end-of-device-path device node is moved after the end of the appended device node.
305 If DevicePathNode is NULL then a copy of DevicePath is returned.
306 If DevicePath is NULL then a copy of DevicePathNode, followed by an end-of-device path device
307 node is returned.
309 is returned.
310 If there is not enough memory to allocate space for the new device path, then NULL is returned.
311 The memory is allocated from EFI boot services memory. It is the responsibility of the caller to
317 @retval NULL There is not enough memory for the new device path.
337 The end-of-device-path device node is moved after the end of the appended device path instance
338 and a new end-of-device-path-instance node is inserted between.
339 If DevicePath is NULL, then a copy if DevicePathInstance is returned.
340 If DevicePathInstance is NULL, then NULL is returned.
341 If DevicePath or DevicePathInstance is invalid, then NULL is returned.
342 If there is not enough memory to allocate space for the new device path, then NULL is returned.
343 The memory is allocated from EFI boot services memory. It is the responsibility of the caller to
366 If DevicePath is NULL, then NULL is returned.
367 If DevicePath points to a invalid device path, then NULL is returned.
368 If there is not enough memory to allocate space for the new device path, then NULL is returned.
369 The memory is allocated from EFI boot services memory. It is the responsibility of the caller to
371 If Size is NULL, then ASSERT().
379 bytes or zero, if DevicePath is NULL.
396 is returned.
397 If NodeLength is smaller than a device path header, then NULL is returned.
398 If there is not enough memory to allocate space for the new device path, then NULL is returned.
399 The memory is allocated from EFI boot services memory. It is the responsibility of the caller to
418 Determines if a device path is single or multi-instance.
420 This function returns TRUE if the device path specified by DevicePath is multi-instance.
421 Otherwise, FALSE is returned.
422 If DevicePath is NULL or invalid, then FALSE is returned.
426 @retval TRUE DevicePath is multi-instance.
427 …@retval FALSE DevicePath is not multi-instance, or DevicePath is NULL or inva…
439 This function returns the device path protocol from the handle specified by Handle. If Handle is
440 NULL or Handle does not contain a device path protocol, then NULL is returned.
456 If Device is a valid device handle that contains a device path protocol, then a device path for
457 the file specified by FileName is allocated and appended to the device path associated with the
458 handle Device. The allocated device path is returned. If Device is NULL or Device is a handle
460 path node for the file specified by FileName is allocated and returned.
461 …The memory for the new device path is allocated from EFI boot services memory. It is the responsib…
464 If FileName is NULL, then ASSERT().
465 If FileName is not aligned on a 16-bit boundary, then ASSERT().
467 @param Device A pointer to a device handle. This parameter is optional and
485 @param DisplayOnly If DisplayOnly is TRUE, then the shorter text representation
486 of the display node is used, where applicable. If DisplayOnly
487 is FALSE, then the longer text representation of the display node
488 is used.
489 @param AllowShortcuts If AllowShortcuts is TRUE, then the shortcut forms of text
493 NULL if DeviceNode is NULL or there was insufficient memory.
508 @param DisplayOnly If DisplayOnly is TRUE, then the shorter text representation
509 of the display node is used, where applicable. If DisplayOnly
510 is FALSE, then the longer text representation of the display node
511 is used.
512 @param AllowShortcuts If AllowShortcuts is TRUE, then the shortcut forms of text
516 is NULL or there was insufficient memory.
534 @return A pointer to the EFI device node or NULL if TextDeviceNode is NULL or there was
551 @return A pointer to the allocated device path or NULL if TextDeviceNode is NULL or