[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-users] Re: [lwip] problems with tcp_segs
From: |
James Roth |
Subject: |
[lwip-users] Re: [lwip] problems with tcp_segs |
Date: |
Wed, 08 Jan 2003 22:29:31 -0000 |
--------------070407070609010806060101
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Andrea Olivotto wrote:
>07/05/02 9.21.20, Andrea Olivotto <address@hidden> wrote:
>
>
>>I'm using an 8051 plus Keil compiler, single thread enviroment.
>>I admit that using that platfor there are some porting problem, so I don't
>>exclude the case one or more
>>porting bugs.
>>...
>>
>
>
>Ops!
>
>Likely I found the problem, obviously a porting issue. Excuse!
>
Was it a time related bug like mine? Perhaps we should put some sanity
checks in the layer above sys_arch to help new ports. In my case, it
took a while to discover the problem. Maybe a sys_arch test driver too.
>
>To Adam: I love you when you write us those messages like the last...
>
>
>Andrea
>
>
>
>
>[This message was sent through the lwip discussion list.]
>
--
James Roth
Shugyo Design Technologies
http://www.shugyodesign.com/
--------------070407070609010806060101
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit
<html>
<head>
</head>
<body>
Andrea Olivotto wrote:<br>
<blockquote type="cite" cite="mid:address@hidden">
<pre wrap="">07/05/02 9.21.20, Andrea Olivotto <a
class="moz-txt-link-rfc2396E"
href="mailto:address@hidden"><address@hidden></a> wrote:<br><br><br></pre>
<blockquote type="cite">
<pre wrap="">I'm using an 8051 plus Keil compiler, single thread
enviroment.<br>I admit that using that platfor there are some porting problem,
so I don't exclude the case one or more <br>porting bugs.<br>...<br></pre>
</blockquote>
<pre wrap=""><!----><br><br>Ops!<br><br>Likely I found the problem,
obviously a porting issue. Excuse!<br><br></pre>
</blockquote>
Was it a time related bug like mine? Perhaps we should put some sanity checks
in the layer above sys_arch to help new ports. In my case, it took a while
to discover the problem. Maybe a sys_arch test driver too.<br>
<blockquote type="cite" cite="mid:address@hidden">
<pre wrap=""><br>To Adam: I love you when you write us those messages
like the last...<br><br><br>Andrea<br><br><br><br><br>[This message was sent
through the lwip discussion list.]<br></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="$mailwrapcol">--
James Roth
Shugyo Design Technologies
<a class="moz-txt-link-freetext"
href="http://www.shugyodesign.com/">http://www.shugyodesign.com/</a>
</pre>
<br>
</body>
</html>
--------------070407070609010806060101--
[This message was sent through the lwip discussion list.]
- [lwip-users] Re: [lwip] problems with tcp_segs,
James Roth <=
- [lwip-users] Re: [lwip] problems with tcp_segs, Andrea Olivotto, 2003/01/08
- [lwip-users] Re: [lwip] problems with tcp_segs, James Roth, 2003/01/08
- [lwip-users] Re: [lwip] problems with tcp_segs, Adam Dunkels, 2003/01/08
- [lwip-users] Re: [lwip] problems with tcp_segs, Andrea Olivotto, 2003/01/09
- [lwip-users] Re: [lwip] problems with tcp_segs, Andrea Olivotto, 2003/01/09
- [lwip-users] Re: [lwip] problems with tcp_segs, Jani Monoses, 2003/01/09