|
| typedef struct _EFI_UDP4_PROTOCOL | EFI_UDP4_PROTOCOL |
| |
| typedef EFI_STATUS(EFIAPI * | EFI_UDP4_GET_MODE_DATA) (IN EFI_UDP4_PROTOCOL *This, OUT EFI_UDP4_CONFIG_DATA *Udp4ConfigData OPTIONAL, OUT EFI_IP4_MODE_DATA *Ip4ModeData OPTIONAL, OUT EFI_MANAGED_NETWORK_CONFIG_DATA *MnpConfigData OPTIONAL, OUT EFI_SIMPLE_NETWORK_MODE *SnpModeData OPTIONAL) |
| |
| typedef EFI_STATUS(EFIAPI * | EFI_UDP4_CONFIGURE) (IN EFI_UDP4_PROTOCOL *This, IN EFI_UDP4_CONFIG_DATA *UdpConfigData OPTIONAL) |
| |
| typedef EFI_STATUS(EFIAPI * | EFI_UDP4_GROUPS) (IN EFI_UDP4_PROTOCOL *This, IN BOOLEAN JoinFlag, IN EFI_IPv4_ADDRESS *MulticastAddress OPTIONAL) |
| |
| typedef EFI_STATUS(EFIAPI * | EFI_UDP4_ROUTES) (IN EFI_UDP4_PROTOCOL *This, IN BOOLEAN DeleteRoute, IN EFI_IPv4_ADDRESS *SubnetAddress, IN EFI_IPv4_ADDRESS *SubnetMask, IN EFI_IPv4_ADDRESS *GatewayAddress) |
| |
| typedef EFI_STATUS(EFIAPI * | EFI_UDP4_POLL) (IN EFI_UDP4_PROTOCOL *This) |
| |
| typedef EFI_STATUS(EFIAPI * | EFI_UDP4_RECEIVE) (IN EFI_UDP4_PROTOCOL *This, IN EFI_UDP4_COMPLETION_TOKEN *Token) |
| |
| typedef EFI_STATUS(EFIAPI * | EFI_UDP4_TRANSMIT) (IN EFI_UDP4_PROTOCOL *This, IN EFI_UDP4_COMPLETION_TOKEN *Token) |
| |
| typedef EFI_STATUS(EFIAPI * | EFI_UDP4_CANCEL) (IN EFI_UDP4_PROTOCOL *This, IN EFI_UDP4_COMPLETION_TOKEN *Token OPTIONAL) |
| |
UDP4 Service Binding Protocol as defined in UEFI specification.
The EFI UDPv4 Protocol provides simple packet-oriented services to transmit and receive UDP packets.
Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.
SPDX-License-Identifier: BSD-2-Clause-Patent
- Revision Reference:
- This Protocol is introduced in UEFI Specification 2.0.
Definition in file Udp4.h.
Aborts an asynchronous transmit or receive request.
The Cancel() function is used to abort a pending transmit or receive request. If the token is in the transmit or receive request queues, after calling this function, Token.Status will be set to EFI_ABORTED and then Token.Event will be signaled. If the token is not in one of the queues, which usually means that the asynchronous operation has completed, this function will not signal the token and EFI_NOT_FOUND is returned.
- Parameters
-
| This | The pointer to the EFI_UDP4_PROTOCOL instance. |
| Token | The pointer to a token that has been issued by EFI_UDP4_PROTOCOL.Transmit() or EFI_UDP4_PROTOCOL.Receive().If NULL, all pending tokens are aborted. |
- Return values
-
| EFI_SUCCESS | The asynchronous I/O request was aborted and Token.Event was signaled. When Token is NULL, all pending requests are aborted and their events are signaled. |
| EFI_INVALID_PARAMETER | This is NULL. |
| EFI_NOT_STARTED | This instance has not been started. |
| EFI_NO_MAPPING | When using the default address, configuration (DHCP, BOOTP, RARP, etc.) is not finished yet. |
| EFI_NOT_FOUND | When Token is not NULL, the asynchronous I/O request was not found in the transmit or receive queue. It has either completed or was not issued by Transmit() and Receive(). |
Definition at line 410 of file Udp4.h.
Initializes, changes, or resets the operational parameters for this instance of the EFI UDPv4 Protocol.
The Configure() function is used to do the following: Initialize and start this instance of the EFI UDPv4 Protocol. Change the filtering rules and operational parameters. Reset this instance of the EFI UDPv4 Protocol. Until these parameters are initialized, no network traffic can be sent or received by this instance. This instance can be also reset by calling Configure() with UdpConfigData set to NULL. Once reset, the receiving queue and transmitting queue are flushed and no traffic is allowed through this instance. With different parameters in UdpConfigData, Configure() can be used to bind this instance to specified port.
- Parameters
-
| This | The pointer to the EFI_UDP4_PROTOCOL instance. |
| Udp4ConfigData | The pointer to the buffer to receive the current configuration data. |
- Return values
-
| EFI_SUCCESS | The configuration settings were set, changed, or reset successfully. |
| EFI_NO_MAPPING | When using a default address, configuration (DHCP, BOOTP, RARP, etc.) is not finished yet. |
| EFI_INVALID_PARAMETER | This is NULL. |
| EFI_INVALID_PARAMETER | UdpConfigData.StationAddress is not a valid unicast IPv4 address. |
| EFI_INVALID_PARAMETER | UdpConfigData.SubnetMask is not a valid IPv4 address mask. The subnet mask must be contiguous. |
| EFI_INVALID_PARAMETER | UdpConfigData.RemoteAddress is not a valid unicast IPv4 address if it is not zero. |
| EFI_ALREADY_STARTED | The EFI UDPv4 Protocol instance is already started/configured and must be stopped/reset before it can be reconfigured. |
| EFI_ACCESS_DENIED | UdpConfigData. AllowDuplicatePort is FALSE and UdpConfigData.StationPort is already used by other instance. |
| EFI_OUT_OF_RESOURCES | The EFI UDPv4 Protocol driver cannot allocate memory for this EFI UDPv4 Protocol instance. |
| EFI_DEVICE_ERROR | An unexpected network or system error occurred and this instance was not opened. |
Definition at line 189 of file Udp4.h.
Polls for incoming data packets and processes outgoing data packets.
The Poll() function can be used by network drivers and applications to increase the rate that data packets are moved between the communications device and the transmit and receive queues. In some systems, the periodic timer event in the managed network driver may not poll the underlying communications device fast enough to transmit and/or receive all data packets without missing incoming packets or dropping outgoing packets. Drivers and applications that are experiencing packet loss should try calling the Poll() function more often.
- Parameters
-
| This | The pointer to the EFI_UDP4_PROTOCOL instance. |
- Return values
-
| EFI_SUCCESS | Incoming or outgoing data was processed. |
| EFI_INVALID_PARAMETER | This is NULL. |
| EFI_DEVICE_ERROR | An unexpected system or network error occurred. |
| EFI_TIMEOUT | Data was dropped out of the transmit and/or receive queue. |
Definition at line 301 of file Udp4.h.
Places an asynchronous receive request into the receiving queue.
The Receive() function places a completion token into the receive packet queue. This function is always asynchronous. The caller must fill in the Token.Event field in the completion token, and this field cannot be NULL. When the receive operation completes, the EFI UDPv4 Protocol driver updates the Token.Status and Token.Packet.RxData fields and the Token.Event is signaled. Providing a proper notification function and context for the event will enable the user to receive the notification and receiving status. That notification function is guaranteed to not be re-entered.
- Parameters
-
| This | The pointer to the EFI_UDP4_PROTOCOL instance. |
| Token | The pointer to a token that is associated with the receive data descriptor. |
- Return values
-
| EFI_SUCCESS | The receive completion token was cached. |
| EFI_NOT_STARTED | This EFI UDPv4 Protocol instance has not been started. |
| EFI_NO_MAPPING | When using a default address, configuration (DHCP, BOOTP, RARP, etc.) is not finished yet. |
| EFI_INVALID_PARAMETER | This is NULL. |
| EFI_INVALID_PARAMETER | Token is NULL. |
| EFI_INVALID_PARAMETER | Token.Event is NULL. |
| EFI_OUT_OF_RESOURCES | The receive completion token could not be queued due to a lack of system resources (usually memory). |
| EFI_DEVICE_ERROR | An unexpected system or network error occurred. |
| EFI_ACCESS_DENIED | A receive completion token with the same Token.Event was already in the receive queue. |
| EFI_NOT_READY | The receive request could not be queued because the receive queue is full. |
Definition at line 338 of file Udp4.h.
Queues outgoing data packets into the transmit queue.
The Transmit() function places a sending request to this instance of the EFI UDPv4 Protocol, alongside the transmit data that was filled by the user. Whenever the packet in the token is sent out or some errors occur, the Token.Event will be signaled and Token.Status is updated. Providing a proper notification function and context for the event will enable the user to receive the notification and transmitting status.
- Parameters
-
| This | The pointer to the EFI_UDP4_PROTOCOL instance. |
| Token | The pointer to the completion token that will be placed into the transmit queue. |
- Return values
-
| EFI_SUCCESS | The data has been queued for transmission. |
| EFI_NOT_STARTED | This EFI UDPv4 Protocol instance has not been started. |
| EFI_NO_MAPPING | When using a default address, configuration (DHCP, BOOTP, RARP, etc.) is not finished yet. |
| EFI_INVALID_PARAMETER | One or more parameters are invalid. |
| EFI_ACCESS_DENIED | The transmit completion token with the same Token.Event was already in the transmit queue. |
| EFI_NOT_READY | The completion token could not be queued because the transmit queue is full. |
| EFI_OUT_OF_RESOURCES | Could not queue the transmit data. |
| EFI_NOT_FOUND | There is no route to the destination network or address. |
| EFI_BAD_BUFFER_SIZE | The data length is greater than the maximum UDP packet size. Or the length of the IP header + UDP header + data length is greater than MTU if DoNotFragment is TRUE. |
Definition at line 375 of file Udp4.h.
1.9.6