On Wed, Feb 15, 2017 at 5:14 AM, Savolainen, Petri (Nokia - FI/Espoo) <petri.savolai...@nokia-bell-labs.com> wrote: > > > From: Yi He [mailto:yi...@linaro.org] > Sent: Tuesday, February 14, 2017 3:59 AM > To: Savolainen, Petri (Nokia - FI/Espoo) > <petri.savolai...@nokia-bell-labs.com> > Cc: Brian Brooks <brian.bro...@linaro.org>; lng-odp@lists.linaro.org > Subject: Re: [lng-odp] [PATCH v3 0/8] First ABI files > > Hi, Petri and Brian > > Can I understand this patch series are giving various platforms a chance to > define their own data structures (like odp_event_t etc) in arch directory, > instead of sharing the same definitions as previously?
The way this software reads is that some data types of the API are now defined in these Arch+OS (pair) files instead of by the ODP implementation itself. This is headed in the right direction! .. because the implementation should NOT be allowed to define API types. But, it needs to be taken even further. One complete and universal set of APIs. What is the concrete use case for allowing all of these API types to be defined differently for each Arch+OS pair? I have previously sent a patch to the list which defines all of the API in one universal set of header files. > Best Regards, Yi > > > No, this adds ABI spec(s). One ABI spec cover (potentially) many > implementations. If an implementation is built in ABI compat mode, it has to > use definitions of the ABI spec. Otherwise (non-ABI compat mode), it can use > its own definitions. > > -Petri >
