Fork of ipxe; additional commands and features https://git.openslx.org/openslx-ng/ipxe.git/atom/src/drivers/net/phantom/phantom.h?h=v1.0.0 2009-05-18T07:33:25+00:00 2009-05-18T07:33:25+00:00 Michael Brown 2009-05-01T14:41:06+00:00 urn:sha1:c44a193d0d147ed6f98741124569864e516e9d4b Add FILE_LICENCE declarations to almost all files that make up the various standard builds of gPXE. 2008-11-01T01:55:13+00:00 Michael Brown 2008-11-01T01:55:13+00:00 urn:sha1:aa95744915aba1b96fd226609e07ad1843437afc This is something of an ugly hack to accommodate an OEM requirement. The NIC has only one expansion ROM BAR, rather than one per port. To allow individual ports to be selectively enabled/disabled for PXE boot (as required), we must therefore leave the expansion ROM always enabled, and place the per-port enable/disable logic within the gPXE driver. 2008-10-31T01:55:58+00:00 Michael Brown 2008-10-31T01:52:55+00:00 urn:sha1:32bc76f902d2f38974311acc12457f25819bf539 The Phantom firmware selectively disables PCI functions based on the board type, with the end result that we see one PCI function for each network port. This allows us to eliminate the code for reading from flash and, more importantly, removes knowledge of the board type magic number from the gPXE driver. 2008-10-28T18:49:58+00:00 Michael Brown 2008-10-28T18:49:58+00:00 urn:sha1:1bc2adea9a56c028babe23fbc5b27a582e90ec4f This interface provides access to firmware settings (e.g. MAC address) that will apply to all drivers loaded for the duration of the current system boot. 2008-10-28T18:47:44+00:00 Michael Brown 2008-10-24T02:49:11+00:00 urn:sha1:664f4cf36577c795c43bd998919b73bdf6a8c2f0 A hardware bug means that reads through the expansion ROM BAR can return corrupted data if the PEGs are running. This breaks platforms that re-read the expansion ROM after invoking gPXE code, such as IBM blade servers. Halt PEGs during driver shutdown, and unhalt PEGs during driver startup if we detect that this is not the first startup since power-on. 2008-10-24T02:52:17+00:00 Michael Brown 2008-10-23T22:35:01+00:00 urn:sha1:d4c8273569b4452fe3a6f2f90557655bceeb1aa3 Most other Phantom drivers define a register space in terms of a 64M virtual address space. While this doesn't map in any meaningful way to the actual addresses used on the latest cards, it makes maintenance easier if we do the same. 2008-08-25T22:25:33+00:00 Michael Brown 2008-08-25T22:25:33+00:00 urn:sha1:f58cc3fca8967b68d108e787239557a81ca852a2 2008-07-24T18:40:10+00:00 Michael Brown 2008-07-24T18:40:10+00:00 urn:sha1:f493283c74e4ded0c4234ddfde097fbfea0b7266 2008-07-08T21:36:07+00:00 Michael Brown 2008-07-08T21:36:07+00:00 urn:sha1:22d00797f15c0d4d43918c0692f6f31b7163be16 2008-07-05T02:38:14+00:00 Michael Brown 2008-07-05T02:38:14+00:00 urn:sha1:3ad348e55a51da012ad4a0ad029da5e80541e4ec