Console driver that needs extra TIMER

[Sebastian Huber]

On 14/08/14 16:25, Joel Sherrill wrote:
> On 8/14/2014 9:21 AM, Sebastian Huber wrote:
>> >On 14/08/14 16:15, Joel Sherrill wrote:
>>>> >>>E.g. most of the tests won't even start without modifications. So
>>>>> >>>>effectively I have to fall back to a polling driver for console if I
>>>>> >>>>want to run the tests unmodified, or is there any mechanism to generally
>>>>> >>>>increment the amount of timers for all tests?
>>> >>I don't think so. There are some BSP hooks for various features and
>>> >>default number
>>> >>of termios ports. But nothing specific to an object.
>>> >>
>>> >>I suppose one could be added but for orthogonality, it would make me wonder
>>> >>why we wouldn't also let you add a BSP factor on every Classic API object.
>>> >>Just thinking out load.
>> >Its not only a BSP factor.  It is also a per driver factor.  Since the console
>> >and clock drivers are optional if you make it only BSP specific, then you have
>> >to overestimate.
>> >
> That has been the problem with the number of termios ports. When set
> above 1 needed for
> the tests, it tends to cover up resource under allocation issues.
>
> If the "needs driver" is not defined, the constant could be undef'ed and
> redef'ed to 0.

One option is to add APIs without the RTEMS object model (e.g. the one from 
FreeBSD) on which the user is responsible to provide the storage.  This works 
well with static initialization and doesn't require complicated additions to 
the already complicated configuration.

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.