[PATCH 10] IO_MANAGER: early dynamic driver registration

Joel Sherrill joel.sherrill at OARcorp.com
Fri Feb 3 17:26:11 UTC 2012

Sorry to cut this down but this is the crux of the problem.

On 02/03/2012 10:33 AM, Daniel Hellstrom wrote:
>> >>  boot_card() is the master initialization sequencer.  Sebastian is
>> >>  right that you can use the bsp_pretasking_hook() or you can
>> >>  use the bsp_predriver_hook().
> >  Without the patch however, rtems_io_initialize() is called twice for every dynamically register driver from bsp_predriver_hook().
> >
Given that as the issue, I wondered if there are enough
system states to solve the issues. The answer is no.
There is no system state change between

There were always steps in the initialization sequence
of "RTEMS readiness" which could have been noted
but there was no requirement to do so.

Would it make sense (and solve this problem) to add at
least one more state? In particular, at least a state at
the end of initializing all drivers to indicate that drivers
have been initialized?

I can also see a state for "initializing drivers" because
a solution to this problem might require that to support
registering during initialization.

NOTE: Any solution like this needs to evaluate the uses
of the system states as defined. It would be easy to
break something. :)

Joel Sherrill, Ph.D.             Director of Research&   Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
     Support Available             (256) 722-9985

More information about the devel mailing list