[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #25352] No MEMP_PBUF_POOL definition.
From: |
Jonathan Larmour |
Subject: |
[lwip-devel] [bug #25352] No MEMP_PBUF_POOL definition. |
Date: |
Sun, 18 Jan 2009 19:38:31 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.8.0.12) Gecko/20071018 Red Hat/1.5.0.12-0.7.el4 Firefox/1.5.0.12 pango-text |
Update of bug #25352 (project lwip):
Status: None => Works For Me
Assigned to: None => jifl
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
This is not an lwIP problem, but something with your port. pbuf.c does depend
on MEM_PBUF_POOL, but that gets defined in memp_std.h which is in turn
included from memp.h. What happens si that memp.h defines a macro
LWIP_MEMPOOL, which includes memp_std.h multiple times with different values
of the LWIP_MEMPOOL macro. In the first one, it is set as this:
typedef enum {
#define LWIP_MEMPOOL(name,num,size,desc) MEMP_##name,
#include "lwip/memp_std.h"
MEMP_MAX
} memp_t;
And in memp_std.h, there is:
#define LWIP_PBUF_MEMPOOL(name, num, payload, desc) LWIP_MEMPOOL(name, num,
(MEMP_ALIGN_SIZE(sizeof(struct pbuf)) + MEMP_ALIGN_SIZE(payload)), desc)
and
LWIP_PBUF_MEMPOOL(PBUF_POOL, PBUF_POOL_SIZE, PBUF_POOL_BUFSIZE,
"PBUF_POOL")
Note the use of the preprocessor string concatenation operator. So that's how
MEMP_PBUF_POOL gets defined.
Further discussion is better suited to the lwip-users list.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?25352>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/