Searched hist:a2642c4d671663ccebc3574cebde8efbfa324ba1 (Results 1 – 1 of 1) sorted by relevance
| /freebsd/sys/dev/fdc/ |
| H A D | fdc.c | diff a2642c4d671663ccebc3574cebde8efbfa324ba1 Tue May 14 23:28:45 CEST 2002 Joerg Wunsch <joerg@FreeBSD.org> After some comments from bde, rewrite the loops to avoid turning the
previously used "micro-optimization" (count-down loop) into a
pessimization. Now the loops are written in the more natural count-up
form.
Also, while being there, i made the logic in out_fdc() similar to the
logic in in_fdc(). The old implementation was a bit bogus anyway
since it first tested the DIO bit and only afterwards the RQM bit.
However, according to the description of the i82077, the DIO bit is
only guaranteed to be valid once the RQM bit is set. Thus, the old
implementatoin would have had the chance to misbehave on a controller
that is implemented in accordance with the i82077 description (but is
not bug-for-bug compatible).
MFC after: 3 days
diff a2642c4d671663ccebc3574cebde8efbfa324ba1 Tue May 14 23:28:45 CEST 2002 Joerg Wunsch <joerg@FreeBSD.org> After some comments from bde, rewrite the loops to avoid turning the
previously used "micro-optimization" (count-down loop) into a
pessimization. Now the loops are written in the more natural count-up
form.
Also, while being there, i made the logic in out_fdc() similar to the
logic in in_fdc(). The old implementation was a bit bogus anyway
since it first tested the DIO bit and only afterwards the RQM bit.
However, according to the description of the i82077, the DIO bit is
only guaranteed to be valid once the RQM bit is set. Thus, the old
implementatoin would have had the chance to misbehave on a controller
that is implemented in accordance with the i82077 description (but is
not bug-for-bug compatible).
MFC after: 3 days
|