lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-users] Query on NO_SYS in opts.h


From: Bilahari Akkiraju
Subject: [lwip-users] Query on NO_SYS in opts.h
Date: Mon, 21 May 2007 16:40:44 -0500

 
Hello all,

             I am trying to port lwip to ppc 83xx platform. Is the port already 
there ?. I understand that I should implement a set of functions that will give 
semaphore, mail box services to the lwip in sys_arch.c.  For a start, can I do 
away with sys_arch.c if I don't want multi threaded lwip ?

I saw in opts.h & lwipopts.h, two #define options 

#define SYS_LIGHTWEIGHT_PORT

& 

#define NO_SYS

What exactly are these, will enabling any one of them will allow me to skip 
implementing sys_arch.c during the initial phases of getting aquainted with 
lwip ?

Thanks
Bilahari

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of address@hidden
Sent: Saturday, May 19, 2007 3:07 AM
To: address@hidden
Subject: lwip-users Digest, Vol 45, Issue 16

Send lwip-users mailing list submissions to
        address@hidden

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.nongnu.org/mailman/listinfo/lwip-users
or, via email, send a message with subject or body 'help' to
        address@hidden

You can reach the person managing the list at
        address@hidden

When replying, please edit your Subject line so it is more specific than "Re: 
Contents of lwip-users digest..."


Today's Topics:

   1. Re: RE : [lwip-users] lwIP Manual (Kieran Mansley)
   2. WG: RE : [lwip-users] lwIP Manual (Goldschmidt Simon)
   3. RE : RE : [lwip-users] lwIP Manual (Fr?d?ric BERNON)


----------------------------------------------------------------------

Message: 1
Date: Fri, 18 May 2007 16:57:33 +0100
From: Kieran Mansley <address@hidden>
Subject: Re: RE : [lwip-users] lwIP Manual
To: Mailing list for lwIP users <address@hidden>
Message-ID:
        <address@hidden>
Content-Type: text/plain; charset=utf-8

On Fri, 2007-05-18 at 17:45 +0200, Frédéric BERNON wrote:
> Kieran,
> 
> Because lot of things change these last months, with lot of new 
> options, I think that will be good to define what tasks/bugs/items 
> have to be closed for the next release, and when this release will be 
> stopped, we could do the documentation.

OK.  I think in general terms for the next release I'd like to prioritise 
anything we foresee that will alter any of our APIs.  We've already made a 
number of changes recently that will break ports.  I'd rather get all the 
port-breakage we think we need into this release, and then any future releases 
would be less painful for the porters.

To this end, it would be a great help if all these issues were in the savannah 
task/patch/bug system.  If anyone knows or can think of anything that should be 
in there and is not, please add it.

I should come up with a way to mark the tasks/patches/bugs that we want to fix 
for the release, and then magic some spare time to let me do it!  

There is also little clamour from users to get the recent stuff into a stable 
form for use, so we needn't hurry a release out.  We can afford to take our 
time, fix more bugs, and get some more of the tasks done.

Leon has volunteered to help with the actual mechanics of the release as he has 
some experience of it, which would be very helpful, but we're not there yet.

There will of course need to be a couple of release candidates, together with 
testing, to make sure we don't release something unusable by others.

Kieran 





------------------------------

Message: 2
Date: Sat, 19 May 2007 10:53:56 +0200
From: "Goldschmidt Simon" <address@hidden>
Subject: WG: RE : [lwip-users] lwIP Manual
To: <address@hidden>
Message-ID:
        <address@hidden>
Content-Type: text/plain; charset="utf-8"

I'd like that idea of Frédéric and me go in: accessing sockets from multiple 
threads. I'll create a bug-tracker item for it. I don't know if it changes the 
API, but it will certainly break ports.
Other than that, there's
- the timestamp thing (big change)
- the etharp/ip_frag thing (no ports change, only internal)
- Also I'd like to put a little time into a "code-review" of the sequential 
API, I think there are still some pitfalls (should I make that a task?).
- Integrating checksum-on-copy would be a huge benefit for the next release 
(the user gets better performance at least for TCP send "for free").
- Integrating support for MACs that support on-the-fly byte-order conversion is 
considered low by me

In general, I think as there's no real time pressure, I'd like all currently 
listed tasks to go in ;-)

Simon

-----Originalnachricht-----
Von: address@hidden
An: Mailing list for lwIP users
Gesendet: 18.05.2007 17:57
Betreff: Re: RE : [lwip-users] lwIP Manual

On Fri, 2007-05-18 at 17:45 +0200, Frédéric BERNON wrote:
> Kieran,
> 
> Because lot of things change these last months, with lot of new 
> options, I think that will be good to define what tasks/bugs/items 
> have to be closed for the next release, and when this release will be 
> stopped, we could do the documentation.

OK.  I think in general terms for the next release I'd like to prioritise 
anything we foresee that will alter any of our APIs.  We've already made a 
number of changes recently that will break ports.  I'd rather get all the 
port-breakage we think we need into this release, and then any future releases 
would be less painful for the porters.

To this end, it would be a great help if all these issues were in the savannah 
task/patch/bug system.  If anyone knows or can think of anything that should be 
in there and is not, please add it.

I should come up with a way to mark the tasks/patches/bugs that we want to fix 
for the release, and then magic some spare time to let me do it!  

There is also little clamour from users to get the recent stuff into a stable 
form for use, so we needn't hurry a release out.  We can afford to take our 
time, fix more bugs, and get some more of the tasks done.

Leon has volunteered to help with the actual mechanics of the release as he has 
some experience of it, which would be very helpful, but we're not there yet.

There will of course need to be a couple of release candidates, together with 
testing, to make sure we don't release something unusable by others.

Kieran 



_______________________________________________
lwip-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://lists.gnu.org/pipermail/lwip-users/attachments/20070519/d2f7b4cf/attachment.html

------------------------------

Message: 3
Date: Sat, 19 May 2007 12:06:27 +0200
From: Fr?d?ric BERNON <address@hidden>
Subject: RE : RE : [lwip-users] lwIP Manual
To: "Mailing list for lwIP users" <address@hidden>
Message-ID: <address@hidden>
Content-Type: text/plain; charset="iso-8859-1"

Skipped content of type multipart/related-------------- next part 
-------------- A non-text attachment was scrubbed...
Name: =?iso-8859-1?Q?Fr=E9d=E9ric_BERNON=2Evcf?=
Type: text/x-vcard
Size: 589 bytes
Desc: =?iso-8859-1?Q?Fr=E9d=E9ric_BERNON=2Evcf?=
Url : 
http://lists.gnu.org/pipermail/lwip-users/attachments/20070519/1d2cc9cd/iso-8859-1QFrE9dE9ric_BERNON2Evcf.vcf

------------------------------

_______________________________________________
lwip-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-users

End of lwip-users Digest, Vol 45, Issue 16
******************************************




reply via email to

[Prev in Thread] Current Thread [Next in Thread]