©Copyright 2003-2004 Marvell®.
All rights reserved.
yukonundi.htm created 09-Jun-2004
Readme File for yukonundi.efi v2.02
UNDI driver for EFI32
This file contains
yukonundi.efi is the EFI UNDI driver for the Marvell(R) Yukon(TM)
Ethernet Controller.
The following table gives an overview of the possible configuration that
YUKONUNDI offers:
Parameter | Possible Values
+-----------------------+-------------------------------------+
Speed Capabilities | Auto (default)
| 10 Mbps
| 100 Mbps
+-----------------------+-------------------------------------+
Duplex Capabilities | Both (default)
| Half duplex
| Full duplex
+-----------------------+-------------------------------------+
The configuration is stored in the VPD memory of the adapter, if there is
enough space left. If the VPD memory is destroyed or YUKONUNDI can not
read the configuration, it uses the default values (see table above).
1) Speed capabilities
The speed capabilities '10 Mbps' or '100 Mbps' force the link speed to the
respective value. If 'Auto' is selected, the link speed will be
negotiated, which can result in a speed of 10, 100 or, if supported by the
actual hardware, 1000 Mbps.
2) Duplex capabilities
The duplex capabilities 'Half duplex' and 'Full duplex' force the duplex
mode to the respective value. If 'Both' is selected, the duplex mode is
negotiated, which can result in a duplex mode of Full duplex or Half
duplex.
Format and coding of the configuration
--------------------------------------
YUKONUNDI uses four bytes of the VPD memory to store the configuration:
- two bytes for the VPD keyword "VE",
- one byte for the length (4) of this VPD entry,
- one bytes for the configuration itself.
Coding of the configuration in the VPD memory:
+---+---+---+---+---+---+---+---+
Bit: | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
+---+---+---+---+---+---+---+---+
| | | |
| | +---+---- Speed capabilities
+---+------------ Duplex capabilities
The default values are all zeros, resulting in the following
configuration:
Link speed capability: Auto.
Duplex capability: Both.
1) Loading YUKONUNDI manually
Manual installation of the driver can be done by invoking the EFI shell
command 'load' with the name of the driver image as argument.
The EFI shell command 'unload' can be used to unload the driver from
memory.
2) Loading YUKONUNDI automatically
To load YUKONUNDI automatically, the driver image must reside on a
drive that is accessible from the EFI shell. To load YUKONUNDI
automatically during every boot, call the shell command 'bcfg':
bcfg driver add # [path]yukonundi.efi "desc"
# Position in the additional driver list.
Type 'bcfg driver dump' to see the current list.
[path] Path to the driver image of YUKONUNDI.
Example fs0:\efi\drivers 197
desc Any description you like, preferably "UNDI" to give a hint of
the driver's nature.
Again, the EFI shell command 'unload' can be used to unload the driver
from memory.
***End of Readme file***