OpenTCP/http_server.c
|
View:
New views
16 Messages
—
Rating Filter:
Alert me
|
 |
OpenTCP/http_server.c
by Bob Furber
::
Rate this Message:
X-SpamDetect-Info: ------------- Start ASpam results ---------------
X-SpamDetect-Info: This message may be spam. This message BODY has been altered to show you the spam information X-SpamDetect: *****: 5.100000 DodgySource=2.0, SPF Default Fail=2.5, X-Verify-SMTP present=0.6 X-SpamDetect-Info: ------------- End ASpam results ----------------- Forgive me if this is not the appropriate list for posting an OpenTCP question. But I have not succeeded in finding a more appropriate list. I am trying to port the OpenTCP stack to the ColdFire and I am running into problems uploading files (target -> client) that are too large to fit in one frame. I get a TCP_EVENT_REGENERATE event. My understanding is that a TCP_EVENT_REGENERATE event is very rare. So, in digging through the code, I notice something that does not seem quite right: So long as there is unacknowledged data (i.e., file) remaining to be sent, https_run() in the main loop loads the TCP Tx buffer with data. It does NOT CHECK if the previous frame has been acknowledged. By doing this, is there not a risk that https_run() could overfeed the client. Can anyone shed some light on this? Thanks, Bob Furber --- coldfire@... Send a post to the list. coldfire-join@... Join the list. coldfire-digest@... Join the list in digest mode. coldfire-leave@... Leave the list. |
|
|
RE: OpenTCP/http_server.c
by Seymour David-ra2693
::
Rate this Message:
Hi Bob, OpenTCP was the path we were going down to have a nice open source Ethernet stack available for ColdFire but the OpenTCP company's resource to maintain it had left (long ago now) and they pulled the open source licensing so we/FSL turn to partnering with InterNiche to create a free ColdFire TCP/IP Lite Ethernet stack with (simple) multitasking OS. Take a look at its code base as it can handle upload of file. http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=COLDFIRE_TCPIP then click the download tab. Regards, David Come to FTF 2008 June 16th through the 19th in Orlando -----Original Message----- X-SpamDetect-Info: ------------- Start ASpam results --------------- X-SpamDetect-Info: This message may be spam. This message BODY has been altered to show you the spam information X-SpamDetect: *****: 5.100000 DodgySource=2.0, SPF Default Fail=2.5, X-Verify-SMTP present=0.6 X-SpamDetect-Info: ------------- End ASpam results ----------------- Forgive me if this is not the appropriate list for posting an OpenTCP question. But I have not succeeded in finding a more appropriate list. I am trying to port the OpenTCP stack to the ColdFire and I am running into problems uploading files (target -> client) that are too large to fit in one frame. I get a TCP_EVENT_REGENERATE event. My understanding is that a TCP_EVENT_REGENERATE event is very rare. So, in digging through the code, I notice something that does not seem quite right: So long as there is unacknowledged data (i.e., file) remaining to be sent, https_run() in the main loop loads the TCP Tx buffer with data. It does NOT CHECK if the previous frame has been acknowledged. By doing this, is there not a risk that https_run() could overfeed the client. Can anyone shed some light on this? Thanks, Bob Furber --- coldfire@... Send a post to the list. coldfire-join@... Join the list. coldfire-digest@... Join the list in digest mode. coldfire-leave@... Leave the list. coldfire@... Send a post to the list. coldfire-join@... Join the list. coldfire-digest@... Join the list in digest mode. coldfire-leave@... Leave the list. |
|
|
Re: OpenTCP/http_server.c
by Mark Butcher
::
Rate this Message:
X-SpamDetect-Info: ------------- Start ASpam results ---------------
X-SpamDetect-Info: This message may be spam. This message BODY has been altered to show you the spam information
X-SpamDetect: ******: 6.300000 From3consonants=0.3, Share Market Scam=6.0
X-SpamDetect-Info: ------------- End ASpam results -----------------
Hi
I am not sure which Coldfire you are using but you can also take a look at the uTasker solution for the single-chip V2 types (the list of supported devices, with overview of their features is here: http://www.utasker.com/forum/index.php?topic=256.0) We have our own support forum at http://www.uTasker.com/forum/ - including TCP/IP stack, a unique real-time simulator and various other peripheral too. The package is fully open-source and free for non-commerical use. It includes useful web support like dynamic HTTP and content generation, as well as secure firmware updates via HTTP post or FTP. The file system allows simple extensions to the V2 devices by using cheap SPI FLASH (ST and ATMEL drivers included), enabling large web servers and complete firmware update support using even the smaller memory devices. Regards Mark www.uTasker.com
coldfire@... Send a post to the list. coldfire-join@... Join the list. coldfire-digest@... Join the list in digest mode. coldfire-leave@... Leave the list. |
|
|
Re: OpenTCP/http_server.c
by Bob Furber
::
Rate this Message:
Thanks David,
> OpenTCP was the path we were going down to have a nice open source > Ethernet stack available for ColdFire but the OpenTCP company's resource > to maintain it had left (long ago now) and they pulled the open source > licensing Yikes! For some reason I had assumed it was GPL. And, up until getting a TCP_EVENT_REGENERATE event, I was quite happy with OpenTCP. In any event, can Viola Systems Ltd. "pull the open source licensing" one handed over in the license on every source page? : *Redistribution and use in source and binary forms, with or without *modification, are permitted provided that the following conditions *are met: : > so we/FSL turn to partnering with InterNiche to create a free > ColdFire TCP/IP Lite Ethernet stack with (simple) multitasking OS. Judging by traffic on the Freescale forum, it appears that there are licensing issues with TCP/IP Lite too. I also get the sense from the forum that there were efforts to replace its multitasking OS by a "superloop", which presumably means polling. This is not unreasonable because an Ethernet chip or module typically has fairly large buffers. It appears these efforts were ended because of licensing issues. Interestingly, Freescale has contributed the HTTP support files, with no restrictions other than "For use on Freescale products only". Is this correct? > Take a look at its code base as it can handle upload of file. > > _http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=COLDFIRE_TCPIP_ > then click the download tab. Thanks. Would you know if TCP/IP Lite has a fairly large and active constituency? Thanks, Bob Furber > Regards, > > David > > David E Seymour > > Come to FTF 2008 June 16th through the 19th in Orlando > > http://www.freescale.com/ftf > > -----Original Message----- > From: coldfire-bounce@... [mailto:coldfire-bounce@...] > On Behalf Of Bob Furber > Sent: Monday, June 09, 2008 7:10 PM > To: Seymour David > Subject: [ColdFire] OpenTCP/http_server.c > > X-SpamDetect-Info: ------------- Start ASpam results --------------- > > X-SpamDetect-Info: This message may be spam. This message BODY has been > altered to show you the spam information > > X-SpamDetect: *****: 5.100000 DodgySource=2.0, SPF Default Fail=2.5, > X-Verify-SMTP present=0.6 > > X-SpamDetect-Info: ------------- End ASpam results ----------------- > > Forgive me if this is not the appropriate list for posting an OpenTCP > > question. But I have not succeeded in finding a more appropriate list. > > I am trying to port the OpenTCP stack to the ColdFire and I am running > > into problems uploading files (target -> client) that are too large to > > fit in one frame. I get a TCP_EVENT_REGENERATE event. > > My understanding is that a TCP_EVENT_REGENERATE event is very rare. So, > > in digging through the code, I notice something that does not seem quite > > right: So long as there is unacknowledged data (i.e., file) remaining to > > be sent, https_run() in the main loop loads the TCP Tx buffer with data. > > It does NOT CHECK if the previous frame has been acknowledged. By doing > > this, is there not a risk that https_run() could overfeed the client. > > Can anyone shed some light on this? > > Thanks, > > Bob Furber > > --- > > coldfire@... Send a post to the list. > > coldfire-join@... Join the list. > > coldfire-digest@... Join the list in digest mode. > > coldfire-leave@... Leave the list. > > coldfire@... Send a post to the list. > coldfire-join@... Join the list. coldfire-digest@... > Join the list in digest mode. coldfire-leave@... Leave the list. --- coldfire@... Send a post to the list. coldfire-join@... Join the list. coldfire-digest@... Join the list in digest mode. coldfire-leave@... Leave the list. |
|
|
Re: OpenTCP/http_server.c
by Bob Furber
::
Rate this Message:
X-SpamDetect-Info: ------------- Start ASpam results ---------------
X-SpamDetect-Info: This message may be spam. This message BODY has been altered to show you the spam information X-SpamDetect: *****: 5.100000 DodgySource=2.0, SPF Default Fail=2.5, X-Verify-SMTP present=0.6 X-SpamDetect-Info: ------------- End ASpam results ----------------- Hi Mark, > I am not sure which Coldfire you are using but you can also take a look > at the uTasker solution for the single-chip V2 types (the list of > supported devices, with overview of their features is here: > http://www.utasker.com/forum/index.php?topic=256.0) > We have our own support forum at http://www.uTasker.com/forum/ - > including TCP/IP stack, a unique real-time simulator and various other > peripheral too. The package is fully open-source and free for > non-commerical use. It includes useful web support like dynamic HTTP and > content generation, as well as secure firmware updates via HTTP post or > FTP. The file system allows simple extensions to the V2 devices by using > cheap SPI FLASH (ST and ATMEL drivers included), enabling large web > servers and complete firmware update support using even the smaller > memory devices. uTasker looks pretty good ..except for the license (and steep learning curve). You see, we like to provide demo programs for our MCF5282 WildFire/WildFireMod development kits ..which we sell. So we would not be able to comply with the "non-commercial use" restriction. OpenTCP seemed ok until we decided to build better demo programs for it and marry it to a FatFS to serve web pages from an SD card. Then we ran into rather sluggish performance and TCP_EVENT_REGENERATE events ...possibly triggered by delays (and not force-feeding as I has speculated earlier). Thanks, Bob > Regards > > Mark > > www.uTasker.com > > >> Hi Bob, >> >> OpenTCP was the path we were going down to have a nice open source >> Ethernet stack available for ColdFire but the OpenTCP company's >> resource to maintain it had left (long ago now) and they pulled the >> open source licensing so we/FSL turn to partnering with InterNiche to >> create a free ColdFire TCP/IP Lite Ethernet stack with (simple) >> multitasking OS. >> >> Take a look at its code base as it can handle upload of file. >> >> _http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=COLDFIRE_TCPIP_ >> then click the download tab. >> >> Regards, >> >> David >> >> David E Seymour >> >> Come to FTF 2008 June 16th through the 19th in Orlando >> >> http://www.freescale.com/ftf >> >> -----Original Message----- >> From: coldfire-bounce@... >> [mailto:coldfire-bounce@...] On Behalf Of Bob Furber >> Sent: Monday, June 09, 2008 7:10 PM >> To: Seymour David >> Subject: [ColdFire] OpenTCP/http_server.c >> >> X-SpamDetect-Info: ------------- Start ASpam results --------------- >> >> X-SpamDetect-Info: This message may be spam. This message BODY has >> been altered to show you the spam information >> >> X-SpamDetect: *****: 5.100000 DodgySource=2.0, SPF Default Fail=2.5, >> X-Verify-SMTP present=0.6 >> >> X-SpamDetect-Info: ------------- End ASpam results ----------------- >> >> Forgive me if this is not the appropriate list for posting an OpenTCP >> >> question. But I have not succeeded in finding a more appropriate list. >> >> I am trying to port the OpenTCP stack to the ColdFire and I am running >> >> into problems uploading files (target -> client) that are too large to >> >> fit in one frame. I get a TCP_EVENT_REGENERATE event. >> >> My understanding is that a TCP_EVENT_REGENERATE event is very rare. So, >> >> in digging through the code, I notice something that does not seem quite >> >> right: So long as there is unacknowledged data (i.e., file) remaining to >> >> be sent, https_run() in the main loop loads the TCP Tx buffer with data. >> >> It does NOT CHECK if the previous frame has been acknowledged. By doing >> >> this, is there not a risk that https_run() could overfeed the client. >> >> Can anyone shed some light on this? >> >> Thanks, >> >> Bob Furber >> > > coldfire@... Send a post to the list. > coldfire-join@... Join the list. coldfire-digest@... > Join the list in digest mode. coldfire-leave@... Leave the list. --- coldfire@... Send a post to the list. coldfire-join@... Join the list. coldfire-digest@... Join the list in digest mode. coldfire-leave@... Leave the list. |
|
|
RE: OpenTCP/http_server.c
by Seymour David-ra2693
::
Rate this Message:
Hi Bob,
FSL had freely licensed the OpenTCP for NE64 and MCF5282 but as I mentioned before the resource at Viola left and the company decided to pull it. So FSL wanted an open source approach. The ColdFire TCP/IP is freely license for use with FSL processors. It provides a nice step to fully supported stack/OS from InterNiche should customers choose that route. Yes, it is being actively used by many and will continue to be. I think it is the up-sell area that FSL cannot generate code and post but customer can add whatever they want for their own use. I'll triple check that answer and reply if I'm wrong. Regards, David David E Seymour Come to FTF 2008 June 16th through the 19th in Orlando http://www.freescale.com/ftf -----Original Message----- From: coldfire-bounce@... [mailto:coldfire-bounce@...] On Behalf Of Bob Furber Sent: Tuesday, June 10, 2008 1:39 PM To: Seymour David Subject: Re: [ColdFire] OpenTCP/http_server.c Thanks David, > OpenTCP was the path we were going down to have a nice open source > Ethernet stack available for ColdFire but the OpenTCP company's resource > to maintain it had left (long ago now) and they pulled the open source > licensing Yikes! For some reason I had assumed it was GPL. And, up until getting a TCP_EVENT_REGENERATE event, I was quite happy with OpenTCP. In any event, can Viola Systems Ltd. "pull the open source licensing" one handed over in the license on every source page? : *Redistribution and use in source and binary forms, with or without *modification, are permitted provided that the following conditions *are met: : > so we/FSL turn to partnering with InterNiche to create a free > ColdFire TCP/IP Lite Ethernet stack with (simple) multitasking OS. Judging by traffic on the Freescale forum, it appears that there are licensing issues with TCP/IP Lite too. I also get the sense from the forum that there were efforts to replace its multitasking OS by a "superloop", which presumably means polling. This is not unreasonable because an Ethernet chip or module typically has fairly large buffers. It appears these efforts were ended because of licensing issues. Interestingly, Freescale has contributed the HTTP support files, with no restrictions other than "For use on Freescale products only". Is this correct? > Take a look at its code base as it can handle upload of file. > > _http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=COLDFIRE _TCPIP_ > then click the download tab. Thanks. Would you know if TCP/IP Lite has a fairly large and active constituency? Thanks, Bob Furber > Regards, > > David > > David E Seymour > > Come to FTF 2008 June 16th through the 19th in Orlando > > http://www.freescale.com/ftf > > -----Original Message----- > From: coldfire-bounce@... > On Behalf Of Bob Furber > Sent: Monday, June 09, 2008 7:10 PM > To: Seymour David > Subject: [ColdFire] OpenTCP/http_server.c > > X-SpamDetect-Info: ------------- Start ASpam results --------------- > > X-SpamDetect-Info: This message may be spam. This message BODY has been > altered to show you the spam information > > X-SpamDetect: *****: 5.100000 DodgySource=2.0, SPF Default Fail=2.5, > X-Verify-SMTP present=0.6 > > X-SpamDetect-Info: ------------- End ASpam results ----------------- > > Forgive me if this is not the appropriate list for posting an OpenTCP > > question. But I have not succeeded in finding a more appropriate list. > > I am trying to port the OpenTCP stack to the ColdFire and I am running > > into problems uploading files (target -> client) that are too large to > > fit in one frame. I get a TCP_EVENT_REGENERATE event. > > My understanding is that a TCP_EVENT_REGENERATE event is very rare. > > in digging through the code, I notice something that does not seem quite > > right: So long as there is unacknowledged data (i.e., file) remaining to > > be sent, https_run() in the main loop loads the TCP Tx buffer with data. > > It does NOT CHECK if the previous frame has been acknowledged. By doing > > this, is there not a risk that https_run() could overfeed the client. > > Can anyone shed some light on this? > > Thanks, > > Bob Furber > > --- > > coldfire@... Send a post to the list. > > coldfire-join@... Join the list. > > coldfire-digest@... Join the list in digest mode. > > coldfire-leave@... Leave the list. > > coldfire@... Send a post to the list. > coldfire-join@... Join the list. coldfire-digest@... > Join the list in digest mode. coldfire-leave@... Leave the list. --- coldfire@... Send a post to the list. coldfire-join@... Join the list. coldfire-digest@... Join the list in digest mode. coldfire-leave@... Leave the list. --- coldfire@... Send a post to the list. coldfire-join@... Join the list. coldfire-digest@... Join the list in digest mode. coldfire-leave@... Leave the list. |
|
|
Re: OpenTCP/http_server.c
by David Brown-4
::
Rate this Message:
Mark Butcher wrote:
> X-SpamDetect-Info: ------------- Start ASpam results --------------- > X-SpamDetect-Info: This message may be spam. This message BODY has been > altered to show you the spam information X-SpamDetect: ******: 6.300000 > From3consonants=0.3, Share Market Scam=6.0 X-SpamDetect-Info: > ------------- End ASpam results ----------------- Hi > > I am not sure which Coldfire you are using but you can also take a look > at the uTasker solution for the single-chip V2 types (the list of > supported devices, with overview of their features is here: > http://www.utasker.com/forum/index.php?topic=256.0) > We have our own support forum at http://www.uTasker.com/forum/ - > including TCP/IP stack, a unique real-time simulator and various other > peripheral too. The package is fully open-source and free for > non-commerical use. It includes useful web support like dynamic HTTP and > content generation, as well as secure firmware updates via HTTP post or > FTP. The file system allows simple extensions to the V2 devices by using > cheap SPI FLASH (ST and ATMEL drivers included), enabling large web > servers and complete firmware update support using even the smaller > memory devices. > > Regards > > Mark > > www.uTasker.com > > I'm sure your stack is good software, and good value for money - but unless I am missing something major, it is completely wrong to describe it as "open source". The term "open source" is a trademarked term with a specific definition, precisely to stop people calling their software "open source" and confusing users. http://www.opensource.org/docs/definition.php It is perfectly possible to provide software stacks as true open source, and make a business out of it (such as providing paid-for alternative licenses, or selling support contracts). It is also perfectly possible to make a business selling non-open-source software. But it is not reasonable to sell or even give away code with proprietary and restrictive licenses (no matter how reasonable and fair the license) and mislabel it as "open source". Since your website makes no claims that the software is open source, I assume this was just a typo in your post. I'm not trying to say there is anything wrong with your software or your license - it's just that for some users, the essential freedoms involved in true open source and/or free (as in speech, not as in beer) licenses are important. mvh., David --- coldfire@... Send a post to the list. coldfire-join@... Join the list. coldfire-digest@... Join the list in digest mode. coldfire-leave@... Leave the list. |
|
|
Re: OpenTCP/http_server.c
by David Brown-4
::
Rate this Message:
Seymour David wrote:
> Hi Bob, > FSL had freely licensed the OpenTCP for NE64 and MCF5282 but as I > mentioned before the resource at Viola left and the company decided to > pull it. So FSL wanted an open source approach. The ColdFire TCP/IP is > freely license for use with FSL processors. It provides a nice step to > fully supported stack/OS from InterNiche should customers choose that > route. > Yes, it is being actively used by many and will continue to be. > I think it is the up-sell area that FSL cannot generate code and post > but customer can add whatever they want for their own use. I'll triple > check that answer and reply if I'm wrong. > Regards, > David > > David E Seymour Could you be more specific about the license? I couldn't see license information on the website, and it's far from clear if by "freely licensed" you mean "free speech" or just "free beer". mvh., David --- coldfire@... Send a post to the list. coldfire-join@... Join the list. coldfire-digest@... Join the list in digest mode. coldfire-leave@... Leave the list. |
|
|
RE: OpenTCP/http_server.c
by Seymour David-ra2693
::
Rate this Message:
Put me down for a free beer please ;-)
The License file is in the source code. I got clarity from the factory: "FSL has the right to modify the stack. We just can't let customers repost the code because the license we have with interniche doesn't allow the "customer" to have redistribute capability." Here is the license for your view/reading pleasure. IMPORTANT. Read the following Freescale Semiconductor Software License Agreement completely. You may then utilize these files. FREESCALE SEMICONDUCTOR SOFTWARE LICENSE AGREEMENT This is a legal agreement between you (either as an individual or as an authorized representative of your employer) and Freescale Semiconductor, Inc. ("Freescale"). It concerns your rights to use this file and any accompanying written materials (the "Software"). In consideration for Freescale allowing you to access the Software, you are agreeing to be bound by the terms of this Agreement. If you do not agree to all of the terms of this Agreement, do not download the Software. If you change your mind later, stop using the Software and delete all copies of the Software in your possession or control. Any copies of the Software that you have already distributed, where permitted, and do not destroy will continue to be governed by this Agreement. Your prior use will also continue to be governed by this Agreement. LICENSE GRANT. Freescale grants to you, free of charge, the non-exclusive, non- transferable right (1) to use the Software, (2) to reproduce the Software, (3) to prepare derivative works of the Software, (4) to distribute the Software and derivative works thereof in source (human-readable) form and object (machine readable) form, and (5) to sublicense to others the right to use the distributed Software. If you violate any of the terms or restrictions of this Agreement, Freescale may immediately terminate this Agreement, and require that you stop using and delete all copies of the Software in your possession or control. COPYRIGHT. The Software is licensed to you, not sold. Freescale owns the Software, and United States copyright laws and international treaty provisions protect the Software. Therefore, you must treat the Software like any other copyrighted material (e.g. a book or musical recording). You may not use or copy the Software for any other purpose than what is described in this Agreement. Except as expressly provided herein, Freescale does not grant to you any express or implied rights under any Freescale or third-party patents, copyrights, trademarks, or trade secrets. Additionally, you must reproduce and apply any copyright or other proprietary rights notices included on or embedded in the Software to any copies or derivative works made thereof, in whole or in part, if any. SUPPORT. Freescale is NOT obligated to provide any support, upgrades or new releases of the Software. If you wish, you may contact Freescale and report problems and provide suggestions regarding the Software. Freescale has no obligation whatsoever to respond in any way to such a problem report or suggestion. Freescale may make changes to the Software at any time, without any obligation to notify or provide updated versions of the Software to you. NO WARRANTY. TO THE MAXIMUM EXTENT PERMITTED BY LAW, FREESCALE EXPRESSLY DISCLAIMS ANY WARRANTY FOR THE SOFTWARE. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. YOU ASSUME THE ENTIRE RISK ARISING OUT OF THE USE OR PERFORMANCE OF THE SOFTWARE, OR ANY SYSTEMS YOU DESIGN USING THE SOFTWARE (IF ANY). NOTHING IN THIS AGREEMENT MAY BE CONSTRUED AS A WARRANTY OR REPRESENTATION BY FREESCALE THAT THE SOFTWARE OR ANY DERIVATIVE WORK DEVELOPED WITH OR INCORPORATING THE SOFTWARE WILL BE FREE FROM INFRINGEMENT OF THE INTELLECTUAL PROPERTY RIGHTS OF THIRD PARTIES. INDEMNITY. You agree to fully defend and indemnify Freescale from any and all claims, liabilities, and costs (including reasonable attorney's fees) related to (1) your use (including your sublicensee's use, if permitted) of the Software or (2) your violation of the terms and conditions of this Agreement. LIMITATION OF LIABILITY. IN NO EVENT WILL FREESCALE BE LIABLE, WHETHER IN CONTRACT, TORT, OR OTHERWISE, FOR ANY INCIDENTAL, SPECIAL, INDIRECT, CONSEQUENTIAL OR PUNITIVE DAMAGES, INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR ANY LOSS OF USE, LOSS OF TIME, INCONVENIENCE, COMMERCIAL LOSS, OR LOST PROFITS, SAVINGS, OR REVENUES TO THE FULL EXTENT SUCH MAY BE DISCLAIMED BY LAW. COMPLIANCE WITH LAWS; EXPORT RESTRICTIONS. You must use the Software in accordance with all applicable U.S. laws, regulations and statutes. You agree that neither you nor your licensees (if any) intend to or will, directly or indirectly, export or transmit the Software to any country in violation of U.S. export restrictions. GOVERNMENT USE. Use of the Software and any corresponding documentation, if any, is provided with RESTRICTED RIGHTS. Use, duplication or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(l) and (2) of the Commercial Computer Software--Restricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer is Freescale Semiconductor, Inc., 6501 William Cannon Drive West, Austin, TX, 78735. HIGH RISK ACTIVITIES. You acknowledge that the Software is not fault tolerant and is not designed, manufactured or intended by Freescale for incorporation into products intended for use or resale in on-line control equipment in hazardous, dangerous to life or potentially life-threatening environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life support machines or weapons systems, in which the failure of products could lead directly to death, personal injury or severe physical or environmental damage ("High Risk Activities"). You specifically represent and warrant that you will not use the Software or any derivative work of the Software for High Risk Activities. CHOICE OF LAW; VENUE; LIMITATIONS. You agree that the statutes and laws of the United States and the State of Texas, USA, without regard to conflicts of laws principles, will apply to all matters relating to this Agreement or the Software, and you agree that any litigation will be subject to the exclusive jurisdiction of the state or federal courts in Texas, USA. You agree that regardless of any statute or law to the contrary, any claim or cause of action arising out of or related to this Agreement or the Software must be filed within one (1) year after such claim or cause of action arose or be forever barred. PRODUCT LABELING. You are not authorized to use any Freescale trademarks, brand names, or logos. ENTIRE AGREEMENT. This Agreement constitutes the entire agreement between you and Freescale regarding the subject matter of this Agreement, and supersedes all prior communications, negotiations, understandings, agreements or representations, either written or oral, if any. This Agreement may only be amended in written form, executed by you and Freescale. SEVERABILITY. If any provision of this Agreement is held for any reason to be invalid or unenforceable, then the remaining provisions of this Agreement will be unimpaired and, unless a modification or replacement of the invalid or unenforceable provision is further held to deprive you or Freescale of a material benefit, in which case the Agreement will immediately terminate, the invalid or unenforceable provision will be replaced with a provision that is valid and enforceable and that comes closest to the intention underlying the invalid or unenforceable provision. NO WAIVER. The waiver by Freescale of any breach of any provision of this Agreement will not operate or be construed as a waiver of any other or a subsequent breach of the same or a different provision. If you read it all then I owe you a free beer! Regards, David David E Seymour Come to FTF 2008 June 16th through the 19th in Orlando http://www.freescale.com/ftf -----Original Message----- From: coldfire-bounce@... [mailto:coldfire-bounce@...] On Behalf Of David Brown Sent: Tuesday, June 10, 2008 3:41 PM To: Seymour David Subject: Re: [ColdFire] OpenTCP/http_server.c Seymour David wrote: > Hi Bob, > FSL had freely licensed the OpenTCP for NE64 and MCF5282 but as I > mentioned before the resource at Viola left and the company decided to > pull it. So FSL wanted an open source approach. The ColdFire TCP/IP is > freely license for use with FSL processors. It provides a nice step to > fully supported stack/OS from InterNiche should customers choose that > route. > Yes, it is being actively used by many and will continue to be. > I think it is the up-sell area that FSL cannot generate code and post > but customer can add whatever they want for their own use. I'll triple > check that answer and reply if I'm wrong. > Regards, > David > > David E Seymour Could you be more specific about the license? I couldn't see license information on the website, and it's far from clear if by "freely licensed" you mean "free speech" or just "free beer". mvh., David --- coldfire@... Send a post to the list. coldfire-join@... Join the list. coldfire-digest@... Join the list in digest mode. coldfire-leave@... Leave the list. --- coldfire@... Send a post to the list. coldfire-join@... Join the list. coldfire-digest@... Join the list in digest mode. coldfire-leave@... Leave the list. |
|
|
Re: OpenTCP/http_server.c
by David Brown-4
::
Rate this Message:
Seymour David wrote:
> Put me down for a free beer please ;-) > The License file is in the source code. > I got clarity from the factory: > "FSL has the right to modify the stack. We just can't let customers > repost the code because the license we have with interniche doesn't > allow the "customer" to have redistribute capability." I'm a little confused - the "license grant" paragraph sections 4 and 5 imply that you *can* repost and distribute the code, along with any changes you make. I'm not a lawyer, of course, so I could be getting this wrong. mvh., David > > LICENSE GRANT. Freescale grants to you, free of charge, the > non-exclusive, non- > transferable right (1) to use the Software, (2) to reproduce the > Software, (3) to prepare > derivative works of the Software, (4) to distribute the Software and > derivative works > thereof in source (human-readable) form and object (machine readable) > form, and (5) to > sublicense to others the right to use the distributed Software. If you > violate any of the > terms or restrictions of this Agreement, Freescale may immediately > terminate this > Agreement, and require that you stop using and delete all copies of the > Software in your > possession or control. > --- coldfire@... Send a post to the list. coldfire-join@... Join the list. coldfire-digest@... Join the list in digest mode. coldfire-leave@... Leave the list. |
|
|
RE: OpenTCP/http_server.c
by Seymour David-ra2693
::
Rate this Message:
You weren't supposed to read it ;-)
I'll ask for additional clarification. I too am not a fan of reading legal spegal. Regards, David David E Seymour Come to FTF 2008 June 16th through the 19th in Orlando http://www.freescale.com/ftf -----Original Message----- From: coldfire-bounce@... [mailto:coldfire-bounce@...] On Behalf Of David Brown Sent: Tuesday, June 10, 2008 4:58 PM To: Seymour David Subject: Re: [ColdFire] OpenTCP/http_server.c Seymour David wrote: > Put me down for a free beer please ;-) > The License file is in the source code. > I got clarity from the factory: > "FSL has the right to modify the stack. We just can't let customers > repost the code because the license we have with interniche doesn't > allow the "customer" to have redistribute capability." I'm a little confused - the "license grant" paragraph sections 4 and 5 imply that you *can* repost and distribute the code, along with any changes you make. I'm not a lawyer, of course, so I could be getting this wrong. mvh., David > > LICENSE GRANT. Freescale grants to you, free of charge, the > non-exclusive, non- > transferable right (1) to use the Software, (2) to reproduce the > Software, (3) to prepare > derivative works of the Software, (4) to distribute the Software and > derivative works > thereof in source (human-readable) form and object (machine readable) > form, and (5) to > sublicense to others the right to use the distributed Software. If you > violate any of the > terms or restrictions of this Agreement, Freescale may immediately > terminate this > Agreement, and require that you stop using and delete all copies of > Software in your > possession or control. > --- coldfire@... Send a post to the list. coldfire-join@... Join the list. coldfire-digest@... Join the list in digest mode. coldfire-leave@... Leave the list. --- coldfire@... Send a post to the list. coldfire-join@... Join the list. coldfire-digest@... Join the list in digest mode. coldfire-leave@... Leave the list. |
|
|
Re: OpenTCP/http_server.c
by Mark Butcher
::
Rate this Message:
Hi David
Please read - 'all source code is distributed and may be modified in any way by the user' - I was not aware that the words "open source" are trademarked (I was told by many that it was suitable to describe the fact, although none of these were lawyers...;-) ) but I will avoid using these two world together in the future so that I don't have to study any legal details. We don't want to claim any agreements as defined by the Open Source Initiative, that is why we don't state this - we do give free code and free support to many individuals and educational establishments: I personally spend on average several hours a day giving free help (Email and sometimes telephone). This helps us to understand the areas the project is used in any also to add the features most requested, as well as solving any problems found (the more users giving feedback the better the code...), which benefits all users, including the commercial users, who do pay a contribution to use the code base in their 'for profit' products as well as receiving preferrential support for up to 1 year. The uTasker has its own license which states that the code should not be passed on to others without them first having agreed to the licensing terms. The terms are mainly to ensure that we don't get sued by any user who finds a bug in the code - liability clause - and things like, it may not be used for development for "Products of war", land mines etc. - this is in fact a requisit of Freescale since we have to ensure this use is restricted according to our Freescale Allicance Partner agreement! To summarise: if there are legal restrictions on using the words "Open Source" to describe the form of the software I withdraw that and request everyone to disgard any references to these words in preference to the statement above. I hope that the this doesn't detract from the fact that we do freely give several years of development work to anyone interested in 'joining' the community. Regards Mark hhtp://www.uTasker.com David Brown schrieb: > > > I'm sure your stack is good software, and good value for money - but > unless I am missing something major, it is completely wrong to > describe it as "open source". The term "open source" is a trademarked > term with a specific definition, precisely to stop people calling > their software "open source" and confusing users. > > http://www.opensource.org/docs/definition.php > > It is perfectly possible to provide software stacks as true open > source, and make a business out of it (such as providing paid-for > alternative licenses, or selling support contracts). It is also > perfectly possible to make a business selling non-open-source > software. But it is not reasonable to sell or even give away code > with proprietary and restrictive licenses (no matter how reasonable > and fair the license) and mislabel it as "open source". > > Since your website makes no claims that the software is open source, I > assume this was just a typo in your post. > > I'm not trying to say there is anything wrong with your software or > your license - it's just that for some users, the essential freedoms > involved in true open source and/or free (as in speech, not as in > beer) licenses are important. > > mvh., > > David > --- > coldfire@... Send a post to the list. > coldfire-join@... Join the list. > coldfire-digest@... Join the list in digest mode. > coldfire-leave@... Leave the list. > > --- coldfire@... Send a post to the list. coldfire-join@... Join the list. coldfire-digest@... Join the list in digest mode. coldfire-leave@... Leave the list. |
|
|
|
|
|
Re: OpenTCP/http_server.c
by David Brown-4
::
Rate this Message:
Mark Butcher wrote:
> Hi David > > Please read - 'all source code is distributed and may be modified in any > way by the user' - I was not aware that the words "open source" are > trademarked (I was told by many that it was suitable to describe the > fact, although none of these were lawyers...;-) ) but I will avoid using > these two world together in the future so that I don't have to study any Don't take my word for the "trademarked" point - after a little reading, it seems that the attempts to trademark "open source" failed as the term was too general. http://en.wikipedia.org/wiki/Open-source_software It sounds from your mail here that you have a very good product, and a good way of licensing the software, and working with customers (both paying and non-paying). My only problem was that the term "open source", and "open" in general, has a specific meaning - when it is used incorrectly, it confuses people and dilutes the meaning of the term. In this case it was a simple misunderstanding - you come very close to the open source development model, but are missing a few vital steps (for good reasons - open source is certainly not the best model for all software). There are cases of people misusing the terms intentionally to mislead people (the so-called "Open Office XML" pseudo-standard is a well-known example) - obviously that's not the case here. What makes the difference with "open source" is that people can take the source code, modify it if they want, and distribute the code and their changes to other people. To be "open source", there should not be any requirement that this distribution needs to involve the copyright owner, and that there are no restrictions on the use of the code (just as free speech must allow the freedom to make, for example, racist remarks - so open software cannot be censored in its use). Of course, this would conflict with your desire to maintain tighter control of the code (for quality control, to restrict usage in certain markets, to control the ownership and copyright of the code, and of course to protect your commercial licenses that pay for your daily bread). If you are interested, have a look at http://www.freertos.org/ . They make three RTOS's for embedded systems. They make "FreeRTOS", which is open source (and requires that users provide a link to the website in their documentation, and that they publish any changes made to the FreeRTOS code they distribute - requirements that are common for open source software, but not required). Secondly, they sell commercial licenses for "OpenRTOS", which is virtually the same code as "FreeRTOS" but with a different license with no user requirements). Thirdly, they have "SafeRTOS", which is a subset of "OpenRTOS" with much more testing, certifications, and warranties. I'm not suggesting that this is the right model for you - just that it might be interesting to look at for comparison. Anyway, thanks for taking the time clarifying your licensing - hopefully it will also be of use to others on this list, or people searching the archives in the future (that's the eternal hope of public mailing lists like this). Best regards, David > legal details. We don't want to claim any agreements as defined by the > Open Source Initiative, that is why we don't state this - we do give > free code and free support to many individuals and educational > establishments: I personally spend on average several hours a day giving > free help (Email and sometimes telephone). This helps us to understand > the areas the project is used in any also to add the features most > requested, as well as solving any problems found (the more users giving > feedback the better the code...), which benefits all users, including > the commercial users, who do pay a contribution to use the code base in > their 'for profit' products as well as receiving preferrential support > for up to 1 year. > > The uTasker has its own license which states that the code should not be > passed on to others without them first having agreed to the licensing > terms. The terms are mainly to ensure that we don't get sued by any user > who finds a bug in the code - liability clause - and things like, it may > not be used for development for "Products of war", land mines etc. - > this is in fact a requisit of Freescale since we have to ensure this use > is restricted according to our Freescale Allicance Partner agreement! > > To summarise: if there are legal restrictions on using the words "Open > Source" to describe the form of the software I withdraw that and request > everyone to disgard any references to these words in preference to the > statement above. I hope that the this doesn't detract from the fact that > we do freely give several years of development work to anyone interested > in 'joining' the community. > > Regards > > Mark > > hhtp://www.uTasker.com > > > David Brown schrieb: >> >> >> I'm sure your stack is good software, and good value for money - but >> unless I am missing something major, it is completely wrong to >> describe it as "open source". The term "open source" is a trademarked >> term with a specific definition, precisely to stop people calling >> their software "open source" and confusing users. >> >> http://www.opensource.org/docs/definition.php >> >> It is perfectly possible to provide software stacks as true open >> source, and make a business out of it (such as providing paid-for >> alternative licenses, or selling support contracts). It is also >> perfectly possible to make a business selling non-open-source >> software. But it is not reasonable to sell or even give away code >> with proprietary and restrictive licenses (no matter how reasonable >> and fair the license) and mislabel it as "open source". >> >> Since your website makes no claims that the software is open source, I >> assume this was just a typo in your post. >> >> I'm not trying to say there is anything wrong with your software or >> your license - it's just that for some users, the essential freedoms >> involved in true open source and/or free (as in speech, not as in >> beer) licenses are important. >> >> mvh., >> >> David --- coldfire@... Send a post to the list. coldfire-join@... Join the list. coldfire-digest@... Join the list in digest mode. coldfire-leave@... Leave the list. |
|
|
Re: OpenTCP/http_server.c
by Bob Furber
::
Rate this Message:
Seymour David wrote:
> Put me down for a free beer please ;-) > : Interestingly, my spam filter classified this email as spam. I does "not do" legalese ;o) > I got clarity from the factory: Clarity?? You must be kidding. Sorry, but I side with my spam filter. Not being a lawyer, this license seems to be a bale of contradictions. > .. We just can't let customers > repost the code because the license we have with interniche doesn't > allow the "customer" to have redistribute capability." Clause (4) allows [re] distribution > FREESCALE SEMICONDUCTOR SOFTWARE LICENSE AGREEMENT > : > LICENSE GRANT. Freescale grants to you, free of charge, the > non-exclusive, non-transferable right > : > (4) to distribute the Software and derivative works thereof in > source (human-readable) form and object (machine readable) form, > and (5) to sublicense to others the right to use the distributed > Software. Is "non-transferable right" to "distribute" and "sublicense" not an oxymoron? > : > COPYRIGHT. The Software is licensed to you, not sold. Freescale owns > the Software, > : > Therefore, you must treat the Software like any other copyrighted > material (e.g. a book or musical recording). Yet, (2) allows me to reproduce, (3) to prepare derivative works (a.k.a. modify), (4), to distribute and (5) to sublicense. I fail to see the book or music analogy. > You may not use or copy the Software for any other > purpose than what is described in this Agreement. Yet clauses (1) to (5) give so much latitude that it is not at all clear what one is NOT allowed to do with the s/w. > : > copyrights, trademarks, or trade secrets. Additionally, you must > reproduce and apply any copyright or other proprietary rights notices > included on or embedded in the Software to any copies or derivative works > made thereof, in whole or in part, if any. When I distribute (clause 4) with the license plastered over all the code, am I not transferring the license? Dreaming in Techicolor, why can Freescale not have a simple, clear GPL like license, FPL, which would be like GPL, but only to be used on Freescale products? Forgive my frustration with this license. The word "obfuscation" comes to mind, rather than clarity. Bob Furber > SUPPORT. Freescale is NOT obligated to provide any support, upgrades or > new > releases of the Software. If you wish, you may contact Freescale and > report problems and > provide suggestions regarding the Software. Freescale has no obligation > whatsoever to > respond in any way to such a problem report or suggestion. Freescale may > make changes > to the Software at any time, without any obligation to notify or provide > updated versions > of the Software to you. > > NO WARRANTY. TO THE MAXIMUM EXTENT PERMITTED BY LAW, > FREESCALE EXPRESSLY DISCLAIMS ANY WARRANTY FOR THE SOFTWARE. > THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, > EITHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THE > IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A > PARTICULAR PURPOSE, OR NON-INFRINGEMENT. YOU ASSUME THE > ENTIRE RISK ARISING OUT OF THE USE OR PERFORMANCE OF THE > SOFTWARE, OR ANY SYSTEMS YOU DESIGN USING THE SOFTWARE (IF > ANY). NOTHING IN THIS AGREEMENT MAY BE CONSTRUED AS A > WARRANTY OR REPRESENTATION BY FREESCALE THAT THE SOFTWARE > OR ANY DERIVATIVE WORK DEVELOPED WITH OR INCORPORATING THE > SOFTWARE WILL BE FREE FROM INFRINGEMENT OF THE INTELLECTUAL > PROPERTY RIGHTS OF THIRD PARTIES. > > INDEMNITY. You agree to fully defend and indemnify Freescale from any > and all > claims, liabilities, and costs (including reasonable attorney's fees) > related to (1) your use > (including your sublicensee's use, if permitted) of the Software or (2) > your violation of > the terms and conditions of this Agreement. > > LIMITATION OF LIABILITY. IN NO EVENT WILL FREESCALE BE LIABLE, > WHETHER IN CONTRACT, TORT, OR OTHERWISE, FOR ANY INCIDENTAL, > SPECIAL, INDIRECT, CONSEQUENTIAL OR PUNITIVE DAMAGES, > INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR ANY LOSS OF USE, LOSS > OF TIME, INCONVENIENCE, COMMERCIAL LOSS, OR LOST PROFITS, > SAVINGS, OR REVENUES TO THE FULL EXTENT SUCH MAY BE DISCLAIMED > BY LAW. > > COMPLIANCE WITH LAWS; EXPORT RESTRICTIONS. You must use the > Software in accordance with all applicable U.S. laws, regulations and > statutes. You agree > that neither you nor your licensees (if any) intend to or will, directly > or indirectly, export > or transmit the Software to any country in violation of U.S. export > restrictions. > > GOVERNMENT USE. Use of the Software and any corresponding > documentation, if > any, is provided with RESTRICTED RIGHTS. Use, duplication or disclosure > by the > Government is subject to restrictions as set forth in subparagraph > (c)(1)(ii) of The Rights > in Technical Data and Computer Software clause at DFARS 252.227-7013 or > subparagraphs (c)(l) and (2) of the Commercial Computer > Software--Restricted Rights at > 48 CFR 52.227-19, as applicable. Manufacturer is Freescale > Semiconductor, Inc., 6501 > William Cannon Drive West, Austin, TX, 78735. > > HIGH RISK ACTIVITIES. You acknowledge that the Software is not fault > tolerant > and is not designed, manufactured or intended by Freescale for > incorporation into > products intended for use or resale in on-line control equipment in > hazardous, dangerous > to life or potentially life-threatening environments requiring fail-safe > performance, such > as in the operation of nuclear facilities, aircraft navigation or > communication systems, air > traffic control, direct life support machines or weapons systems, in > which the failure of > products could lead directly to death, personal injury or severe > physical or environmental > damage ("High Risk Activities"). You specifically represent and warrant > that you will not > use the Software or any derivative work of the Software for High Risk > Activities. > > CHOICE OF LAW; VENUE; LIMITATIONS. You agree that the statutes and laws > > of the United States and the State of Texas, USA, without regard to > conflicts of laws > principles, will apply to all matters relating to this Agreement or the > Software, and you > agree that any litigation will be subject to the exclusive jurisdiction > of the state or federal > courts in Texas, USA. You agree that regardless of any statute or law to > the contrary, any > claim or cause of action arising out of or related to this Agreement or > the Software must > be filed within one (1) year after such claim or cause of action arose > or be forever barred. > > PRODUCT LABELING. You are not authorized to use any Freescale > trademarks, > brand names, or logos. > > ENTIRE AGREEMENT. This Agreement constitutes the entire agreement > between > you and Freescale regarding the subject matter of this Agreement, and > supersedes all > prior communications, negotiations, understandings, agreements or > representations, either > written or oral, if any. This Agreement may only be amended in written > form, executed > by you and Freescale. > > SEVERABILITY. If any provision of this Agreement is held for any reason > to be > invalid or unenforceable, then the remaining provisions of this > Agreement will be > unimpaired and, unless a modification or replacement of the invalid or > unenforceable > provision is further held to deprive you or Freescale of a material > benefit, in which case > the Agreement will immediately terminate, the invalid or unenforceable > provision will be > replaced with a provision that is valid and enforceable and that comes > closest to the > intention underlying the invalid or unenforceable provision. > > NO WAIVER. The waiver by Freescale of any breach of any provision of > this > Agreement will not operate or be construed as a waiver of any other or a > subsequent > breach of the same or a different provision. > > If you read it all then I owe you a free beer! > > Regards, > David > > David E Seymour > Come to FTF 2008 June 16th through the 19th in Orlando > > http://www.freescale.com/ftf > > > -----Original Message----- > From: coldfire-bounce@... [mailto:coldfire-bounce@...] > On Behalf Of David Brown > Sent: Tuesday, June 10, 2008 3:41 PM > To: Seymour David > Subject: Re: [ColdFire] OpenTCP/http_server.c > > Seymour David wrote: >> Hi Bob, >> FSL had freely licensed the OpenTCP for NE64 and MCF5282 but as I >> mentioned before the resource at Viola left and the company decided to >> pull it. So FSL wanted an open source approach. The ColdFire TCP/IP > is >> freely license for use with FSL processors. It provides a nice step > to >> fully supported stack/OS from InterNiche should customers choose that >> route. >> Yes, it is being actively used by many and will continue to be. >> I think it is the up-sell area that FSL cannot generate code and post >> but customer can add whatever they want for their own use. I'll > triple >> check that answer and reply if I'm wrong. >> Regards, >> David >> >> David E Seymour > > Could you be more specific about the license? I couldn't see license > information on the website, and it's far from clear if by "freely > licensed" you mean "free speech" or just "free beer". > > mvh., > > David > > --- > coldfire@... Send a post to the list. > coldfire-join@... Join the list. > coldfire-digest@... Join the list in digest mode. > coldfire-leave@... Leave the list. > > --- > coldfire@... Send a post to the list. > coldfire-join@... Join the list. > coldfire-digest@... Join the list in digest mode. > coldfire-leave@... Leave the list. > > > --- coldfire@... Send a post to the list. coldfire-join@... Join the list. coldfire-digest@... Join the list in digest mode. coldfire-leave@... Leave the list. |
|
|
Re: OpenTCP/http_server.c
by Bob Furber
::
Rate this Message:
Seymour David wrote:
> FSL had freely licensed the OpenTCP for NE64 and MCF5282 but as I > mentioned before the resource at Viola left and the company decided to > pull it. So FSL wanted an open source approach. The ColdFire TCP/IP is > freely license for use with FSL processors. It provides a nice step to > fully supported stack/OS from InterNiche should customers choose that > route. > Yes, it is being actively used by many and will continue to be. > I think it is the up-sell area that FSL cannot generate code and post > but customer can add whatever they want for their own use. I'll triple > check that answer and reply if I'm wrong. It appears there was a flurry of activity on porting lwIP to the NE64 and the Coldfire5282, about 3 years ago. Would you have any recollection of this? Would you know why Freescale chose the InterNiche stack over the more widely supported lwIP? Thanks, Bob Furber > David E Seymour > Come to FTF 2008 June 16th through the 19th in Orlando > > http://www.freescale.com/ftf > > -----Original Message----- > From: coldfire-bounce@... [mailto:coldfire-bounce@...] > On Behalf Of Bob Furber > Sent: Tuesday, June 10, 2008 1:39 PM > To: Seymour David > Subject: Re: [ColdFire] OpenTCP/http_server.c > > Thanks David, > >> OpenTCP was the path we were going down to have a nice open source >> Ethernet stack available for ColdFire but the OpenTCP company's > resource >> to maintain it had left (long ago now) and they pulled the open source > >> licensing > > Yikes! For some reason I had assumed it was GPL. And, up until getting a > > TCP_EVENT_REGENERATE event, I was quite happy with OpenTCP. > > In any event, can Viola Systems Ltd. "pull the open source licensing" > one handed over in the license on every source page? > : > *Redistribution and use in source and binary forms, with or without > *modification, are permitted provided that the following conditions > *are met: > : >> so we/FSL turn to partnering with InterNiche to create a free >> ColdFire TCP/IP Lite Ethernet stack with (simple) multitasking OS. > > Judging by traffic on the Freescale forum, it appears that there are > licensing issues with TCP/IP Lite too. I also get the sense from the > forum that there were efforts to replace its multitasking OS by a > "superloop", which presumably means polling. This is not unreasonable > because an Ethernet chip or module typically has fairly large buffers. > It appears these efforts were ended because of licensing issues. > > Interestingly, Freescale has contributed the HTTP support files, with no > > restrictions other than "For use on Freescale products only". Is this > correct? > >> Take a look at its code base as it can handle upload of file. >> >> > _http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=COLDFIRE > _TCPIP_ >> then click the download tab. > > Thanks. > > Would you know if TCP/IP Lite has a fairly large and active > constituency? > > Thanks, > > Bob Furber > >> Regards, >> >> David >> >> David E Seymour >> >> Come to FTF 2008 June 16th through the 19th in Orlando >> >> http://www.freescale.com/ftf >> >> -----Original Message----- >> From: coldfire-bounce@... > [mailto:coldfire-bounce@...] >> On Behalf Of Bob Furber >> Sent: Monday, June 09, 2008 7:10 PM >> To: Seymour David >> Subject: [ColdFire] OpenTCP/http_server.c >> >> X-SpamDetect-Info: ------------- Start ASpam results --------------- >> >> X-SpamDetect-Info: This message may be spam. This message BODY has > been >> altered to show you the spam information >> >> X-SpamDetect: *****: 5.100000 DodgySource=2.0, SPF Default Fail=2.5, >> X-Verify-SMTP present=0.6 >> >> X-SpamDetect-Info: ------------- End ASpam results ----------------- >> >> Forgive me if this is not the appropriate list for posting an OpenTCP >> >> question. But I have not succeeded in finding a more appropriate list. >> >> I am trying to port the OpenTCP stack to the ColdFire and I am running >> >> into problems uploading files (target -> client) that are too large to >> >> fit in one frame. I get a TCP_EVENT_REGENERATE event. >> >> My understanding is that a TCP_EVENT_REGENERATE event is very rare. > So, >> in digging through the code, I notice something that does not seem > quite >> right: So long as there is unacknowledged data (i.e., file) remaining > to >> be sent, https_run() in the main loop loads the TCP Tx buffer with > data. >> It does NOT CHECK if the previous frame has been acknowledged. By > doing >> this, is there not a risk that https_run() could overfeed the client. >> >> Can anyone shed some light on this? >> >> Thanks, >> >> Bob Furber >> >> --- >> >> coldfire@... Send a post to the list. >> >> coldfire-join@... Join the list. >> >> coldfire-digest@... Join the list in digest mode. >> >> coldfire-leave@... Leave the list. >> >> coldfire@... Send a post to the list. >> coldfire-join@... Join the list. coldfire-digest@... > >> Join the list in digest mode. coldfire-leave@... Leave the > list. > > --- > coldfire@... Send a post to the list. > coldfire-join@... Join the list. > coldfire-digest@... Join the list in digest mode. > coldfire-leave@... Leave the list. > > --- > coldfire@... Send a post to the list. > coldfire-join@... Join the list. > coldfire-digest@... Join the list in digest mode. > coldfire-leave@... Leave the list. > > > --- coldfire@... Send a post to the list. coldfire-join@... Join the list. coldfire-digest@... Join the list in digest mode. coldfire-leave@... Leave the list. |
| Free embeddable forum powered by Nabble | Forum Help |
