[En-Nut-Discussion] Preview Fix 060626

[Michael Jones]

The "imr &= ~INT_RX_OVRN" does not seem to be a good idea as there is
nowhere where the overrun flags is enabled again once a overrun happens...
Cu,
Michael

-----Original Message-----
From: en-nut-discussion-bounces at egnite.de
[mailto:en-nut-discussion-bounces at egnite.de] On Behalf Of Harald Kipp
Sent: Tuesday, June 27, 2006 2:25 PM
To: Ethernut User Chat (English)
Subject: RE: [En-Nut-Discussion] Preview Fix 060626



At 14:12 27.06.2006 +0200, you wrote:

>Just one question: what does the "imr &= ~INT_RX_OVRN" do?

I did that without looking into the datasheet, but simply
because it is done similar in the other branches. It seems
to help. :-)

But not really. I additionally added a post to the receiver
queue and this seems to help a lot

     if (isr & INT_RX_OVRN) {
         putchar('O');
         imr &= ~INT_RX_OVRN;
         nic_outlb(NIC_ACK, INT_RX_OVRN);
         //nic_outlb(NIC_MMUCR, MMU_TOP);
         NutEventPostFromIrq(&ni->ni_rx_rdy); <--- Added
     }

Now my Ethernut 2 "feels" again like before.

Harald

_______________________________________________
En-Nut-Discussion mailing list
En-Nut-Discussion at egnite.de
http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion