/** @file\r
UDP4 Service Binding Protocol as defined in UEFI specification.\r
\r
- The EFI UDPv4 Protocol provides simple packet-oriented services \r
- to transmit and receive UDP packets. \r
+ The EFI UDPv4 Protocol provides simple packet-oriented services\r
+ to transmit and receive UDP packets.\r
\r
-Copyright (c) 2006 - 2010, Intel Corporation. All rights reserved<BR>\r
-This program and the accompanying materials are licensed and made available under \r
-the terms and conditions of the BSD License that accompanies this distribution. \r
-The full text of the license may be found at\r
-http://opensource.org/licenses/bsd-license.php. \r
- \r
-THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS, \r
-WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED. \r
+Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>\r
+SPDX-License-Identifier: BSD-2-Clause-Patent\r
\r
- @par Revision Reference: \r
- This Protocol is introduced in UEFI Specification 2.0. \r
+ @par Revision Reference:\r
+ This Protocol is introduced in UEFI Specification 2.0.\r
\r
**/\r
\r
0x3ad9df29, 0x4501, 0x478d, {0xb1, 0xf8, 0x7f, 0x7f, 0xe7, 0x0e, 0x50, 0xf3 } \\r
}\r
\r
-typedef struct _EFI_UDP4_PROTOCOL EFI_UDP4_PROTOCOL; \r
- \r
+typedef struct _EFI_UDP4_PROTOCOL EFI_UDP4_PROTOCOL;\r
+\r
+///\r
+/// EFI_UDP4_SERVICE_POINT is deprecated in the UEFI 2.4B and should not be used any more.\r
+/// The definition in here is only present to provide backwards compatability.\r
+///\r
typedef struct {\r
EFI_HANDLE InstanceHandle;\r
EFI_IPv4_ADDRESS LocalAddress;\r
UINT16 LocalPort;\r
EFI_IPv4_ADDRESS RemoteAddress;\r
UINT16 RemotePort;\r
-} EFI_UDP4_SERVICE_POINT; \r
+} EFI_UDP4_SERVICE_POINT;\r
\r
+///\r
+/// EFI_UDP4_VARIABLE_DATA is deprecated in the UEFI 2.4B and should not be used any more.\r
+/// The definition in here is only present to provide backwards compatability.\r
+///\r
typedef struct {\r
EFI_HANDLE DriverHandle;\r
UINT32 ServiceCount;\r
EFI_UDP4_SESSION_DATA *UdpSessionData; //OPTIONAL\r
EFI_IPv4_ADDRESS *GatewayAddress; //OPTIONAL\r
UINT32 DataLength;\r
- UINT32 FragmentCount; \r
+ UINT32 FragmentCount;\r
EFI_UDP4_FRAGMENT_DATA FragmentTable[1];\r
} EFI_UDP4_TRANSMIT_DATA;\r
\r
OUT EFI_IP4_MODE_DATA *Ip4ModeData OPTIONAL,\r
OUT EFI_MANAGED_NETWORK_CONFIG_DATA *MnpConfigData OPTIONAL,\r
OUT EFI_SIMPLE_NETWORK_MODE *SnpModeData OPTIONAL\r
- ); \r
- \r
+ );\r
+\r
\r
/**\r
Initializes, changes, or resets the operational parameters for this instance of the EFI UDPv4\r
Protocol.\r
- \r
+\r
The Configure() function is used to do the following:\r
* Initialize and start this instance of the EFI UDPv4 Protocol.\r
* Change the filtering rules and operational parameters.\r
@retval EFI_OUT_OF_RESOURCES The EFI UDPv4 Protocol driver cannot allocate memory for this\r
EFI UDPv4 Protocol instance.\r
@retval EFI_DEVICE_ERROR An unexpected network or system error occurred and this instance\r
- was not opened. \r
+ was not opened.\r
\r
**/\r
typedef\r
(EFIAPI *EFI_UDP4_CONFIGURE)(\r
IN EFI_UDP4_PROTOCOL *This,\r
IN EFI_UDP4_CONFIG_DATA *UdpConfigData OPTIONAL\r
- ); \r
+ );\r
\r
/**\r
Joins and leaves multicast groups.\r
- \r
+\r
The Groups() function is used to enable and disable the multicast group\r
filtering. If the JoinFlag is FALSE and the MulticastAddress is NULL, then all\r
currently joined groups are left.\r
IN EFI_UDP4_PROTOCOL *This,\r
IN BOOLEAN JoinFlag,\r
IN EFI_IPv4_ADDRESS *MulticastAddress OPTIONAL\r
- ); \r
+ );\r
\r
/**\r
Adds and deletes routing table entries.\r
- \r
+\r
The Routes() function adds a route to or deletes a route from the routing table.\r
Routes are determined by comparing the SubnetAddress with the destination IP\r
address and arithmetically AND-ing it with the SubnetMask. The gateway address\r
IN EFI_IPv4_ADDRESS *SubnetAddress,\r
IN EFI_IPv4_ADDRESS *SubnetMask,\r
IN EFI_IPv4_ADDRESS *GatewayAddress\r
- ); \r
+ );\r
\r
/**\r
Polls for incoming data packets and processes outgoing data packets.\r
- \r
+\r
The Poll() function can be used by network drivers and applications to increase\r
the rate that data packets are moved between the communications device and the\r
transmit and receive queues.\r
EFI_STATUS\r
(EFIAPI *EFI_UDP4_POLL)(\r
IN EFI_UDP4_PROTOCOL *This\r
- ); \r
+ );\r
\r
/**\r
Places an asynchronous receive request into the receiving queue.\r
- \r
+\r
The Receive() function places a completion token into the receive packet queue.\r
This function is always asynchronous.\r
The caller must fill in the Token.Event field in the completion token, and this\r
(EFIAPI *EFI_UDP4_RECEIVE)(\r
IN EFI_UDP4_PROTOCOL *This,\r
IN EFI_UDP4_COMPLETION_TOKEN *Token\r
- ); \r
+ );\r
\r
/**\r
Queues outgoing data packets into the transmit queue.\r
- \r
+\r
The Transmit() function places a sending request to this instance of the EFI\r
UDPv4 Protocol, alongside the transmit data that was filled by the user. Whenever\r
the packet in the token is sent out or some errors occur, the Token.Event will\r
(EFIAPI *EFI_UDP4_TRANSMIT)(\r
IN EFI_UDP4_PROTOCOL *This,\r
IN EFI_UDP4_COMPLETION_TOKEN *Token\r
- ); \r
+ );\r
\r
/**\r
Aborts an asynchronous transmit or receive request.\r
- \r
+\r
The Cancel() function is used to abort a pending transmit or receive request.\r
If the token is in the transmit or receive request queues, after calling this\r
function, Token.Status will be set to EFI_ABORTED and then Token.Event will be\r
(EFIAPI *EFI_UDP4_CANCEL)(\r
IN EFI_UDP4_PROTOCOL *This,\r
IN EFI_UDP4_COMPLETION_TOKEN *Token OPTIONAL\r
- ); \r
+ );\r
\r
///\r
-/// The EFI_UDP4_PROTOCOL defines an EFI UDPv4 Protocol session that can be used \r
-/// by any network drivers, applications, or daemons to transmit or receive UDP packets. \r
-/// This protocol instance can either be bound to a specified port as a service or \r
-/// connected to some remote peer as an active client. Each instance has its own settings, \r
+/// The EFI_UDP4_PROTOCOL defines an EFI UDPv4 Protocol session that can be used\r
+/// by any network drivers, applications, or daemons to transmit or receive UDP packets.\r
+/// This protocol instance can either be bound to a specified port as a service or\r
+/// connected to some remote peer as an active client. Each instance has its own settings,\r
/// such as the routing table and group table, which are independent from each other.\r
///\r
struct _EFI_UDP4_PROTOCOL {\r
projects / mirror_edk2.git / blobdiff