Dell Products Inc.

Aniruddha Suresh Herekar

Deepaganesh Paulraj

Ankit Kumar Singh

James Peter Giannoules

Sumanth Vidyadhara

Lee Eric Ballard

Chandrasekhar Puthillathe

Manjunath Vishwanath

Ajay Shenoy

William C Edwards

Naveen Karthick Chandrasekaran

William Carl Edwards, Iii

Sankara Rao Gara

Jitendra Kumar Rath

Guru Prasad Yadav

Sreenivasula Reddy G

Rohitkumar Arehalli

Sriparna Som

Rajeswari Ayyaswamy

Senthil Kumar Parangusam

Sheshadri Pathpalya Raghavendra Rao

An information handling system may include a host system, a management controller configured to provide out-of-band management of the information handling system, and a network interface controller. The management controller may be configured to: determine an inventory of the network interface controller, the inventory indicating at least one component having a firmware; retrieve a firmware update image for updating the firmware; and cause the network interface controller to boot from the firmware update image, the firmware update image being configured to install an update to the firmware.

Secure smart network interface controller firmware update

An information handling system may include a processor, a data processing unit communicatively coupled to the processor, and a management controller communicatively coupled to the processor and the data processing unit and configured for out-of-band management of the information handling system. The management controller may further be configured to obtain a hardware inventory and capabilities of the data processing unit; based on the hardware inventory and capabilities, generate a firmware capsule for execution during a basic input/output system phase of the data processing unit to cause a secure erasure of contents of a memory of the data processing unit; and communicate the firmware capsule to the data processing unit during an operating system phase of the data processing unit and cause the data processing unit to reboot to its basic input/output system phase in order to execute drivers of the firmware capsule in order to securely erase the memory.

Secure wipe of data processing unit using firmware capsule

An information handling system includes a Unified Extensible Firmware Interface (UEFI) and a management controller. The management controller establishes a communication channel with the UEFI, and provides a memory path associated with a driver associated with an operation to be performed in the UEFI. Based on the memory path, the UEFI receives the requested driver from a memory associated with the UEFI, and loads the requested driver. The UEFI executes the loaded requested driver, and provides an execution status for executed driver to the management controller.

Management controller requests in a UEFI pre-boot environment of an information handling system

In one or more embodiments, one or more systems, one or more methods, and/or one or more processes may boot an operating system; after booting the operating system, determine that a solid state drive has been hot added to a Peripheral Component Interconnect Express (PCIe) port; suppress discovery of the solid state drive by the operating system; determine a policy associated with the solid state drive; determine that a current configuration associated with the solid state drive does not match a configuration associated with the policy associated with the solid state drive; determine that the configuration associated with the policy can be applied to the solid state drive; apply the configuration associated with the policy to the solid state drive without utilizing the operating system; and inform the operating system that the solid state drive has been communicatively coupled to at least one processor via a PCIe root complex.

System and method of configuring non-volatile memory media

Methods, systems, and computer programs for receiving, by an information handling system firmware driver, a request for a feature associated with information handling system firmware, the feature stored in a baseboard management controller; determining a transfer size associated with the feature; identifying a plurality of connectivity points, each of the plurality of connectivity points communicatively coupling the information handling system firmware driver to the baseboard management controller, and each of the plurality of connectivity points associated with a bandwidth; selecting a transport route from the plurality of connectivity points based in part on the transfer size associated with the feature; and in response to selecting the transport route: transmitting the request for the feature to the baseboard management controller via the transport route; receiving the feature from the baseboard management controller via the transport route; and providing the feature to the information handling system firmware for execution.

Identifying a transport route using an information handling system firmware driver

An information handling system may include a processor, one or more storage resources communicatively coupled to the processor, including at least one of the one or more storage resources communicatively coupled to the processor via a storage interface, and a basic input/output system (BIOS) comprising a program of instructions executable by the processor and configured to cause the processor to initialize one or more information handling resources of the information handling system. The BIOS may be further configured to, in response to a request to perform a firmware update to the one or more storage resources, scan for storage resources communicatively coupled to the processor via the storage interface, register unique identifiers associated with the storage resources communicatively coupled to the processor via the storage interface, and perform a firmware update of the storage resources communicatively coupled to the processor via the storage interface based on the unique identifiers.

Systems and methods for update of storage resource firmware

A method and an information handling system (IHS) renders a graphical user interface (GUI) from a remote device using a local storage. An interface controller detects a first event used to initiate access to the GUI at the remote device. The controller requests GUI frame buffer data corresponding to the first event, and GUI change data from the remote device. The GUI change data correspond to respective events that can trigger changes to the GUI. In response to receiving the requested data, the controller provides a first locally-rendered GUI using the GUI frame buffer data. The controller stores the GUI change data in local storage. The controller then detects a second event/interaction via the first locally-rendered GUI and retrieves from local storage a relevant portion of the GUI change data. The controller provides an updated locally-rendered GUI using the relevant portion of GUI change data.

Faster frame buffer rendering over a network

Systems and methods are provided that may be implemented to securely load Unified Extensible Firmware Interface (UEFI) images (e.g., UEFI Applications, UEFI Drivers, UEFI firmware volumes, etc.) onto an information handling system from an authenticated (e.g., OEM authenticated) hardware image source device or 'IO store' (e.g., such as USB device, network file system device, PCIe device, network storage, shared storage, dynamic RAM disk, etc.) based on a UEFI virtual device path that is mapped to an authenticated hardware device path that is established for the authenticated hardware image source device.

Growing community of inventors

Bengaluru, India

Aniruddha Suresh Herekar