<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openslx-ng/ipxe.git/src/drivers, branch v0.9.8</title>
<subtitle>Fork of ipxe; additional commands and features</subtitle>
<id>https://git.openslx.org/openslx-ng/ipxe.git/atom/src/drivers?h=v0.9.8</id>
<link rel='self' href='https://git.openslx.org/openslx-ng/ipxe.git/atom/src/drivers?h=v0.9.8'/>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/'/>
<updated>2009-10-14T01:11:16+00:00</updated>
<entry>
<title>[hermon] Reset device during probe()</title>
<updated>2009-10-14T01:11:16+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2009-10-14T01:09:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=9f7141a1cedeca6d55b9ce43322f509a4577c883'/>
<id>urn:sha1:9f7141a1cedeca6d55b9ce43322f509a4577c883</id>
<content type='text'>
Some systems will retry their boot sequence in the event of a boot
failure.  On these systems, the second and subsequent boot attempts
will fail to initialise the Hermon HCA.

Fix by resetting the HCA during probe().  This incurs a one-second
cost, but there seems to be no viable alternative.

Originally-fixed-by: Itay Gazit &lt;itaygazit@gmail.com&gt;
</content>
</entry>
<entry>
<title>[pci] Add generic configuration space backup/restore facility</title>
<updated>2009-10-14T01:06:23+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2009-10-14T01:06:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=4175b778c277c87980266c854139b7f93b5564d9'/>
<id>urn:sha1:4175b778c277c87980266c854139b7f93b5564d9</id>
<content type='text'>
Some devices can only be reset via a mechanism that also resets the
card's PCI core, thus necessitating a backup and restore of all or
part of the PCI configuration space across a reset.
</content>
</entry>
<entry>
<title>[ath5k] Remove spurious debugging check</title>
<updated>2009-08-17T23:10:53+00:00</updated>
<author>
<name>Joshua Oreman</name>
</author>
<published>2009-08-17T22:02:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=d7dfc9572e84b8ff55751096181068c63c58d826'/>
<id>urn:sha1:d7dfc9572e84b8ff55751096181068c63c58d826</id>
<content type='text'>
Signed-off-by: Marty Connor &lt;mdc@etherboot.org&gt;
</content>
</entry>
<entry>
<title>[netdevice] Allow the hardware and link-layer addresses to differ in size</title>
<updated>2009-08-11T23:23:38+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2009-08-11T22:40:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=4eab5bc8ca6b66dc965cf188dd4577ad19c5b879'/>
<id>urn:sha1:4eab5bc8ca6b66dc965cf188dd4577ad19c5b879</id>
<content type='text'>
IPoIB has a 20-byte link-layer address, of which only eight bytes
represent anything relating to a "hardware address".

The PXE and EFI SNP APIs expect the permanent address to be the same
size as the link-layer address, so fill in the "permanent address"
field with the initial link layer address (as generated by
register_netdev() based upon the real hardware address).
</content>
</entry>
<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>[infiniband] Allow SRP reconnection attempts even after reporting failures</title>
<updated>2009-08-10T21:30:56+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2009-08-10T01:20:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=965a0f7a75ef0011062413a6fa62ab6404e0b1ea'/>
<id>urn:sha1:965a0f7a75ef0011062413a6fa62ab6404e0b1ea</id>
<content type='text'>
With iSCSI, connection attempts are expensive; it may take many
seconds to determine that a connection will fail.  SRP connection
attempts are much less expensive, so we may as well avoid the
"optimisation" of declaring a state of permanent failure after a
certain number of attempts.  This allows a gPXE SRP initiator to
resume operations after an arbitrary amount of SRP target downtime.
</content>
</entry>
<entry>
<title>[infiniband] Add support for SRP over Infiniband</title>
<updated>2009-08-10T21:27:33+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2009-07-17T21:11:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=0c30dc6bc5f26e7011ddfcda34d7adac653464cf'/>
<id>urn:sha1:0c30dc6bc5f26e7011ddfcda34d7adac653464cf</id>
<content type='text'>
SRP is the SCSI RDMA Protocol.  It allows for a method of SAN booting
whereby the target is responsible for reading and writing data using
Remote DMA directly to the initiator's memory.  The software initiator
merely sends and receives SCSI commands; it never has to touch the
actual data.
</content>
</entry>
<entry>
<title>[hermon] Reduce the RC ACK timeout</title>
<updated>2009-08-10T21:22:42+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2009-08-10T01:10:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=1175f0cf29acbb8328e1ab054bb0f5d7077c3cc0'/>
<id>urn:sha1:1175f0cf29acbb8328e1ab054bb0f5d7077c3cc0</id>
<content type='text'>
The ACK timeout determines how long we take to notice a failed
Reliable Connection.  Reducing it from the arbitrary value of 19 down
to 14 reduces the individual ACK timeout from around 2.1s to 67ms;
this in turn reduces the time to tear down and re-establish a broken
SRP session from around 30s to around 1s.
</content>
</entry>
<entry>
<title>[hermon] Randomise the high-order bits of queue pair numbers</title>
<updated>2009-08-10T21:19:39+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2009-08-09T19:38:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=0b1222f2332e89bcece1912ec6058479b45f62f1'/>
<id>urn:sha1:0b1222f2332e89bcece1912ec6058479b45f62f1</id>
<content type='text'>
The Infiniband Communication Manager will refuse to establish a
connection if it believes the connection is already established.
There is no immediately obvious way to ask it to tear down the
existing connection and replace it; to issue a DREP we would need to
know the local and remote communication IDs used for the previous
connection setup.

We can work around this by randomising the high-order bits of the
queue pair number; these have no significance to the hardware, but are
sufficient to convince the IB CM that this is a different connection.
</content>
</entry>
<entry>
<title>[scsi] Generalise iscsi_parse_lun() to scsi_parse_lun()</title>
<updated>2009-08-10T18:30:41+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2009-08-09T14:30:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=d94479468010ba2f64bc8664585e9c3491129303'/>
<id>urn:sha1:d94479468010ba2f64bc8664585e9c3491129303</id>
<content type='text'>
</content>
</entry>
</feed>
