John Baldwin fab2d1adf6 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.		2006-10-05 15:38:59 +00:00
..
ipmi.c	Fix a memory leak in ipmi_unload().	2006-09-26 15:48:13 +00:00
ipmi_acpi.c	Update the ipmi(4) driver:	2006-09-22 22:11:29 +00:00
ipmi_isa.c	Update the ipmi(4) driver:	2006-09-22 22:11:29 +00:00
ipmi_kcs.c	Update the ipmi(4) driver:	2006-09-22 22:11:29 +00:00
ipmi_pci.c	Update the ipmi(4) driver:	2006-09-22 22:11:29 +00:00
ipmi_smbios.c	Map pmap_{un,}mapbios() to pmap_{un,}mapdev() on 6.x and earlier.	2006-09-22 22:16:20 +00:00
ipmi_smbus.c	Update the ipmi(4) driver:	2006-09-22 22:11:29 +00:00
ipmi_smic.c	The IPMI spec is ambiguous (or rather, it contradicts itself) about whether	2006-10-05 15:38:59 +00:00
ipmi_ssif.c	Update the ipmi(4) driver:	2006-09-22 22:11:29 +00:00
ipmivars.h	Update the ipmi(4) driver:	2006-09-22 22:11:29 +00:00