[PATCH] rtems: Generate <rtems/bspIo.h>

[Sebastian Huber]

On 30/07/2021 15:55, Joel Sherrill wrote:
> 
> On Fri, Jul 30, 2021, 8:33 AM Sebastian Huber 
> <sebastian.huber at embedded-brains.de 
> <mailto:sebastian.huber at embedded-brains.de>> wrote:
> 
>     On 30/07/2021 15:25, Joel Sherrill wrote:
>      > On Fri, Jul 30, 2021 at 1:52 AM Sebastian Huber
>      > <sebastian.huber at embedded-brains.de
>     <mailto:sebastian.huber at embedded-brains.de>>  wrote:
>      >> On 30/07/2021 00:54, Chris Johns wrote:
>      >>> On 29/7/21 10:59 pm, Sebastian Huber wrote:
>      >>>> On 29/07/2021 14:51, Sebastian Huber wrote:
>      >>>>> Change license to BSD-2-Clause according to file histories and
>      >>>>> documentation re-licensing agreement.
>      >>>>>
>      >>>>> Place the group into the I/O Manager group.  Add all source
>     files to the
>      >>>>> group.
>      >>>>>
>      >>>>> Update #3899.
>      >>>>> Update #3993.
>      > Should the specification include what format specifiers are
>     supported? Those
>      > would seem to be API contracts/requirements.
> 
>     What we have currently is this:
> 
>     .. rubric:: PARAMETERS:
> 
>     ``fmt``
>           This parameter is a printf()-style format string.
> 
>     .. rubric:: CONSTRAINTS:
> 
>     The following constraints apply to this directive:
> 
>     * The directive may be called from within any runtime context.
> 
>     * The directive will not cause the calling task to be preempted.
> 
>     * Formatting of floating point numbers is not supported.
> 
>     Doing a detailed documentation of the supported format specifiers would
>     be a bit of work.
> 
> 
> I wasn't thinking of heavy detail. Just a list of which specifiers are 
> supported and maybe some general missing format options. Beyond that see 
> printf for details.
> 
> I was thinking you would need a requirement for a specifier that is 
> supported. Otherwise you don't have traceability to the entire source code.
> 
> Trying to focus on general description of what was present for the 
> missing the requirements are positive, not negative.

For the space profile I only need rtems_putc(), rtems_put_char(), and 
getchark(). The _IO_Vprintf() belongs to the test code.

-- 
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber at embedded-brains.de
phone: +49-89-18 94 741 - 16
fax:   +49-89-18 94 741 - 08

Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/