vbox的更動 58466 路徑 trunk/src/VBox/Devices/EFI/Firmware/MdePkg/Include/Protocol/Udp4.h

時間撮記:

2015-10-29 上午04:30:44 (9 年 以前)

作者:

vboxsync

svn:sync-xref-src-repo-rev:

103777

訊息:

EFI/Firmware: Merged in the svn:eol-style, svn:mime-type and trailing whitespace cleanup that was done after the initial UDK2014.SP1 import: svn merge ^{/vendor/edk2/UDK2014.SP1} /vendor/edk2/current .

位置:

trunk/src/VBox/Devices/EFI/Firmware

檔案:

• . (修改) (1 屬性更動)
• MdePkg/Include/Protocol/Udp4.h (修改) (13 筆差異)

trunk/src/VBox/Devices/EFI/Firmware/MdePkg/Include/Protocol/Udp4.h ¶

@@ -2 +2 @@
   UDP4 Service Binding Protocol as defined in UEFI specification.
 
-  The EFI UDPv4 Protocol provides simple packet-oriented services 
-  to transmit and receive UDP packets.  
+  The EFI UDPv4 Protocol provides simple packet-oriented services
+  to transmit and receive UDP packets.
 
 Copyright (c) 2006 - 2014, Intel Corporation. All rights reserved.<BR>
-This program and the accompanying materials are licensed and made available under 
-the terms and conditions of the BSD License that accompanies this distribution.  
+This program and the accompanying materials are licensed and made available under
+the terms and conditions of the BSD License that accompanies this distribution.
 The full text of the license may be found at
-http://opensource.org/licenses/bsd-license.php.                                          
-    
-THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,                     
-WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.      
-
-  @par Revision Reference:          
-  This Protocol is introduced in UEFI Specification 2.0.       
+http://opensource.org/licenses/bsd-license.php.
+
+THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,
+WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.
+
+  @par Revision Reference:
+  This Protocol is introduced in UEFI Specification 2.0.
 
 **/
@@ -36 +36 @@
   }
 
-typedef struct _EFI_UDP4_PROTOCOL EFI_UDP4_PROTOCOL; 
-  
+typedef struct _EFI_UDP4_PROTOCOL EFI_UDP4_PROTOCOL;
+
 ///
 /// EFI_UDP4_SERVICE_POINT is deprecated in the UEFI 2.4B and should not be used any more.
@@ -48 +48 @@
   EFI_IPv4_ADDRESS        RemoteAddress;
   UINT16                  RemotePort;
-} EFI_UDP4_SERVICE_POINT; 
+} EFI_UDP4_SERVICE_POINT;
 
 ///
@@ -102 +102 @@
   EFI_IPv4_ADDRESS          *GatewayAddress;       //OPTIONAL
   UINT32                    DataLength;
-  UINT32                    FragmentCount; 
+  UINT32                    FragmentCount;
   EFI_UDP4_FRAGMENT_DATA    FragmentTable[1];
 } EFI_UDP4_TRANSMIT_DATA;
@@ -153 +153 @@
   OUT EFI_MANAGED_NETWORK_CONFIG_DATA  *MnpConfigData  OPTIONAL,
   OUT EFI_SIMPLE_NETWORK_MODE          *SnpModeData    OPTIONAL
-  );  
-  
+  );
+
 
 /**
   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.
@@ -191 +191 @@
                                 EFI UDPv4 Protocol instance.
   @retval EFI_DEVICE_ERROR      An unexpected network or system error occurred and this instance
-                                 was not opened. 
+                                 was not opened.
 
 **/
@@ -199 +199 @@
   IN EFI_UDP4_PROTOCOL      *This,
   IN EFI_UDP4_CONFIG_DATA   *UdpConfigData OPTIONAL
-  );  
+  );
 
 /**
   Joins and leaves multicast groups.
-  
+
   The Groups() function is used to enable and disable the multicast group
   filtering. If the JoinFlag is FALSE and the MulticastAddress is NULL, then all
@@ -236 +236 @@
   IN BOOLEAN                JoinFlag,
   IN EFI_IPv4_ADDRESS       *MulticastAddress    OPTIONAL
-  );   
+  );
 
 /**
   Adds and deletes routing table entries.
-  
+
   The Routes() function adds a route to or deletes a route from the routing table.
   Routes are determined by comparing the SubnetAddress with the destination IP
@@ -284 +284 @@
   IN EFI_IPv4_ADDRESS       *SubnetMask,
   IN EFI_IPv4_ADDRESS       *GatewayAddress
-  );     
+  );
 
 /**
   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
@@ -310 +310 @@
 (EFIAPI *EFI_UDP4_POLL)(
   IN EFI_UDP4_PROTOCOL      *This
-  );   
+  );
 
 /**
   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.
@@ -348 +348 @@
   IN EFI_UDP4_PROTOCOL          *This,
   IN EFI_UDP4_COMPLETION_TOKEN  *Token
-  );   
+  );
 
 /**
   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
@@ -385 +385 @@
   IN EFI_UDP4_PROTOCOL           *This,
   IN EFI_UDP4_COMPLETION_TOKEN   *Token
-  );     
+  );
 
 /**
   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
@@ -420 +420 @@
   IN EFI_UDP4_PROTOCOL          *This,
   IN EFI_UDP4_COMPLETION_TOKEN  *Token  OPTIONAL
-  );       
-
-///
-/// The EFI_UDP4_PROTOCOL defines an EFI UDPv4 Protocol session that can be used 
-/// by any network drivers, applications, or daemons to transmit or receive UDP packets. 
-/// This protocol instance can either be bound to a specified port as a service or 
-/// connected to some remote peer as an active client. Each instance has its own settings, 
+  );
+
+///
+/// The EFI_UDP4_PROTOCOL defines an EFI UDPv4 Protocol session that can be used
+/// by any network drivers, applications, or daemons to transmit or receive UDP packets.
+/// This protocol instance can either be bound to a specified port as a service or
+/// connected to some remote peer as an active client. Each instance has its own settings,
 /// such as the routing table and group table, which are independent from each other.
 ///