diff options
| author | jhb <jhb@FreeBSD.org> | 2006-10-05 15:38:59 +0000 |
|---|---|---|
| committer | jhb <jhb@FreeBSD.org> | 2006-10-05 15:38:59 +0000 |
| commit | 88140f6436fa0f8b0fc6cca06c4a353d4b9ecf3c (patch) | |
| tree | ad8e2b461d8a3c7770e78da1b0ed10b692e619a4 /lib/libc/stdlib/exit.c | |
| parent | 4131837d351ce66f9a070dec90a1e0578a04695b (diff) | |
| download | FreeBSD-src-88140f6436fa0f8b0fc6cca06c4a353d4b9ecf3c.zip FreeBSD-src-88140f6436fa0f8b0fc6cca06c4a353d4b9ecf3c.tar.gz | |
The IPMI spec is ambiguous (or rather, it contradicts itself) about whether
or not the OS has to wait for RX_RDY or TX_RDY to be set before the OS sets
the control code in the control/status register. Looking at the interface
design, it seems that RX_RDY and TX_RDY are probably there to protect
access to the data register and have nothing to do with the control/status
register. Nevertheless, try to take what I think is the more conservative
approach and always wait for the appropriate [TR]X_RDY flag to be set
before writing any of the WR_NEXT, WR_END, RD_START, or RD_NEXT control
codes to the control/status register.
Diffstat (limited to 'lib/libc/stdlib/exit.c')
0 files changed, 0 insertions, 0 deletions
