libi2c: Claiming driver slot failed

[Joel Sherrill]

On 8/11/2013 10:10 PM, Chris Johns wrote:
> Nick Withers wrote:
>> It seems to me like there's an inversion of the App ->  BSP ->  RTEMS
>> abstraction going on here, where the app effectively needs to know
>> "black-box" details of the BSP, making maintenence and portability more
>> difficult and error prone than needs be...?
>>
> I would like to see the drivers and the device table become unlimited
> just like the other unlimited resources in the kernel. The value becomes
> an allocation unit.
Agreed it would be nice.

But, in the short term, I think Nick is simply complaining that the
i2c driver has implicit configuration requirements he has to
explicitly configure.

I didn't write and haven't used the i2c driver, so I have to ask:

What are the configuration requirements for the i2c driver?

I expect the ATA/IDE driver and any other stock driver dynamically
registered as a side-effect of a capability initialization call has the
same issue.
> Chris
>


-- 
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