[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RE : RE : [lwip-devel] Last changes by Marc
From: |
Jonathan Larmour |
Subject: |
Re: RE : RE : [lwip-devel] Last changes by Marc |
Date: |
Tue, 21 Aug 2007 15:23:37 +0100 |
User-agent: |
Thunderbird 1.5.0.12 (X11/20070530) |
Frédéric BERNON wrote:
I had thought you had meant make it only the ETHARP_TCPIP_ETHINPUT option,
rather than make it no option at all. Not everyone uses ethernet, and
there may be other routes for drivers to introduce packets to the system
(e.g. via their own tcpip_callback calls, like PPP does), so it should
still be an option I think. Not least if anyone was using only PPP, not
ethernet.
Ok. So, which option? I think that LWIP_ARP should be enought and avoid to
(re-)add something like ETHARP_TCPIP_ETHINPUT or ETHARP_TCPIP_INPUT. Your point
of view?
I guess since for now at least LWIP_ARP is specific to ethernet, then yes
changing the #if ETHARP_TCPIP_ETHINPUT code to be LWIP_ARP would be fine
for me. And remove the ETHARP_TCPIP_INPUT specific code, as you wanted.
Jifl
--
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["The best things in life aren't things."]------ Opinions==mine