Look  http://www.sics.se/~adam/lwip/os.html. It's old, but most of the document 
is always valid. It explain "how" implement lwip with or without OS. Be careful 
about multithreading if you use it (lwip core have to be protected against 
concurrent access), but it's not your case I think.
 
 
  
====================================
Frédéric BERNON 
HYMATOM SA 
Chef de projet informatique 
Microsoft Certified Professional 
Tél. : +33 (0)4-67-87-61-10 
Fax. : +33 (0)4-67-70-85-44 
Email : [EMAIL PROTECTED] 
Web Site : http://www.hymatom.fr <http://www.hymatom.fr/>  
====================================
P Avant d'imprimer, penser à l'environnement
 

        -----Message d'origine-----
        De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Mumtaz 
Ahmad
        Envoyé : mercredi 23 mai 2007 06:26
        À : Mailing list for lwIP users
        Objet : Re: [lwip-users] Example port for a beginner
        
        
        1    In my point of view windows port is the most simple port to start 
with .
        2    Yes lwip stack can be implemented without sys_arch.c provided that 
you understand where the stack should be made thread safe . I have done it by 
myself and implemented my own api layer as well .
        4    Yes sys_timeouts  is pretty confusing but if you implement your 
own api layer then you can ignore it all together 
         

                ----- Original Message ----- 
                From: Bilahari Akkiraju <mailto:[EMAIL PROTECTED]>  
                To: [email protected] 
                Sent: Wednesday, May 23, 2007 3:19 AM
                Subject: [lwip-users] Example port for a beginner


                
                  Hello all ,  I have few questions on lwip-1.2.0 ( I hope I 
have chosen a minimum risk version, is it a stable version)

                1 . Any good example of a port that's available for a beginenr 
who is trying to port lwip to ppc 83xx. 

                2. Can I port lwip stack without implementing sys_arch.c at 
all. I mean without impelementing semaphore and mailbox funcs.

                3 . Should I change or add some stuff in sys.c like in 
sys_arch.c. 

                4. And what exactly does sys_timeouts structure in sys.h 
signify  ? I see that it's a linked list with each node having time value, 
handler and its arguments. Whats the logic behind duch design, why is it a 
linked list, does it store different timers each with its own base value, 
handler that fires when it hits low or a high ?. I am throughly confused about 
this way of dealing with timeouts.

                Thanks. 

                
  _____  


                

                _______________________________________________
                lwip-users mailing list
                [email protected]
                http://lists.nongnu.org/mailman/listinfo/lwip-users

<<image001.jpg>>

<<image002.jpg>>

BEGIN:VCARD
VERSION:2.1
N:BERNON;Frédéric;;M.
FN:Frédéric BERNON
ORG:HYMATOM SA;Recherche et Développement
TITLE:Chef de projet informatique
TEL;WORK;VOICE:04-67-87-61-10
TEL;WORK;FAX:04-67-70-85-44
ADR;WORK;ENCODING=QUOTED-PRINTABLE:;23;Zone Industrielle=0D=0A175 rue de Massacan;VENDARGUES;;34740;FRANCE;
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:23=0D=0AZone Industrielle=0D=0A175 rue de Massacan=0D=0AVENDARGUES 34740=0D=
=0AFrance
URL;WORK:http://www.hymatom.fr
ROLE:Chef de projet informatique
EMAIL;PREF;INTERNET:[EMAIL PROTECTED]
REV:20020404T083210Z
END:VCARD
_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users

Reply via email to