Ian Dowse cb0d1e061b Revision 1.136 introduced two features that may cause undefined ... behaviour of the hardware: a possibly reserved bit of the receive descriptor (RFA) `status' field is borrowed to record no-resource (RNR) events, and the same status field is read and written to at a time that may clash with the hardware updating this field. There is no hardware documentation available to determine if these things are safe to do; the second issue almost certainly isn't, and the first is only safe if there is documentation saying that this bit is free to be used by the driver. The PR referenced below provides extremely convincing evidence that the changes cause random crashes on some (unusual) hardware. Since these features are only required by the DEVICE_POLLING case, this commit makes their use conditional on that option. It does not change the DEVICE_POLLING case, but at least people with the rare hardware on which this code causes problems can now avoid the crashes by not enabling DEVICE_POLLING. PR: kern/42260 Reviewed by: luigi Problem revision found by: Pawel Malachowski <pawmal@unia.3lo.lublin.pl> Tested by: Pawel Malachowski <pawmal@unia.3lo.lublin.pl> MFC after: 1 week		2002-10-30 19:08:56 +00:00
..
if_fxp.c	Revision 1.136 introduced two features that may cause undefined	2002-10-30 19:08:56 +00:00
if_fxpreg.h	. Add structure definition for microcode download.	2001-10-25 05:25:58 +00:00
if_fxpvar.h	Change callers of mtx_init() to pass in an appropriate lock type name. In	2002-04-04 21:03:38 +00:00
rcvbundl.h