[lng-odp] [API-NEXT RFC PATCH 0/3] new try for a adding a driver interface

2016-01-26 Thread Christophe Milard
This patch series implements a new structure in the ODP repo so that new interfaces can be more easily added to ODP Saddly changing the current structure seems needed as just adding to it results in a quite fuzzy file organisation: Today: include/odp/api is the reference for the ODP API interface

Re: [lng-odp] [API-NEXT RFC PATCH 0/3] new try for a adding a driver interface

2016-01-26 Thread Mike Holmes
Inline comment on include structure On 26 January 2016 at 13:04, Christophe Milard wrote: > This patch series implements a new structure in the ODP repo so that new > interfaces can be more easily added to ODP > > Saddly changing the current structure seems needed as just adding to it > results

Re: [lng-odp] [API-NEXT RFC PATCH 0/3] new try for a adding a driver interface

2016-01-26 Thread Christophe Milard
On 26 January 2016 at 22:45, Mike Holmes wrote: > Inline comment on include structure > > On 26 January 2016 at 13:04, Christophe Milard < > christophe.mil...@linaro.org> wrote: > >> This patch series implements a new structure in the ODP repo so that new >> interfaces can be more easily added to

Re: [lng-odp] [API-NEXT RFC PATCH 0/3] new try for a adding a driver interface

2016-01-27 Thread Christophe Milard
In other words, what I don't like with your proposal, Mike, is that the term "application" gets two meanings: in "app", it means the program attached to the north interface. in "api", (the "a" is for application),it means anything attached to ODP (either north or south interface) I dont think havi