Messages in this thread |  | | Date | Wed, 12 Feb 1997 23:46:52 +0000 (GMT) | From | Chris Evans <> | Subject | Re: 2.0.27 major problems #1 -- 3c59x driver. |
| |
On Wed, 12 Feb 1997, Philip Blundell wrote:
> > Just cut and paste into the same area when the "access conflict" occurs. > > The idea is that when the controller refuses to work, reinitialize it. > > A transmitter access conflict is not disaster. There is no need to > reinitialise the controller - all it means is that the driver's > transmit routine was reentered, and the second transmit was deferred to > avoid contention.
I am forced to disagree -- when your card hangs it certainly _is_ a disaster. Additionally, the code implies that that if execution reaches this stage it is a disaster anyway; quote "if this ever happens then the queue layer is doing something evil"
Chris.
|  |