Re: [RFC PATCH 00/10] ratp: new generic RATP command support

2018-02-07 Thread Sascha Hauer
On Tue, Feb 06, 2018 at 05:43:40PM +0100, Aleksander Morgado wrote: > >> > >> The first patches (1-5) break the current RATP API, by introducing > >> the concept of requests, responses and indications: > >> * Requests sent to one endpoint are expected to be replied with > >>a response by the

Re: [RFC PATCH 00/10] ratp: new generic RATP command support

2018-02-06 Thread Aleksander Morgado
>> >> The first patches (1-5) break the current RATP API, by introducing >> the concept of requests, responses and indications: >> * Requests sent to one endpoint are expected to be replied with >>a response by the peer endpoint. >> * Indications are messages sent from one endpoint to

Re: [RFC PATCH 00/10] ratp: new generic RATP command support

2018-02-06 Thread Sascha Hauer
Hi Aleksander, On Fri, Feb 02, 2018 at 12:14:32PM +0100, Aleksander Morgado wrote: > Until now, the barebox-specific RATP commands were all defined and > implemented in common/ratp.c. This series of patches allow ratp > commands to be defined in a similar way to console commands. I like the

[RFC PATCH 00/10] ratp: new generic RATP command support

2018-02-02 Thread Aleksander Morgado
Until now, the barebox-specific RATP commands were all defined and implemented in common/ratp.c. This series of patches allow ratp commands to be defined in a similar way to console commands. The first patches (1-5) break the current RATP API, by introducing the concept of requests, responses and