When building lwIP-1.4.1 on Linaro GCC v4.9.3 with -Wall, GCC issues
warnings in two places where the macro ip_addr_isany(addr1) is used, saying
the comparison against NULL will always evaluate to false. This warning is
correct in both cases because the macro is given the address of a local
stack v
On Sep 14, 2017, at 5:09 AM, Adrian Figueroa
wrote:
>
> I did some more testing and it does not seem to be systematic. As lwIP is not
> showing errors in any of the stats, it is likely not its fault.
>
> Do you have any suggestions on how to find the reason for dropped packets?
> Maybe someon
On Nov 6, 2017, at 6:57 AM, Elmar Wieser wrote:
>
> Hello,
>
> we have unreproduceable hardfaults in function lpc_enetif_input which occur
> randomly from 1 to 5 days.
>
> void lpc_enetif_input(struct netif *netif)
> {
> struct eth_hdr *ethhdr;
>
> struct pb
On Dec 20, 2017, at 10:17 AM, Ben Stuyts wrote:
>
> Hi,
>
> TI’s Stellarisware library for the LM3S series chips uses lwIP v1.3.1. By any
> chance, has anybody ported lwIP v2.0.3 to Stellarisware?
>
> They basically #include all the lwIP *.c files into a single lwiplib.c file
> and compile th
On Dec 20, 2017, at 7:23 PM, Ben Stuyts wrote:
>
> Hi Nathan,
>
>> On 20 Dec 2017, at 16:31, Nathan Hartman wrote:
>>
>> On Dec 20, 2017, at 10:17 AM, Ben Stuyts wrote:
>>>
>>> TI’s Stellarisware library for the LM3S series chips uses lwIP v1.3.1
On Jan 10, 2018, at 3:56 AM, MaartenPR wrote:
> For those interested and using the same processor and drivers. This is what
> I ended up changing in the stm32f7xx_hal_eth.c driver file (lines 1632 to
> 1653):
>
>
>
> Hope this help others with the same problems. Always check the hardware
> firs
On Mar 14, 2018, at 3:24 PM, "goldsi...@gmx.de" wrote:
>
>> On 14.03.2018 17:09, Giuseppe Modugno wrote:
>> #define MEM_LIBC_MALLOC 1
>>
>> If I try to set MEMP_MEM_MALLOC, I have some strange problems.
>
> I suspect threading issues. I checked on win32 and it seems to work fine. In
> the en
Under git tag STABLE-2_1_0_RC1 it appears that CHANGELOG entries for
STABLE-2.0.2 and STABLE-2.0.3 have disappeared. Is this intentional or an
error?
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
On Thu, Nov 8, 2018 at 11:57 PM uaz wrote:
> Hi all,
>
> I'm currently running lwip v2.0.3 on LPC4357 platform.
> I have some issue with pbuf mem_alloc(), which I believe is fragmentation
> issue because after several packet transfers, I'm unable to allocate pbuf
> anymore.
I once had a problem
On Sat, Mar 23, 2019 at 10:59 AM LRA_ wrote:
>
> The port has everything pretty much on the ethernet interrupt. I probably
> could change it, I hate it being there.
There's an article about how to get it out of the interrupt. Not sure what
the performance is like but it's for TM4C12x:
https://
On Thu, Jul 25, 2019 at 4:31 PM Dirk Ziegelmeier
wrote:
> What do you need an IP stack for when you want to process raw ethernet
> frames???
>
My guess is that you need it because the system does other things with the
network, too.
___
lwip-users maili
On Mon, Sep 23, 2019 at 5:08 PM Dave Nadler wrote:
>
> Apologies if I'm doing something silly...
> I started last fall with stable version 2.1.2 (downloaded tarball).
> In the course of working with LwIP I found+fixed a few minor issues;
> and hoped to create a couple pull requests for the fixes.
On Wed, Sep 25, 2019 at 5:33 PM Dave Nadler wrote:
> On 9/23/2019 5:21 PM, Nathan Hartman wrote:
>
> On Mon, Sep 23, 2019 at 5:08 PM Dave Nadler
> wrote:
>
> Apologies if I'm doing something silly...
> I started last fall with stable version 2.1.2 (downloaded ta
13 matches
Mail list logo
