<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openslx-ng/ipxe.git/src/drivers/net/phantom/phantom.c, branch v1.0.0</title>
<subtitle>Fork of ipxe; additional commands and features</subtitle>
<id>https://git.openslx.org/openslx-ng/ipxe.git/atom/src/drivers/net/phantom/phantom.c?h=v1.0.0</id>
<link rel='self' href='https://git.openslx.org/openslx-ng/ipxe.git/atom/src/drivers/net/phantom/phantom.c?h=v1.0.0'/>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/'/>
<updated>2009-08-11T23:19:14+00:00</updated>
<entry>
<title>[netdevice] Separate out the concept of hardware and link-layer addresses</title>
<updated>2009-08-11T23:19:14+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2009-08-11T19:19:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=37a0aab4ff2c86f4d109d4cd479535be97d07a94'/>
<id>urn:sha1:37a0aab4ff2c86f4d109d4cd479535be97d07a94</id>
<content type='text'>
The hardware address is an intrinsic property of the hardware, while
the link-layer address can be changed at runtime.  This separation is
exposed via APIs such as PXE and EFI, but is currently elided by gPXE.

Expose the hardware and link-layer addresses as separate properties
within a net device.  Drivers should now fill in hw_addr, which will
be used to initialise ll_addr at the time of calling
register_netdev().
</content>
</entry>
<entry>
<title>[netdevice] Make ll_broadcast per-netdevice rather than per-ll_protocol</title>
<updated>2009-07-17T22:02:48+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2009-07-17T21:48:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=d09290161e33574d8f0fa900ebe739214d17fe1a'/>
<id>urn:sha1:d09290161e33574d8f0fa900ebe739214d17fe1a</id>
<content type='text'>
IPoIB has a link-layer broadcast address that varies according to the
partition key.  We currently go through several contortions to pretend
that the link-layer address is a fixed constant; by making the
broadcast address a property of the network device rather than the
link-layer protocol it will be possible to simplify IPoIB's broadcast
handling.
</content>
</entry>
<entry>
<title>[legal] Add a selection of FILE_LICENCE declarations</title>
<updated>2009-05-18T07:33:25+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2009-05-01T14:41:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=c44a193d0d147ed6f98741124569864e516e9d4b'/>
<id>urn:sha1:c44a193d0d147ed6f98741124569864e516e9d4b</id>
<content type='text'>
Add FILE_LICENCE declarations to almost all files that make up the
various standard builds of gPXE.
</content>
</entry>
<entry>
<title>[pci] Add driver_data field to struct pci_device_id</title>
<updated>2009-03-26T10:22:15+00:00</updated>
<author>
<name>Thomas Miletich</name>
</author>
<published>2009-03-26T10:19:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=3da6f1c7bdc227ed0b5ab45562278fa4a18c15d3'/>
<id>urn:sha1:3da6f1c7bdc227ed0b5ab45562278fa4a18c15d3</id>
<content type='text'>
Modified-by: Michael Brown &lt;mcb30@etherboot.org&gt;
Signed-off-by: Michael Brown &lt;mcb30@etherboot.org&gt;
</content>
</entry>
<entry>
<title>[i386] Change [u]int32_t to [unsigned] int, rather than [unsigned] long</title>
<updated>2008-11-19T19:15:44+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-11-19T02:22:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=b59e0cc56eb6d5f3b6f934722931f6919309ffd2'/>
<id>urn:sha1:b59e0cc56eb6d5f3b6f934722931f6919309ffd2</id>
<content type='text'>
This brings us in to line with Linux definitions, and also simplifies
adding x86_64 support since both platforms have 2-byte shorts, 4-byte
ints and 8-byte long longs.
</content>
</entry>
<entry>
<title>[phantom] Do not halt PEGs on driver shutdown</title>
<updated>2008-11-08T05:10:23+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-11-08T05:10:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=46f43d8ea763ca2a9d4d1b87db589bb7dcc978bf'/>
<id>urn:sha1:46f43d8ea763ca2a9d4d1b87db589bb7dcc978bf</id>
<content type='text'>
Halting the PEGs breaks platforms where there is sideband access to
the NIC (e.g. HP machines using iLO).  (We have to retain the
unhalting code because on some other platforms (e.g. IBM blades with
BOFM) the pre-PXE firmware must halt the PEGs to avoid issues with the
BIOS rereading via the expansion ROM BAR.)
</content>
</entry>
<entry>
<title>[phantom] Allow for PXE boot to be enabled/disabled on a per-port basis</title>
<updated>2008-11-01T01:55:13+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-11-01T01:55:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=aa95744915aba1b96fd226609e07ad1843437afc'/>
<id>urn:sha1:aa95744915aba1b96fd226609e07ad1843437afc</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>[phantom] Assume one net device per PCI function</title>
<updated>2008-10-31T01:55:58+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-10-31T01:52:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=32bc76f902d2f38974311acc12457f25819bf539'/>
<id>urn:sha1:32bc76f902d2f38974311acc12457f25819bf539</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>[settings] Add the notion of a "tag magic" to numbered settings</title>
<updated>2008-10-30T21:47:14+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-10-29T18:17:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=0a6c66a83018c64d961ee4e8601ae8950cbee00b'/>
<id>urn:sha1:0a6c66a83018c64d961ee4e8601ae8950cbee00b</id>
<content type='text'>
Settings can be constructed using a dotted-decimal notation, to allow
for access to unnamed settings.  The default interpretation is as a
DHCP option number (with encapsulated options represented as
"&lt;encapsulating option&gt;.&lt;encapsulated option&gt;".

In several contexts (e.g. SMBIOS, Phantom CLP), it is useful to
interpret the dotted-decimal notation as referring to non-DHCP
options.  In this case, it becomes necessary for these contexts to
ignore standard DHCP options, otherwise we end up trying to, for
example, retrieve the boot filename from SMBIOS.

Allow settings blocks to specify a "tag magic".  When dotted-decimal
notation is used to construct a setting, the tag magic value of the
originating settings block will be ORed in to the tag number.
Store/fetch methods can then check for the magic number before
interpreting arbitrarily-numbered settings.
</content>
</entry>
<entry>
<title>[phantom] Add CLP settings interface</title>
<updated>2008-10-28T18:49:58+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-10-28T18:49:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=1bc2adea9a56c028babe23fbc5b27a582e90ec4f'/>
<id>urn:sha1:1bc2adea9a56c028babe23fbc5b27a582e90ec4f</id>
<content type='text'>
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.
</content>
</entry>
</feed>
