Method, device and equipment capable of responding to key input at early stage of firmware and medium

Abstract

The invention discloses a method, a device, equipment and a medium capable of responding to key input in the early stage of firmware, and relates to the technical field of computers, and the method comprises the following steps: in the PEI stage of the firmware, initializing a USB controller and configuring input equipment connected to the USB controller; starting from the PEI stage, recording key information input by a user through the input equipment; and in a BDS stage of firmware, executing a corresponding starting strategy based on the recorded key information. According to the method, the problems of short operation window and poor experience caused by firmware response lag are systematically solved, an interaction environment of coherent response in the whole process from starting to ending is constructed, and the user control force and the interaction experience are remarkably improved.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method, apparatus, device, and medium that can respond to key inputs early in the firmware process. Background Technology

[0002] During the computer system startup process, the Basic Input / Output System (BIOS) is responsible for performing a series of critical tasks, including hardware initialization, self-test, and booting the operating system. This startup process typically involves the PEI (Pre-EFI Initialization) stage, the DXE (Driver Execution Environment) stage, and the POST (Power-On Self-Test) stage. The POST stage, being a relatively late stage in the startup process, is responsible for comprehensive testing and configuration of the system hardware. In current implementations, firmware responses to user commands issued via external input devices (such as a USB keyboard) are usually designed to begin during the POST stage or a subsequent stage. This design means that from the moment the computer is powered on until the system enters the POST stage, where keyboard input can be recognized, there is a waiting period during which the user cannot interact with the firmware.

[0003] During this waiting period, users can observe the system's internal initialization process but cannot input any commands via buttons. Only when the startup process reaches a specific stage and a brief prompt appears on the screen offering selectable functions (such as a hotkey for accessing the settings interface), do users have a very limited window to operate. Because this prompt is displayed very briefly and at a fixed time, users must concentrate intently on the screen to quickly press the corresponding button when it appears. Any deviation in timing, whether slightly earlier or later, may render the button press ineffective, preventing the system from capturing and responding to the user's input.

[0004] Furthermore, due to the lack of an effective real-time feedback mechanism, users often cannot immediately receive confirmation from the screen that their operation has been successfully received by the system after pressing a function key. This uncertainty makes it difficult for users to determine whether the key press was effective, leading them to tend to repeatedly press the same key to ensure that at least one input is correctly recognized by the system. This interaction mode not only increases the user's operational burden but also makes the entire startup process less intuitive and user-friendly. Summary of the Invention

[0005] The present invention provides a method, apparatus, device, and medium for responding to key inputs in the early stages of firmware development, aiming to solve at least one of the technical problems mentioned in the background art.

[0006] In a first aspect, embodiments of the present invention provide a method for responding to key inputs in the early stages of firmware development, comprising: During the PEI phase of the firmware, the USB controller is initialized and the input devices connected to the USB controller are configured; Starting from the PEI stage, the key input information entered by the user through the input device is recorded; During the BDS phase of the firmware, the corresponding boot strategy is executed based on the recorded key information.

[0007] A further technical solution is that the method further includes: The DXE stage takes over the configuration of the USB controller and input device from the PEI stage to maintain the continuity of key recording.

[0008] A further technical solution is that the method further includes: in the PEI stage, outputting hotkey prompts on the display to prompt the user to perform operations.

[0009] A further technical solution is that, after recording the key information input by the user through the input device, the method further includes: outputting feedback information on the display to indicate that the key information has been received and responded to.

[0010] A further technical solution is that the button information includes hotkey instructions for triggering at least one of the following functions: entering the firmware settings interface, the boot menu, the system recovery mode, or the diagnostic mode.

[0011] A further technical solution is that, in the BDS stage of the firmware, the corresponding startup strategy is executed based on the recorded key information, including: if the recorded key information is a startup menu hotkey instruction, then the startup device selection menu is called and displayed.

[0012] A further technical solution is that the hotkey prompt information and the feedback information are displayed in different positions on the screen.

[0013] Secondly, embodiments of the present invention also provide an apparatus that can respond to key inputs early in the firmware process, comprising a unit for performing the above-described method.

[0014] Thirdly, embodiments of the present invention also provide a computer device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the above-described method.

[0015] Fourthly, embodiments of the present invention also provide a computer-readable storage medium storing a computer program that, when executed by a processor, can implement the above-described method.

[0016] This invention provides a method, apparatus, device, and medium for responding to key inputs early in the firmware lifecycle. The method includes: initializing a USB controller and configuring an input device connected to the USB controller during the PEI phase of the firmware; recording key input information from the user via the input device starting from the PEI phase; and executing a corresponding startup strategy based on the recorded key input information during the BDS phase of the firmware. This invention advances the initialization of the USB controller and input device to the firmware PEI phase, allowing users to input effectively from the moment the device is powered on, significantly extending the operation window. The continuous key input recording mechanism starting from the PEI phase ensures reliable capture of user input during firmware transitions. Finally, the recorded key commands are executed during the BDS phase, accurately implementing the user's intent into the startup strategy. This solution systematically solves the problem of short operation windows and poor user experience caused by firmware response delays, constructing a seamless interactive environment from startup to completion, significantly improving user control and interactive experience. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 A flowchart illustrating a method for responding to key inputs in the early stages of firmware development, as provided in an embodiment of the present invention; Figure 2 This is a schematic block diagram of a computer device provided in an embodiment of the present invention. Detailed Implementation

[0019] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0020] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0021] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0022] It should also be further understood that the term "and / or" as used in this specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0023] As used in this specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if [described condition or event] is detected" may be interpreted, depending on the context, as "once determined," "in response to determination," "once [described condition or event] is detected," or "in response to detection of [described condition or event]."

[0024] Please see Figure 1 This invention provides a method for responding to key inputs early in the firmware process, the method comprising the following steps: S1, during the PEI phase of the firmware, the USB controller is initialized and the input device connected to the USB controller is configured. The input device may be, for example, a keyboard device, but this invention is not specifically limited thereto.

[0025] In practice, the initialization of the USB controller and connected input devices is performed during the PEI phase of the firmware. This significantly advances the timing of input device preparation, which was traditionally completed later. It breaks the limitation of the original technology where users had to wait until the POST phase to input data, allowing the user operation channel to be established from the initial hardware self-test upon system power-on. This is equivalent to opening a parallel interactive channel for the firmware boot process, allowing users to input commands simultaneously with hardware testing. This transforms the previously wasted waiting time into an effective operation window, fundamentally solving the problem of a short user operation window caused by delayed response times.

[0026] In some preferred embodiments, initializing the USB controller specifically includes initializing the USB XHCI controller. XHCI is currently the mainstream and advanced USB host controller interface standard, especially supporting high-speed protocols such as USB 3.0 and later. The initialization of the XHCI controller is completed during the timing-critical PEI stage. This ensures early compatibility with a large number of modern USB keyboards, especially those relying on high-speed USB interfaces.

[0027] S2, starting from the PEI stage, record the key information input by the user through the input device.

[0028] In practice, user keystroke information is recorded starting from the PEI stage, constructing a continuous input capture mechanism that spans the early stages of firmware startup. Since the system will enter subsequent stages such as DXE after the PEI stage, the internal state of the firmware constantly changes during this process. Continuous recording ensures that regardless of how the system state evolves, the user's input intent can be reliably captured without loss. This eliminates the need for users to worry about which specific stage the firmware is currently executing or to precisely calculate keystroke timing, greatly reducing the possibility of invalid input due to stage transitions or internal processing delays, thereby improving the determinism and reliability of input operations.

[0029] It is clarified that keystroke recording does not end in the PEI phase but continues into subsequent phases. For example, the DXE phase is the core period when the firmware loads and executes a large number of drivers. During this time, the system state undergoes complex changes, but the monitoring and recording of user input remains uninterrupted. This continuity ensures that regardless of when the user presses a key in the middle, late PEI, or DXE phase, their input intention can be reliably captured by the system. This greatly reduces the risk of losing user input due to internal firmware phase switching and improves the reliability of the interaction.

[0030] In some preferred embodiments, the configuration of the USB controller and input device in the DXE stage is taken over from the PEI stage to maintain the continuity of key recording.

[0031] In practice, by taking over and maintaining the configuration of the USB controller and input devices from the PEI stage during the DXE stage, problems such as hardware controller reset, configuration loss, or driver reinitialization caused by stage switching are avoided. This seamless connection mechanism ensures that the keyboard input channel remains uninterrupted and consistent throughout the entire firmware initialization cycle, which is the technical foundation for realizing the "continuous recording" function, thus providing users with a smooth and uninterrupted interactive experience.

[0032] In some preferred embodiments, the method further includes the following step: during the PEI stage, outputting hotkey prompts on the display to prompt the user to perform operations.

[0033] In practice, by displaying hotkey prompts on the screen during the PEI stage, clear operational guidance is provided to users from the very beginning of system startup. Users do not need to rely on memory or guesswork to understand which functions the system supports, nor do they need to worry about being unable to operate due to missing the brief on-screen prompts. This is equivalent to establishing a simple user interface in the early stages of system startup, significantly lowering the technical threshold and enabling even non-professional users to easily and accurately press the correct function key at the correct time, thereby improving the ease of use and user experience.

[0034] In some preferred embodiments, the method further includes the step of outputting feedback information on a display to indicate that the key information has been received and responded to.

[0035] In practice, when a user presses a function key, the system immediately outputs feedback information on the screen. This provides a visual confirmation signal for each user action, directly solving the problem of users repeatedly pressing keys to confirm whether the system is responding and eliminating uncertainty in the operation. For example, after a user presses the F12 key, the screen immediately displays "Startup menu command received," giving the user clear positive feedback, enhancing the user's sense of control over the system and confidence in the interaction process, making the entire startup process more intuitive and user-friendly.

[0036] In some preferred embodiments, the hotkey prompts and the feedback information are displayed in different positions on the screen.

[0037] In practice, by displaying hotkey prompts and operation feedback information in different screen locations, a clear information structure is achieved. This design avoids later feedback information from overwriting or confusing earlier prompts, making the user interface cleaner and more organized. Users can easily associate dynamically appearing feedback information with static initial prompts without them interfering with each other. This visual distinction enhances the logic and readability of the human-computer interaction interface, especially in the early startup phase where screen display area is limited, enabling more effective communication of information to users and further optimizing the clarity and user-friendliness of the interaction.

[0038] In some preferred embodiments, the key information includes hotkey instructions for triggering at least one function among firmware settings interface, boot menu, system recovery mode, or diagnostic mode.

[0039] In practical implementation, by specifically defining the function types corresponding to the key information, the substantive control capabilities achievable by this invention are clearly defined. These hotkey instructions cover key startup scenarios such as firmware settings, boot device selection, system recovery, and diagnostics, making this early input method no longer a single-function method but a universal early interaction platform. This limitation reveals the broad application prospects of this invention, allowing users to quickly trigger different system-level functions through a unified early key entry point at various stages of product production, testing, maintenance, and daily use, greatly enhancing the flexibility and convenience of firmware in dealing with different scenarios.

[0040] S3, in the BDS stage of the firmware, executes the corresponding startup strategy based on the recorded key information.

[0041] In practical implementation, the BDS (Boot Device Selection) stage, based on previously recorded key press information, executes the corresponding boot strategy, achieving effective linkage between early user input and final system behavior. It translates the user's initial intent into specific control actions at the critical decision point before the system boots the operating system. For example, if the user presses the boot menu selection key at the moment of power-on, the system will automatically present the selection interface as it prepares to boot the device, without requiring the user to wait for specific prompts before taking action. This design allows early user input to substantially influence the boot process, achieving a delayed response mode of "early input, late execution," ensuring both smooth system initialization and the ultimate realization of user control.

[0042] In some preferred embodiments, the above step "execute the corresponding startup strategy based on the recorded key information in the BDS stage of the firmware" specifically includes the following steps: if the recorded key information is a startup menu hotkey instruction, then call and display the startup device selection menu.

[0043] In practice, when the system retrieves the recorded boot menu hotkey command during the BDS stage, it directly calls and displays the boot device selection menu. This allows users to quickly boot from different devices (such as USB drives, CDs, and networks) without first entering a complex BIOS settings interface and then navigating through tedious steps. In scenarios requiring frequent switching of boot devices, such as operating system installation, system repair, or mass production in factories, this significantly shortens the operation path, improves work efficiency, and demonstrates the powerful practical value of this method.

[0044] This invention proposes a method for responding to key inputs early in the firmware lifecycle, comprising: initializing a USB controller and configuring an input device connected to the USB controller during the PEI phase of the firmware; recording key input information by the user through the input device starting from the PEI phase; and executing a corresponding startup strategy based on the recorded key input information during the BDS phase of the firmware. This invention advances the initialization of the USB controller and input device to the firmware PEI phase, enabling effective input from the moment the device is powered on, significantly extending the operation window. The continuous key input recording mechanism starting from the PEI phase ensures reliable capture of user input during firmware transitions. Finally, the recorded key commands are executed during the BDS phase, accurately implementing the user's intent into the startup strategy. This solution systematically solves the problem of a short operation window and poor user experience caused by firmware response lag, constructing a seamless interactive environment from startup to completion, significantly improving user control and interactive experience.

[0045] Corresponding to the above-described method for responding to key inputs early in firmware, the present invention also provides an apparatus for responding to key inputs early in firmware. This apparatus includes a unit for performing the aforementioned method for responding to key inputs early in firmware, and can be configured in a desktop computer, tablet computer, laptop computer, or other terminal. Specifically, the apparatus for responding to key inputs early in firmware includes: An initialization unit is used to initialize the USB controller and configure the input devices connected to the USB controller during the PEI phase of the firmware. A recording unit is used to record key information input by the user through the input device, starting from the PEI stage. The execution unit is used to execute the corresponding startup strategy based on the recorded key information during the BDS stage of the firmware.

[0046] In some preferred embodiments, the apparatus further includes: The receiving unit is used to take over the configuration of the USB controller and input device in the PEI stage during the DXE stage in order to maintain the continuity of key recording.

[0047] In some preferred embodiments, the apparatus further includes: The first output unit is used to output hotkey prompts on the display during the PEI stage to prompt the user for operation.

[0048] In some preferred embodiments, the apparatus further includes: The second output unit is used to output feedback information on the display to indicate that the key information has been received and responded to.

[0049] In some preferred embodiments, the key information includes hotkey instructions for triggering at least one function among firmware settings interface, boot menu, system recovery mode, or diagnostic mode.

[0050] In some preferred embodiments, the step of executing the corresponding startup strategy based on the recorded key information during the BDS stage of the firmware includes: if the recorded key information is a startup menu hotkey instruction, then calling and displaying the startup device selection menu.

[0051] In some preferred embodiments, the hotkey prompts and the feedback information are displayed in different positions on the screen.

[0052] It should be noted that those skilled in the art will clearly understand that the specific implementation process of the device and each unit that can respond to key input in the early stages of firmware can be found in the corresponding descriptions in the foregoing method embodiments. For the sake of convenience and brevity, these details will not be repeated here.

[0053] The aforementioned device that can respond to key inputs early in the firmware can be implemented as a computer program, which can, for example... Figure 2 It runs on the computer device shown.

[0054] Please see Figure 2 , Figure 2 This is a schematic block diagram of a computer device provided in an embodiment of this application. The computer device 500 can be a terminal or a server. The terminal can be an electronic device with communication functions, such as a smartphone, tablet, laptop, desktop computer, personal digital assistant, or wearable device. The server can be a standalone server or a server cluster composed of multiple servers.

[0055] The computer device 500 includes a processor 502, a memory, and a network interface 505 connected via a system bus 501. The memory may include a non-volatile storage medium 503 and internal memory 504.

[0056] The non-volatile storage medium 503 may store an operating system 5031 and a computer program 5032. When the computer program 5032 is executed, it causes the processor 502 to execute a method that can respond to key inputs in the early stages of firmware development.

[0057] The processor 502 provides computing and control capabilities to support the operation of the entire computer device 500.

[0058] The internal memory 504 provides an environment for the execution of the computer program 5032 in the non-volatile storage medium 503. When the computer program 5032 is executed by the processor 502, the processor 502 can execute a method that can respond to key inputs in the early stages of firmware.

[0059] The network interface 505 is used for network communication with other devices. Those skilled in the art will understand that the above structure is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device 500 to which the present application is applied. A specific computer device 500 may include more or fewer components than shown in the figures, or combine certain components, or have different component arrangements.

[0060] The processor 502 is used to run a computer program 5032 stored in the memory to perform the following steps: During the PEI phase of the firmware, the USB controller is initialized and the input devices connected to the USB controller are configured; Starting from the PEI stage, the key input information entered by the user through the input device is recorded; During the BDS phase of the firmware, the corresponding boot strategy is executed based on the recorded key information.

[0061] In some preferred embodiments, the method further includes: The DXE stage takes over the configuration of the USB controller and input device from the PEI stage to maintain the continuity of key recording.

[0062] In some preferred embodiments, the method further includes: during the PEI stage, outputting hotkey prompts on the display to prompt the user to perform operations.

[0063] In some preferred embodiments, after recording the key information input by the user through the input device, the method further includes: outputting feedback information on the display to indicate that the key information has been received and responded to.

[0064] In some preferred embodiments, the key information includes hotkey instructions for triggering at least one function among firmware settings interface, boot menu, system recovery mode, or diagnostic mode.

[0065] In some preferred embodiments, the step of executing the corresponding startup strategy based on the recorded key information during the BDS stage of the firmware includes: if the recorded key information is a startup menu hotkey instruction, then calling and displaying the startup device selection menu.

[0066] In some preferred embodiments, the hotkey prompts and the feedback information are displayed in different positions on the screen.

[0067] It should be understood that in the embodiments of this application, the processor 502 may be a central processing unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0068] It will be understood by those skilled in the art that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program may be stored in a storage medium, which is a computer-readable storage medium. The computer program is executed by at least one processor in the computer system to implement the process steps of the embodiments of the above methods.

[0069] Therefore, the present invention also provides a storage medium. This storage medium can be a computer-readable storage medium. The storage medium stores a computer program. When executed by a processor, the computer program causes the processor to perform the following steps: During the PEI phase of the firmware, the USB controller is initialized and the input devices connected to the USB controller are configured; Starting from the PEI stage, the key input information entered by the user through the input device is recorded; During the BDS phase of the firmware, the corresponding boot strategy is executed based on the recorded key information.

[0070] In some preferred embodiments, the method further includes: The DXE stage takes over the configuration of the USB controller and input device from the PEI stage to maintain the continuity of key recording.

[0071] In some preferred embodiments, the method further includes: during the PEI stage, outputting hotkey prompts on the display to prompt the user to perform operations.

[0072] In some preferred embodiments, after recording the key information input by the user through the input device, the method further includes: outputting feedback information on the display to indicate that the key information has been received and responded to.

[0073] In some preferred embodiments, the key information includes hotkey instructions for triggering at least one function among firmware settings interface, boot menu, system recovery mode, or diagnostic mode.

[0074] In some preferred embodiments, the step of executing the corresponding startup strategy based on the recorded key information during the BDS stage of the firmware includes: if the recorded key information is a startup menu hotkey instruction, then calling and displaying the startup device selection menu.

[0075] In some preferred embodiments, the hotkey prompts and the feedback information are displayed in different positions on the screen.

[0076] The storage medium is a physical, non-transient storage medium, such as a USB flash drive, external hard drive, read-only memory (ROM), magnetic disk, or optical disk, or any other physical storage medium capable of storing program code. The computer-readable storage medium can be non-volatile or volatile.

[0077] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0078] In the several embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of each unit is merely a logical functional division, and there may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0079] The steps in the method of this invention can be adjusted, merged, or reduced in order according to actual needs. The units in the device of this invention can be merged, divided, or reduced according to actual needs. Furthermore, the functional units in the various embodiments of this invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0080] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a terminal, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention.

[0081] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0082] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Since these modifications and variations fall within the scope of the claims and their equivalents, this invention also intends to include these modifications and variations.

[0083] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and these modifications or substitutions should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for responding to key inputs early in the firmware process, characterized in that, include: During the PEI phase of the firmware, the USB controller is initialized and the input devices connected to the USB controller are configured; Starting from the PEI stage, the key input information entered by the user through the input device is recorded; During the BDS phase of the firmware, the corresponding boot strategy is executed based on the recorded key information.

2. The method for responding to key inputs early in the firmware according to claim 1, characterized in that, The method further includes: The DXE stage takes over the configuration of the USB controller and input device from the PEI stage to maintain the continuity of key recording.

3. The method for responding to key inputs early in the firmware according to claim 1, characterized in that, The method further includes: during the PEI stage, outputting hotkey prompts on the display to prompt the user to perform operations.

4. The method for responding to key inputs early in the firmware according to claim 3, characterized in that, After recording the key information input by the user through the input device, the method further includes: outputting feedback information on the display to indicate that the key information has been received and responded to.

5. The method for responding to key inputs early in the firmware according to claim 1, characterized in that, The key information includes hotkey commands for triggering at least one of the following functions: firmware settings interface, boot menu, system recovery mode, or diagnostic mode.

6. The method for responding to key inputs early in the firmware according to claim 5, characterized in that, In the BDS stage of the firmware, the corresponding startup strategy is executed based on the recorded key information, including: if the recorded key information is a startup menu hotkey instruction, then the startup device selection menu is invoked and displayed.

7. The method for responding to key inputs early in the firmware according to claim 4, characterized in that, The hotkey prompts and feedback information are displayed in different positions on the screen.

8. A device capable of responding to key inputs early in the firmware process, characterized in that, Includes a unit for performing the method as described in any one of claims 1-7.

9. A computer device, characterized in that, The computer device includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The storage medium stores a computer program that, when executed by a processor, can implement the method as described in any one of claims 1-7.

Images