On 13/2/2024 7:32 pm, Sebastian Huber wrote:
> Hello Chris,
>
> sorry for the delay.
>
> On 07.02.24 00:56, Chris Johns wrote:
>> On 5/2/2024 9:13 pm, Sebastian Huber wrote:
>>> Hello Chris,
>>>
>>> thanks for having a look at it.
>>>
>>> On 02.02.24 00:14, Chris Johns wrote:
Hi,
T
Hello Chris,
sorry for the delay.
On 07.02.24 00:56, Chris Johns wrote:
On 5/2/2024 9:13 pm, Sebastian Huber wrote:
Hello Chris,
thanks for having a look at it.
On 02.02.24 00:14, Chris Johns wrote:
Hi,
Thanks for the updated documentation, protocol and use cases. It has helped. Now
I unde
On 5/2/2024 9:13 pm, Sebastian Huber wrote:
> Hello Chris,
>
> thanks for having a look at it.
>
> On 02.02.24 00:14, Chris Johns wrote:
>> Hi,
>>
>> Thanks for the updated documentation, protocol and use cases. It has helped.
>> Now
>> I understand some of the context I have raised further ques
Hello Chris,
thanks for having a look at it.
On 02.02.24 00:14, Chris Johns wrote:
Hi,
Thanks for the updated documentation, protocol and use cases. It has helped. Now
I understand some of the context I have raised further questions about it I feel
we should resolve. Without a protocol version
Hi,
Thanks for the updated documentation, protocol and use cases. It has helped. Now
I understand some of the context I have raised further questions about it I feel
we should resolve. Without a protocol version number being exchanged it limits
how we can grow and develop this protocol beyond wher
The RTEMS Test Framework packet processor provides a simple mechanism to
exchange reliable and in-order data through transmitting and receiving
one character at a time.
The packet processor does not buffer data. The processor uses a
stop-and-wait automatic repeat request method. There is at most
