summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* [release] Update version to 0.9.8 for releasev0.9.8Marty Connor2009-10-141-2/+2
|
* [hermon] Reset device during probe()Michael Brown2009-10-142-0/+28
| | | | | | | | | | | 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 <itaygazit@gmail.com>
* [pci] Add generic configuration space backup/restore facilityMichael Brown2009-10-142-0/+123
| | | | | | 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.
* [job] Report progress of downloader jobs via job_progress()Michael Brown2009-08-311-2/+21
|
* [job] Add missing job_progress() interface methodMichael Brown2009-08-312-0/+10
|
* [ath5k] Remove spurious debugging checkJoshua Oreman2009-08-181-10/+0Star
| | | | Signed-off-by: Marty Connor <mdc@etherboot.org>
* [802.11] Support multicast hashingMichael Brown2009-08-123-22/+4Star
| | | | | | | 802.11 multicast hashing is the same as standard Ethernet hashing, so just expose and use eth_mc_hash(). Signed-off-by: Joshua Oreman <oremanj@rwcr.net>
* [802.11] Properly initialize autoassociation processJoshua Oreman2009-08-121-1/+2
| | | | | | | | | | | | | The recent change to process_add() to detect duplicate process additions relies on the fact that all processes will be initialized using process_init_stopped() before being passed to that function. The autoassociation process was not initialized in this fashion, so process_add() erroneously detected it as a duplicate. Fix by using process_init_stopped() to initialize the autoassociation process instead of setting the step member directly. Signed-off-by: Michael Brown <mcb30@etherboot.org>
* [dhcp] Fall back to using the hardware address to populate the chaddr fieldMichael Brown2009-08-123-12/+52
| | | | | | | | | | | | | | | | | | | | | | | | For IPoIB, the chaddr field is too small (16 bytes) to contain the 20-byte IPoIB link-layer address. RFC4390 mandates that we should pass an empty chaddr field and rely on the DHCP client identifier instead. This has many problems, not least of which is that a client identifier containing an IPoIB link-layer address is not very useful from the point of view of creating DHCP reservations, since the QPN component is assigned at runtime and may vary between boots. Leave the DHCP client identifier as-is, to avoid breaking existing setups as far as possible, but expose the real hardware address (the port GUID) via the DHCP chaddr field, using the broadcast flag to instruct the DHCP server not to use this chaddr value as a link-layer address. This makes it possible (at least with ISC dhcpd) to create DHCP reservations using host declarations such as: host duckling { fixed-address 10.252.252.99; hardware unknown-32 00:02:c9:02:00:25:a1:b5; }
* [netdevice] Allow the hardware and link-layer addresses to differ in sizeMichael Brown2009-08-128-17/+66
| | | | | | | | | | 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).
* [netdevice] Separate out the concept of hardware and link-layer addressesMichael Brown2009-08-1222-82/+71Star
| | | | | | | | | | | 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().
* [doc] Expand scope of doxygen-generated documentationMichael Brown2009-08-114-30/+45
|
* [zbin] Change fixup semantics to support ROMs over 128k uncompressedJoshua Oreman2009-08-117-75/+92
| | | | | | | | | | | | | | | | | | | | | | | | The option ROM header contains a one-byte field indicating the number of 512-byte sectors in the ROM image. Currently it is linked to contain the number of uncompressed sectors, with an instruction to the compressor to correct it. This causes link failure when the uncompressed size of the ROM image is over 128k. Fix by replacing the SUBx compressor fixup with an ADDx fixup that adds the total compressed output length, scaled as requested, to an addend stored in the field where the final length value will be placed. This is similar to the behavior of ELF relocations, and ensures that an overflow error will not be generated unless the compressed size is still too large for the field. This also allows us to do away with the _filesz_pgh and _filesz_sect calculations exported by the linker script. Output tested bitwise identical to the old SUBx mechanism on hd, dsk, lkrn, and rom prefixes, on both 32-bit and 64-bit processors. Modified-by: Michael Brown <mcb30@etherboot.org> Signed-off-by: Michael Brown <mcb30@etherboot.org>
* [doc] Update doxygen.cfg to match version running on rom.etherboot.orgMichael Brown2009-08-111-75/+320
|
* [infiniband] Add support for the SRP Boot Firmware TableMichael Brown2009-08-103-0/+236
| | | | | | The SRP Boot Firmware Table serves a similar role to the iSCSI and AoE Boot Firmware Tables; it provides information required by the loaded OS in order to establish a connection back to the SRP boot device.
* [infiniband] Disambiguate CM connection rejection reasonsMichael Brown2009-08-103-4/+32
| | | | | | | | | | | | | There is diagnostic value in being able to disambiguate between the various reasons why an IB CM has rejected a connection attempt. In particular, reason 8 "invalid service ID" can be used to identify an incorrect SRP service_id root-path component, and reason 28 "consumer reject" corresponds to a genuine SRP login rejection IU, which can be passed up to the SRP layer. For rejection reasons other than "consumer reject", we should not pass through the private data, since it is most likely generated by the CM without any protocol-specific knowledge.
* [infiniband] Allow SRP reconnection attempts even after reporting failuresMichael Brown2009-08-102-18/+5Star
| | | | | | | | | 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.
* [infiniband] Generate more specific errors in response to failure MADsMichael Brown2009-08-104-6/+8
| | | | | | | Generate errors within individual MAD transaction consumers such as ib_pathrec.c and ib_mcast.c, rather than within ib_mi.c. This allows for more meaningful error messages to eventually be displayed to the user.
* [infiniband] Add support for SRP over InfinibandMichael Brown2009-08-109-0/+1960
| | | | | | | | 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.
* [infiniband] Add last_opened_ibdev(), analogous to last_opened_netdev()Michael Brown2009-08-103-1/+27
| | | | | | | The minimal-surprise behaviour, when no explicit SRP initiator device is specified, will probably be to use the most recently opened Infiniband device. This matches our behaviour with using the most recently opened net device for PXE, iSCSI, AoE, NBI, etc.
* [infiniband] Add find_ibdev()Michael Brown2009-08-102-0/+17
|
* [infiniband] Add a "communication-managed reliable connection" protocolMichael Brown2009-08-103-0/+456
| | | | | | | SRP over Infiniband uses a protocol whereby data is sent via a combination of the CM private data fields and the RC queue pair itself. This seems sufficiently generic that it's worth having available as a separate protocol.
* [hermon] Reduce the RC ACK timeoutMichael Brown2009-08-101-1/+1
| | | | | | | | 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.
* [hermon] Randomise the high-order bits of queue pair numbersMichael Brown2009-08-102-6/+7
| | | | | | | | | | | | | 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.
* [scsi] Make LUN a property of the SCSI backend onlyMichael Brown2009-08-102-3/+0Star
| | | | | Nothing within the SCSI core actually refers to the LUN, so we can simplify matters by treating it as purely a property of the backend.
* [scsi] Generalise iscsi_parse_lun() to scsi_parse_lun()Michael Brown2009-08-104-48/+48
|
* [scsi] Generalise iscsi_detached_command() to scsi_detached_command()Michael Brown2009-08-103-6/+15
|
* [process] Make it safe to call process_add() multiple timesMichael Brown2009-08-105-3/+14
|
* [infiniband] Handle duplicate Communication Management REPsMichael Brown2009-08-092-0/+58
| | | | | | | | | | | We will terminate our transaction as soon as we receive the first CM REP, since that provides all the state that we need. However, the peer may resend the REP if it didn't see our RTU, and if we don't respond with another RTU we risk being disconnected. (This protocol appears not to handle retries gracefully.) Fix by adding a management agent that will listen for these duplicate REPs and send back an RTU.
* [ath5k] Add support for non-802.11n Atheros wireless NICsJoshua Oreman2009-08-0921-0/+17970
| | | | Signed-off-by: Michael Brown <mcb30@etherboot.org>
* [legal] Add MIT licence declarationJoshua Oreman2009-08-091-0/+10
| | | | Signed-off-by: Michael Brown <mcb30@etherboot.org>
* [802.11] Fix memory leak on unsuccessful probesJoshua Oreman2009-08-091-2/+1Star
| | | | | | | When a probe found no results, the list head of beacons would not be freed, leaking 16 bytes of memory per probe. Signed-off-by: Michael Brown <mcb30@etherboot.org>
* [802.11] Fix maximum packet lengthJoshua Oreman2009-08-091-5/+13
| | | | | | | | | | | | | Previously the maximum packet length was computed using an erroneous understanding of the role of the MIC field in TKIP-encrypted packets. The field is actually considered to be part of the MSDU (encrypted and fragmented data), not the MPDU (container for each encrypted fragment). As such its size does not contribute to cryptographic overhead outside the data field's size limitations. The net result is that the previous maximum packet length value was 4 bytes too long; fix it to the correct value of 2352. Signed-off-by: Michael Brown <mcb30@etherboot.org>
* [802.11] Set channels early on to avoid tuning to an undefined channelJoshua Oreman2009-08-091-0/+5
| | | | | | | | | | | Some cards (such as ath5k) always need to tune to a particular channel when they are reset; the reset may happen upon open(), which is before the channels array would be set up (in prepare_probe()). Avoid tuning the card to an inconsistent state by copying the hardware supported-channels array to the 802.11 device's allowable-channels array even before channels are "properly" set up. Signed-off-by: Michael Brown <mcb30@etherboot.org>
* [802.11] Enhance support for driver PHY differencesJoshua Oreman2009-08-093-44/+147
| | | | | | | | | | | | | | | | | The prior net80211 model of physical-layer behavior for drivers was overly simplistic and limited the drivers that could be written. To be more flexible, split the driver-provided list of supported rates by band, and add a means for specifying a list of supported channels. Allow drivers to specify a hardware channel value that will be tied to uses of the channel. Expose net80211_duration() to drivers, and make the rate it uses in its computations configurable, so that it can be used in calculating durations that must be set in hardware for ACK and CTS packets. Add net80211_cts_duration() for the common case of calculating the duration for a CTS packet. Signed-off-by: Michael Brown <mcb30@etherboot.org>
* [geniso] Emit proper error message for incorrect location of ISOLINUX_BINvibi sreenivasan2009-08-091-1/+1
| | | | | | | | If isolinux.bin is not installed in the expected location the error message shown is slightly misleading. Signed-off-by: Vibi Sreenivasan <vibi_sreenivasan@cms.com> Signed-off-by: Michael Brown <mcb30@etherboot.org>
* [infiniband] Update all other MAD users to use a management interfaceMichael Brown2009-08-0912-992/+747Star
|
* [infiniband] Update subnet management agent to use a management interfaceMichael Brown2009-08-098-313/+412
|
* [infiniband] Add the concept of a management interfaceMichael Brown2009-08-094-1/+549
| | | | | | | | | A management interface is the component through which both local and remote management agents are accessed. This new implementation of a management interface allows for the user to react to timed-out transactions, and also allows for cancellation of in-progress transactions.
* [hermon] Allow for multiple calls to ib_modify_qp()Michael Brown2009-08-092-31/+64
|
* [romprefix] Cope with PnP BIOSes that fail to set %es:%di on entryMichael Brown2009-08-081-7/+20
| | | | | | | | | | | | Some BIOSes support the BIOS Boot Specification (BBS) but fail to set %es:%di correctly when calling the option ROM initialisation entry point. This causes gPXE to identify the BIOS as non-PnP (and so non-BBS), leaving the user unable to control the boot order. Fix by scanning for the $PnP signature ourselves, rather than relying on the BIOS having passed in %es:%di correctly. Tested-by: Helmut Adrigan <helmut.adrigan@chello.at>
* [hermon] Add support for multiple ports and detecting non-IB portsMichael Brown2009-08-063-31/+110
| | | | Originally-fixed-by: Itay Gazit <itaygazit@gmail.com>
* [infiniband] Change IB_{QPN,QKEY,QPT} names from {SMA,GMA} to {SMI,GSI}Michael Brown2009-08-065-30/+30
| | | | | | | | | | The IBA specification refers to management "interfaces" and "agents". The interface is the component that connects to the queue pair and sends and receives MADs; the agent is the component that constructs the reply to the MAD. Rename the IB_{QPN,QKEY,QPT} constants as a first step towards making this separation in gPXE.
* [build] Mark __intel_new_proc_init with __libgcc rather than cdeclMichael Brown2009-08-031-1/+1
| | | | | | | | | | The function __intel_new_proc_init() (called implicitly when building using icc) is marked with __attribute__((cdecl)). This breaks building on x86_64, where cdecl is meaningless. Fix by replacing with the existing __libgcc macro, which is already defined to be "__attribute__((cdecl))" for i386 builds and empty for x86_64 builds.
* [sky2] Add support for Marvell Yukon-II gigabit Ethernet cardsJoshua Oreman2009-08-033-0/+4576
| | | | Signed-off-by: Michael Brown <mcb30@etherboot.org>
* [pci] Add definitions for Advanced Error Reporting registersJoshua Oreman2009-08-031-0/+27
| | | | Signed-off-by: Michael Brown <mcb30@etherboot.org>
* [legal] Add the MIT and ISC licenses to licence.plH. Peter Anvin2009-08-031-0/+25
| | | | | | | | The MIT and ISC licenses are legally equivalent to the bsd2 license, but with slightly different verbiage. Signed-off-by: H. Peter Anvin <hpa@zytor.com> Signed-off-by: Michael Brown <mcb30@etherboot.org>
* [pxe] Dual-license pxe_api.h under the MIT licenseH. Peter Anvin2009-08-031-0/+25
| | | | | | | | | pxe_api.h is just a description of API functions, it's actively undesirable to have more implementations than necessary. Allowing it under the MIT license lets the Syslinux libraries use it. Signed-off-by: H. Peter Anvin <hpa@zytor.com> Signed-off-by: Michael Brown <mcb30@etherboot.org>
* [config] Enable PXE commands by default only on pcbios architectureJoshua Oreman2009-08-032-1/+3
| | | | | | | The commands bring in UNDI and thus real-mode code, so they cannot be used on EFI. Signed-off-by: Michael Brown <mcb30@etherboot.org>
* [pxe] Avoid printf format warning on some compilersMichael Brown2009-08-021-1/+1
| | | | Tested-by: Joshua Oreman <oremanj@xenon.get-linux.org>