> and only one interrupt runs at a time and isn't interrupted by another
> interrupt while using
lwIP - you should be safe.
Simon, could you clarify why nesting interrupts are a problem and
non-nesting are not? Do you mean that, if an interrupt executes lwIP
code then it should not be interrupted
Please disregard the previous post...
It was just me being lazy as to how to use cmake...
--Ivan
smime.p7s
Description: Signature cryptographique S/MIME
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwi
I fail to see where the problem is.
lwIP does not require an OS, as long as you can compile C code you are fine.
A port is basically what you described, you write your driver, you read
this:
http://www.nongnu.org/lwip/2_1_x/group__sys__layer.html
you modify architecture dependent files, and you put
On 26.10.2018 10:27, vr roriz wrote:
>> and only one interrupt runs at a time and isn't interrupted by another
>> interrupt while using
> lwIP - you should be safe.
>
> Simon, could you clarify why nesting interrupts are a problem and
> non-nesting are not? Do you mean that, if an interrupt execu
Le 10/26/2018 à 3:36 PM, Sergio R. Caprile a écrit :
I fail to see where the problem is.
lwIP does not require an OS, as long as you can compile C code you are fine.
A port is basically what you described, you write your driver, you read
this:
http://www.nongnu.org/lwip/2_1_x/group__sys__layer.
>Vitor, make sure your processes are never cycled by the scheduler
otherwise you'll violate the threading requirements. I'd suggest to just
have a single thread for lwip and use a mailbox or similar to trigger
certain actions. The OS will take care that you can write into the
mailbox from any inter
On 26.10.2018 15:57, vr roriz wrote:
>> Vitor, make sure your processes are never cycled by the scheduler
> otherwise you'll violate the threading requirements. I'd suggest to just
> have a single thread for lwip and use a mailbox or similar to trigger
> certain actions. The OS will take care that
