Re: [lwip-users] Initialization of global variables

2010-11-05 Thread Piotr Piwko
2010/11/5 goldsi...@gmx.de : > You could have had that problem with any other third-party library. Why not > rely on a fact that is defined in the C standard? It makes the binary > smaller. OK, there might be code where those global variables get initalized > to zero/NULL again (lwIP did that, too,

Re: [lwip-users] Initialization of global variables

2010-11-05 Thread mat henshall
Jeff, that is a good solution. Next time I need to do this, I will look into that. Thanks. M On Fri, Nov 5, 2010 at 2:00 PM, Jeff Barber wrote: > Why don't you just imitate what the boot loader would do?  Find the > symbol that indicates the beginning of BSS and the symbol that > indicates the e

Re: [lwip-users] Initialization of global variables

2010-11-05 Thread Jeff Barber
Why don't you just imitate what the boot loader would do? Find the symbol that indicates the beginning of BSS and the symbol that indicates the end, find the difference and clear. Then only do that when your wakeup has decided there's something to do. Linker-dependent but usually these symbols ar

Re: [lwip-users] Initialization of global variables

2010-11-05 Thread mat henshall
Simon... It sounds like you are frustrated that this issue has been raised multiple times and doesn't seem to go away! I am sorry to add to the 'fire'. In all the important things that could be done/worked on this is, I am sure a low priority. I wanted to bring to your attention a use case where

Re: [lwip-users] Initialization of global variables

2010-11-05 Thread goldsi...@gmx.de
Rick Solotke wrote: I just wanted to pop in and say that I have observed and debugged the same problem, specifically for the UDP and TCP PCB lists. It would be great if the code could be changed to explicitly initialize these to NULL. You could have had that problem with any other third-party li

Re: [lwip-users] Initialization of global variables

2010-11-05 Thread Simon Goldschmidt
Excerpt from the ANSI-C Standard (e.g. http://flash-gordon.me.uk/ansi.c.txt): If an object that has static storage duration is not initialized explicitly, it is initialized implicitly as if every member that has arithmetic type were assigned 0 and every member that has pointer type were assigned a

Re: [lwip-users] Initialization of global variables

2010-11-05 Thread mat henshall
Simon, I have hit this problem where an environment by default turns off the initialization of globals for 'efficiency' and expects an application to explicit zero out the globals and statics as needed. For example, I use an ultra low powered wifi chip that has lwIP in ROM and it loads applicaiton

Re: [lwip-users] Initialization of global variables

2010-11-05 Thread Simon Goldschmidt
Hey Piotr, I hate to turn you down on that, but the variables are deliberately not being initialized: when not initialized (and thus implicitly zeroed at startup), they are put into the uninitialized section and no space on disk/in flash is needed. However when they are initialized to NULL, the

RE: [lwip-users] Initialization of global variables

2010-11-05 Thread Rick Solotke
Hi all, I just wanted to pop in and say that I have observed and debugged the same problem, specifically for the UDP and TCP PCB lists. It would be great if the code could be changed to explicitly initialize these to NULL. Cheers, Rick -Original Message- From: lwip-users-bounces+rsolotk

[lwip-users] Initialization of global variables

2010-11-05 Thread Piotr Piwko
Hello, I currently implement the LwIP stack under u-boot environment and I have one notice regarding global variables initialization. I think that every global variable which are not static should be initialized by NULL or 0 value. I mean for example: file tcp.c: struct tcp_pcb *tcp_bound_pcbs; u

Re: [lwip-users] Help on porting LWIP

2010-11-05 Thread Jeff Barber
Simon, Sure. Please feel free to update as appropriate. I've kept half an eye on the development of 1.4.0 but given the time frames, I haven't been in a position to upgrade the lwip version in my product (and probably won't be able to any time soon). Yes, the "mch_ip_addr" is simply a typedef for

Re: [lwip-users] Help on porting LWIP

2010-11-05 Thread Simon Goldschmidt
Great job, thanks for that! There are a few things I would change though, if it's OK for you (and when I find the time): - lwIP 1.4.0 provides ready-to-use functions for timers, so there's no need to implement that yourself - you used the type mch_ip_add, which is not defined anywhere - later, th

Re: [lwip-users] Help on porting LWIP

2010-11-05 Thread Jeff Barber
Done. New page on the wiki at http://lwip.wikia.com/wiki/Porting_For_Bare_Metal On Thu, Nov 4, 2010 at 3:50 PM, Kieran Mansley wrote: > > On 4 Nov 2010, at 17:55, Jeff Barber wrote: > >> I went through this learning curve last year and did essentially the >> same thing (for a very different boa

RE: [lwip-users] Help on porting LWIP

2010-11-05 Thread André
Kieran, I think I will have some problems in the beggining, if I get lots of troubles, I will try to port on a Windows machine and learn it before porting. Ty for your answer. []s André --- Em qui, 4/11/10, Kieran Mansley escreveu: > De: Kieran Mansley > Assunto: RE: [lwip-users] Help on po

Re: [lwip-users] Help on porting LWIP

2010-11-05 Thread André
Jeff, Thanks a lot for this steps. By now, as I can see, I will have a lot of work to do. If I got any sucees I will post in here, so anyone who needs something that looks like what I'm doing will be able to use it. Ty everyone []s André --- Em qui, 4/11/10, Jeff Barber escreveu: > De: Jeff