/** @file\r
Deal with devices that just exist in memory space.\r
- \r
+\r
To follow the EFI driver model you need a root handle to start with. An\r
- EFI driver will have a driver binding protocol (Supported, Start, Stop) \r
- that is used to layer on top of a handle via a gBS->ConnectController. \r
+ EFI driver will have a driver binding protocol (Supported, Start, Stop)\r
+ that is used to layer on top of a handle via a gBS->ConnectController.\r
The first handle has to just be in the system to make that work. For\r
- PCI it is a PCI Root Bridge IO protocol that provides the root. \r
- \r
- On an embedded system with MMIO device we need a handle to just \r
- show up. That handle will have this protocol and a device path \r
- protocol on it. \r
- \r
+ PCI it is a PCI Root Bridge IO protocol that provides the root.\r
+\r
+ On an embedded system with MMIO device we need a handle to just\r
+ show up. That handle will have this protocol and a device path\r
+ protocol on it.\r
+\r
For an ethernet device the device path must contain a MAC address device path\r
node.\r
\r