diff options
author | yongari <yongari@FreeBSD.org> | 2010-08-23 18:51:31 +0000 |
---|---|---|
committer | yongari <yongari@FreeBSD.org> | 2010-08-23 18:51:31 +0000 |
commit | f76184d2bf5b1a3c4d5c2a7e475a3e0217a1c52d (patch) | |
tree | 009db2044ff03308e264f6b1c86c1c8757397f5e /gnu/lib/libgomp | |
parent | c508e8d0565077199d527e8af2593119f8162450 (diff) | |
download | FreeBSD-src-f76184d2bf5b1a3c4d5c2a7e475a3e0217a1c52d.zip FreeBSD-src-f76184d2bf5b1a3c4d5c2a7e475a3e0217a1c52d.tar.gz |
Move xl_reset() to xl_init_locked(). This will make driver
initialize controller from a known good state. Previously driver
used to issue controller reset while TX/RX DMA are in progress.
I guess resetting controller in active TX/RX DMA cycle is to ensure
stopping I/Os in xl_shutdown(). I remember some buggy controllers
didn't respond with stop command if controller is under high
network load at the time of shutdown so resetting controller was
the only safe way to stop the I/Os. However, from my experiments,
controller always responded with stop command under high network
load so I think it's okay to remove the xl_reset() in
device_shutdown handler.
Resetting controller also will clear configured RX filter which
in turn will make WOL support hard because driver have to reprogram
RX filter in WOL handler as well as setting station address.
Diffstat (limited to 'gnu/lib/libgomp')
0 files changed, 0 insertions, 0 deletions