> That's correct. lwIP does not check or creat the FCS, nor does it care for > padding. Both have to be handled by the driver or hardware (as do many MACs I > know).
Thanks for confirming this. It allowed me to be confident I had some other problems. (I am set up sending and receiving packets now) I have a follow up question, now that I am sending and receiving packets, I am wondering what sort of locking I need to provide on my driver. Can two threads enter into the low_level() functions? (I am running lwip with an OS, with a socket based model, and I am using an Ethernet RX worker task that will run after an RX interrupt) I think this should be added to the documentation as the description about the length of packets is rather slim. I don't mind editing the wiki if no one has objections. Regards Paul > > Simon > -- > Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! > Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail > > _______________________________________________ > lwip-users mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/lwip-users > -- ---- Regards Paul Archer [email protected] _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
