libi2c: Claiming driver slot failed

[ruizx]

On Friday, August 09, 2013 10:33 AM Chris Johns wrote:

> Nick Withers wrote:
>> On Mon, 2013-08-05 at 14:02 +1000, Nick Withers wrote:
>>> Hi guys,
>>> 
>>> When I boot an MVME3100 (PowerPC) off the ticker sample
>>> application, I get an error message "libi2c: Claiming driver slot
>>> failed (rtems status code 5)".
>> 
>> (snip)
>> 
>> I got past this by #defining CONFIGURE_MAXIMUM_DRIVERS up to 10.
>> 
>> Is this something that I should have to do? Would've thought the BSP
>> code'd handle this...?
> 
> The BSP may require a number of driver slots while the actual number
> used depends on your application and the drivers it uses. It is useful
> on targets where the memory size is small.
> 
> Currently there is no way for the BSP to provide a number for the
> table so the application needs to size things to get it running. If
> you have ideas on how this could be done we would welcome it.
> 
> Chris
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-users
> .

I also find CONFIGURE_MAXIMUM_TASKS has is this problem.
There are some system tasks or component related tasks, e.g. bd swap task,read ahead task.
So at begining I'll set a big enough value, then change it to a suitable value later.