On 05/25/2011 04:50 AM, abhimanyu kapur wrote:
Hi
I am very new to lwIP and need support. I am using a custom OS , and i
am required to port lwIP onto my patform. I did see some material
online, but i am hoping to get some documentation / instructions on
porting lwIP on my OS. I also tried buty
Hi
I am very new to lwIP and need support. I am using a custom OS , and i am
required to port lwIP onto my patform. I did see some material online, but i
am hoping to get some documentation / instructions on porting lwIP on my OS.
I also tried buty could not find the sys_arch.c file. Do i have to
Kieran Mansley wrote:
On Tue, 2011-05-24 at 15:14 +0200, ake.forsl...@nibe.se wrote:
1. Can I use threads? One to receive and one to transmit data and
then
check if the data arrives correctly?
You can, but I would do it all in one thread, and use poll() to
determine when each socket needs atten
"Walter Saegesser" wrote:
> Thanks for the instructions. I completely misinterpreted the use of
> sys_mbox_set_invalid / sys_sem_set_invalid. I thought you just wanted to
> invalidate a previously valid mbox or sem.
> Does 'sys_xxx_free' also have to invalidate the the mbox or sem, i.e.
> *mbox =
Hi Åke,
On mar, 2011-05-24 at 15:14 +0200, ake.forsl...@nibe.se wrote:
> My questions are:
> 1. Can I use threads? One to receive and one to transmit data and then
> check if the data arrives correctly?
Yes, you can. I only have experience with sockets API (which in my
opinion is simpler to use
On Tue, 2011-05-24 at 15:14 +0200, ake.forsl...@nibe.se wrote:
> 1. Can I use threads? One to receive and one to transmit data and
> then
> check if the data arrives correctly?
You can, but I would do it all in one thread, and use poll() to
determine when each socket needs attention (either sendi
Hi,
I've just started porting lwip to our platform and I have run in to some
slight problems and I hope this is the right mailing list for these kind
of questions (if it isn't please redirect me to a more suitable place)
I've gotten the porting layer in place and the my lwip_init() has stopped
m.duck...@kunbus.de wrote:
> in ethernetif_init() of lwIP 1.4.0 in the file ethernetif.c there is
> memory allocated for the struct ethernetif and assigned to netif->state.
> This data is never used in the lwip stack and not freed in netif_remove().
> I think this malloc and assignment should be
Hi,
in ethernetif_init() of lwIP 1.4.0 in the file ethernetif.c there is
memory allocated for the struct ethernetif and assigned to netif->state.
This data is never used in the lwip stack and not freed in netif_remove().
I think this malloc and assignment should be removed.
regards
Mathias
Hi Simon
> The macro sys_mbox_set_invalid() is (like the name says) supposed
> to set a pointer to an mbox to a known state so that we can later
> check if that pointer is valid (mbox created) or invalid (mbox not
created).
> E.g. if you defined sys_mbox_t to "void*", then you would
> #define s
On Tue, 2011-05-24 at 08:07 +0200, Walter Saegesser wrote:
> The concept of many people writing the documentation is welcome. But
> there should or maybe even must be a supervisor, who approves or
> disapproves the information given. Otherwise I fear that people will
> sooner or later realize they
"Walter Saegesser" wrote:
> conn = (struct netconn *)memp_malloc(MEMP_NETCONN);
> ...
> sys_mbox_set_invalid(&conn->acceptmbox);
>
> As far as I see, 'acceptmbox' has not been assigned and thus can hold
> any value - if you are unlucky enough even a valid handle.
The macro sys_mbox_set_inva
12 matches
Mail list logo
