M. Koehrer wrote:
>  Hi Jan,
> 
> Oops, I had an error in my debug code. Sorry for that.
> The status value is actually 0x0050 and not 0xb70f.

That means: nothing pending, command unit is idle, receive unit is ready.

> The regular status values are 0x4050, 0x0050, 0x2050,
> That seems to be ok as well...
> One thing, I have just looked at:
> The driver uses the Early Interrupt (ER) Flag for signaling.
> Can this be, that the interrupt comes in, the ER is signaled but the data is 
> not yet
> available?!? How is this handled by the driver - or this is not relevant?

If you are referring to this line

http://www.rts.uni-hannover.de/rtnet/lxr/source/drivers/rt_eepro100.c#L1164

that's inverted logic. Set means "don't report!"

Did you already check how many RX events are reported in the IRQ and if
there is one missing after the last transmission?

Jan

Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users

Reply via email to