You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Guillaume Durand <gd...@gillinfo.com> on 2006/07/13 16:15:40 UTC
DeviceManager and driver bundle update
Hello,
my question isn't felix specific since it has no DeviceManager
implementation yet, but it may sometime.
When a driver bundle is updated the spec says the DeviceManager should
wait some time to determine if the bundle is really updated or rather
uninstalled (or stopped).
I suppose it is to determine wether to release the matches between the
driver and its devices.
The implementations I tried so far (knopflerfish R3, and eclipse R4)
seem to not implement this behaviour, since if there are 2 drivers
declared for the same device category and I update the currently used
one the other one is immediately attached to the devices even though it
has a lower match value. It seems there's something wrong here as I
would expect the higher matching one should always be used.
Do these implementations just forgot to implement this behaviour or did
I misunderstand the spec?
--
Guillaume Durand
SIRLAN Technologies
Direct : 04 76 53 35 14
Standard : 04 76 53 35 10
Re: DeviceManager and driver bundle update
Posted by Stefano Lenzi <ki...@interfree.it>.
Guillaume Durand wrote:
> Do these implementations just forgot to implement this behaviour or did
> I misunderstand the spec?
>
IMHO, I think that they are not following the standard.