[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #26133] Processor specific porting needs flexibility i
From: |
Srinivas Gollakota |
Subject: |
[lwip-devel] [bug #26133] Processor specific porting needs flexibility in terms of placement of various memory pools. |
Date: |
Wed, 15 Apr 2009 21:06:27 +0000 |
User-agent: |
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; YComp 5.0.0.0; SV1; GTB5) |
Follow-up Comment #4, bug #26133 (project lwip):
>Ideally this should be an optional feature, so the existing
>behaviour is the default (as that is what most will want) and >those that
need it could specify something like #define >LWIP_MEMP_EXTERNALLY_ALLOCATED 1
(just a suggestion for the >name) in lwipopts.h
Sure,This would be an optional feature for those who want to have finer
control on the placement rather than compiler chosen one.
One way is as below.
#ifdef LWIP_MEMP_EXTERNALLY_ALLOCATED
static u8_t* memp_memory;
u8_t** lwip_memp_ptr = &memp_memory;
u32_t lwip_memp_len = xxx; // length of the memp memory
#else
// default
#endif
and init routine will set the pointer to appropriate location
*lwip_memp_ptr = xxx;
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?26133>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/