Hello Joel,
From: Joel Sherrill [j...@rtems.org]
Sent: Monday, February 26, 2018 12:21
> On Feb 26, 2018 5:13 AM, "Jakob Viketoft" <jakob.viket...@aacmicrotec.com>
> wrote:
>> E.g. could it be possible for the translation mechanism to look if there is
>> already an errno defined and then return this instead of doing the error
>> code translation?
>> It seems like the translation I'm talking about happens in the
>> rtems_deviceio_write() function in cpukit/libcsupport/src/sup_fs_deviceio.c
> Completely random thought as I sit on a plane without code.
> Add a field to the arguments structure for errno. See it to zero before the
> call. If it is set to non-zero after the call, then the driver wanted to
> return errno directly. Otherwise translate.
This was my thought as well, I just wanted to bounce it off the RTEMS list and
also possibly get official support for a feature as this.
> A middle step is to see if any of the unused RTEMS status codes make sense to
> use and cover your use cases.
This is the way we do it today. Unfortunately, so many of the different RTEMS
codes are translated into the same errno codes which makes it very hard to have
an intelligent error reporting/differentiation.
/Jakob
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
