mirror of
https://github.com/tianocore/edk2
synced 2026-08-27 00:23:19 -04:00
Replace traditional `#ifndef`/`#define`/`#endif` include guards with
`#pragma` once.
`#pragma once` is a widely supported preprocessor directive that
prevents header files from being included multiple times. It is
supported by all toolchains used to build edk2: GCC, Clang/LLVM, and
MSVC.
Compared to macro-based include guards, `#pragma once`:
- Eliminates the risk of macro name collisions or copy/paste errors
where two headers inadvertently use the same guard macro.
- Eliminate inconsistency in the way include guard macros are named
(e.g., some files use `__FILE_H__`, others use `FILE_H_`, etc.).
- Reduces boilerplate (three lines replaced by one).
- Avoids polluting the macro namespace with guard symbols.
- Can improve build times as the preprocessor can skip re-opening the
file entirely, rather than re-reading it to find the matching
`#endif` ("multiple-include optimization").
- Note that some compilers may already optimize traditional include
guards, by recognzining the idiomatic pattern.
This change is made acknowledging that overall portability of the
code will technically be reduced, as `#pragma once` is not part of the
C/C++ standards.
However, this is considered acceptable given:
1. edk2 already defines a subset of supported compilers in
BaseTools/Conf/tools_def.template, all of which have supported
`#pragma once` for over two decades.
2. There have been concerns raised to the project about inconsistent
include guard naming and potential macro collisions.
Approximate compiler support dates:
- MSVC: Supported since Visual C++ 4.2 (1996)
- GCC: Supported since 3.4 (2004)
(http://gnu.ist.utl.pt/software/gcc/gcc-3.4/changes.html)
- Clang (LLVM based): Since initial release in 2007
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
44 lines
1.3 KiB
C
44 lines
1.3 KiB
C
/** @file
|
|
Deal with devices that just exist in memory space.
|
|
|
|
To follow the EFI driver model you need a root handle to start with. An
|
|
EFI driver will have a driver binding protocol (Supported, Start, Stop)
|
|
that is used to layer on top of a handle via a gBS->ConnectController.
|
|
The first handle has to just be in the system to make that work. For
|
|
PCI it is a PCI Root Bridge IO protocol that provides the root.
|
|
|
|
On an embedded system with MMIO device we need a handle to just
|
|
show up. That handle will have this protocol and a device path
|
|
protocol on it.
|
|
|
|
For an ethernet device the device path must contain a MAC address device path
|
|
node.
|
|
|
|
Copyright (c) 2008 - 2009, Apple Inc. All rights reserved.<BR>
|
|
|
|
SPDX-License-Identifier: BSD-2-Clause-Patent
|
|
|
|
**/
|
|
|
|
#pragma once
|
|
|
|
//
|
|
// Protocol GUID
|
|
//
|
|
// BF4B9D10-13EC-43dd-8880-E90B718F27DE
|
|
|
|
#define EMBEDDED_DEVICE_PROTOCOL_GUID \
|
|
{ 0xbf4b9d10, 0x13ec, 0x43dd, { 0x88, 0x80, 0xe9, 0xb, 0x71, 0x8f, 0x27, 0xde } }
|
|
|
|
typedef struct {
|
|
UINT16 VendorId;
|
|
UINT16 DeviceId;
|
|
UINT16 RevisionId;
|
|
UINT16 SubsystemId;
|
|
UINT16 SubsystemVendorId;
|
|
UINT8 ClassCode[3];
|
|
UINT8 HeaderSize;
|
|
UINTN BaseAddress;
|
|
} EMBEDDED_DEVICE_PROTOCOL;
|
|
|
|
extern EFI_GUID gEmbeddedDeviceGuid;
|