On 03/31/2011 05:44 PM, ext Arjan van de Ven wrote:
On 3/31/2011 7:28 AM, Carsten Munk wrote:
2011/3/31 Arjan van de Ven<[email protected]>:
this is the wrong solution though; udev not fastinit need to take
care fo
this
Agreed, the problem here is that udev has probably not settled by the
time sensord starts (it is in rc.sysinit afterall and start_udev is in
a backgrounded nice -20) and finished it's initialization.
so call udev settle either as part of sensord or as part of the start
lines that start sensord ?
I somehow managed to miss this discussion, completely. I made a new
SR#16518:
http://build.meego.com/request/show/16518
the current thing gets you two concurrent module loading paths --> bad.
The best thing would be if sensord had udev support instead of a
static configuration file, or in some way wait for the devices
mentioned in the configuration instead of aborting when it can't find
them?
I would say that is a hard requirement for sensord to be useful..
That'd probably require substantial code changes which may breach
feature freeze - should we have a proper solution in 1.3 instead?
I would call this a serious design bug, and one that needs fixing.
I agree on that sensorfw should have udev support. But, as Carsten
suspected, that requires big code changes that won't be available for
MeeGo 1.2. Target for this would be 1.3.
--
Markus
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
