On 05.11.2024 19:02, Peter Robinson wrote:
> On Tue, 5 Nov 2024 at 15:15, Simon Glass wrote:
>> Hi Peter,
>>
>> On Tue, 5 Nov 2024 at 06:10, Peter Robinson wrote:
>>> On Tue, 5 Nov 2024 at 13:03, Simon Glass wrote:
Hi Tom,
On Mon, 4 Nov 2024 at 16:32, Tom Rini wrote:
> On M
On Tue, Nov 05, 2024 at 12:03:49PM -0700, Simon Glass wrote:
> Hi Tom,
>
> On Tue, 5 Nov 2024 at 11:26, Tom Rini wrote:
> >
> > On Tue, Nov 05, 2024 at 09:07:17AM -0700, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Tue, 5 Nov 2024 at 08:47, Tom Rini wrote:
> > > >
> > > > On Tue, Nov 05, 2024
On 06.11.2024 02:00, Tom Rini wrote:
> On Tue, Nov 05, 2024 at 09:59:57PM +0300, Mikhail Kshevetskiy wrote:
>> On 05.11.2024 21:26, Tom Rini wrote:
>>> On Tue, Nov 05, 2024 at 09:07:17AM -0700, Simon Glass wrote:
Hi Tom,
On Tue, 5 Nov 2024 at 08:47, Tom Rini wrote:
> On Tue, N
On Tue, Nov 05, 2024 at 09:59:57PM +0300, Mikhail Kshevetskiy wrote:
>
> On 05.11.2024 21:26, Tom Rini wrote:
> > On Tue, Nov 05, 2024 at 09:07:17AM -0700, Simon Glass wrote:
> >> Hi Tom,
> >>
> >> On Tue, 5 Nov 2024 at 08:47, Tom Rini wrote:
> >>> On Tue, Nov 05, 2024 at 08:15:25AM -0700, Simon
Hi Tom,
On Tue, 5 Nov 2024 at 11:26, Tom Rini wrote:
>
> On Tue, Nov 05, 2024 at 09:07:17AM -0700, Simon Glass wrote:
> > Hi Tom,
> >
> > On Tue, 5 Nov 2024 at 08:47, Tom Rini wrote:
> > >
> > > On Tue, Nov 05, 2024 at 08:15:25AM -0700, Simon Glass wrote:
> > > > Hi Peter,
> > > >
> > > > On Tue
On 05.11.2024 21:26, Tom Rini wrote:
> On Tue, Nov 05, 2024 at 09:07:17AM -0700, Simon Glass wrote:
>> Hi Tom,
>>
>> On Tue, 5 Nov 2024 at 08:47, Tom Rini wrote:
>>> On Tue, Nov 05, 2024 at 08:15:25AM -0700, Simon Glass wrote:
Hi Peter,
On Tue, 5 Nov 2024 at 06:10, Peter Robinson
On Tue, Nov 05, 2024 at 09:07:17AM -0700, Simon Glass wrote:
> Hi Tom,
>
> On Tue, 5 Nov 2024 at 08:47, Tom Rini wrote:
> >
> > On Tue, Nov 05, 2024 at 08:15:25AM -0700, Simon Glass wrote:
> > > Hi Peter,
> > >
> > > On Tue, 5 Nov 2024 at 06:10, Peter Robinson wrote:
> > > >
> > > > On Tue, 5 No
Hi Tom,
On Tue, 5 Nov 2024 at 08:47, Tom Rini wrote:
>
> On Tue, Nov 05, 2024 at 08:15:25AM -0700, Simon Glass wrote:
> > Hi Peter,
> >
> > On Tue, 5 Nov 2024 at 06:10, Peter Robinson wrote:
> > >
> > > On Tue, 5 Nov 2024 at 13:03, Simon Glass wrote:
> > > >
> > > > Hi Tom,
> > > >
> > > > On M
On Tue, 5 Nov 2024 at 15:15, Simon Glass wrote:
>
> Hi Peter,
>
> On Tue, 5 Nov 2024 at 06:10, Peter Robinson wrote:
> >
> > On Tue, 5 Nov 2024 at 13:03, Simon Glass wrote:
> > >
> > > Hi Tom,
> > >
> > > On Mon, 4 Nov 2024 at 16:32, Tom Rini wrote:
> > > >
> > > > On Mon, Oct 28, 2024 at 05:31
On Tue, Nov 05, 2024 at 08:15:25AM -0700, Simon Glass wrote:
> Hi Peter,
>
> On Tue, 5 Nov 2024 at 06:10, Peter Robinson wrote:
> >
> > On Tue, 5 Nov 2024 at 13:03, Simon Glass wrote:
> > >
> > > Hi Tom,
> > >
> > > On Mon, 4 Nov 2024 at 16:32, Tom Rini wrote:
> > > >
> > > > On Mon, Oct 28, 20
Hi Peter,
On Tue, 5 Nov 2024 at 06:10, Peter Robinson wrote:
>
> On Tue, 5 Nov 2024 at 13:03, Simon Glass wrote:
> >
> > Hi Tom,
> >
> > On Mon, 4 Nov 2024 at 16:32, Tom Rini wrote:
> > >
> > > On Mon, Oct 28, 2024 at 05:31:30PM +0300, Mikhail Kshevetskiy wrote:
> > >
> > > > Legacy TCP stack i
On Tue, Nov 05, 2024 at 06:03:44AM -0700, Simon Glass wrote:
> Hi Tom,
>
> On Mon, 4 Nov 2024 at 16:32, Tom Rini wrote:
> >
> > On Mon, Oct 28, 2024 at 05:31:30PM +0300, Mikhail Kshevetskiy wrote:
> >
> > > Legacy TCP stack is bad. Here are some of the known issues:
> > > * tcp packet from other
On Tue, 5 Nov 2024 at 13:03, Simon Glass wrote:
>
> Hi Tom,
>
> On Mon, 4 Nov 2024 at 16:32, Tom Rini wrote:
> >
> > On Mon, Oct 28, 2024 at 05:31:30PM +0300, Mikhail Kshevetskiy wrote:
> >
> > > Legacy TCP stack is bad. Here are some of the known issues:
> > > * tcp packet from other connection
Hi Tom,
On Mon, 4 Nov 2024 at 16:32, Tom Rini wrote:
>
> On Mon, Oct 28, 2024 at 05:31:30PM +0300, Mikhail Kshevetskiy wrote:
>
> > Legacy TCP stack is bad. Here are some of the known issues:
> > * tcp packet from other connection can break a current one
> > * tcp send sequence always starts fr
On Mon, Oct 28, 2024 at 05:31:30PM +0300, Mikhail Kshevetskiy wrote:
> Legacy TCP stack is bad. Here are some of the known issues:
> * tcp packet from other connection can break a current one
> * tcp send sequence always starts from zero
> * bad tcp options processing
> * strange assumptions o
Legacy TCP stack is bad. Here are some of the known issues:
* tcp packet from other connection can break a current one
* tcp send sequence always starts from zero
* bad tcp options processing
* strange assumptions on packet size for selective acknowledge
* tcp interface assumes one of the two
16 matches
Mail list logo