David Lockyer wrote:
Okay, thank you for the suggestion. Just to be clear are you
suggesting modifying lwip_select() to allocate select_cb from a pool &
free prior to return?
Via a define, like Joel wrote, yes. This might need a new memp pool
though...
We don't have an abstraction for your p
> On Sep 7, 2017, at 9:14 AM, David Lockyer wrote:
>
> Hi Simon,
>
> Okay, thank you for the suggestion. Just to be clear are you suggesting
> modifying lwip_select() to allocate select_cb from a pool & free prior to
> return?
>
> I will have to investigate the speed impact of this, as I hav
Hi Simon,
Okay, thank you for the suggestion. Just to be clear are you suggesting
modifying lwip_select() to allocate select_cb from a pool & free prior
to return?
I will have to investigate the speed impact of this, as I have
MEM_LIBC_MALLOC and MAEP_MEM_MALLOC both defined as 1.
David
On 0
Looks correct. I guess mpu mode is not used too often. My suggestion would
probably be to get select_cb from a Memo pool...
Simon
Am 6. September 2017 16:12:47 MESZ schrieb David Lockyer
:
>Hi,
>
>I have a project that uses an STM32F MCU running FreeRTOS (cortex mpu
>port) & lwip, with the MP
Hi David,
Most of my code is RAW API so I have not seen any issues.
BR,
Noam.
From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On
Behalf Of David Lockyer
Sent: Thursday, September 07, 2017 11:21 AM
To: lwip-users@nongnu.org
Subject: Re: [lwip-users] LWIP_MPU_COMPATIBLE set
Hi Noam,
Thanks for the files, they are not too dissimilar to what I have.
My sys_arch_protect / sys_arch_unprotect are slightly different:
sys_prot_t sys_arch_protect(void)
{
vPortEnterCritical();
return 1;
}
void sys_arch_unprotect(sys_prot_t pval)
{
( void ) pval;
vPortExitCr
