[PATCH][RFC] cache generation + separate FDI parser process
Danny Kukawka
danny.kukawka at web.de
Tue Jan 9 11:04:04 PST 2007
On Tuesday 09 January 2007 18:13, Rob Taylor wrote:
> Danny Kukawka wrote:
> > On Tuesday 09 January 2007 14:20, Sergey Lapin wrote:
[...]
> > This change mean I can't add a new fdi-file and attach my new hardware
> > without restart HAL or/and hald-cache? No good idea on a normal system
> > (and not a embedded device with known number of devices). And if I need
> > to validate and read all files with each (re)start or change I can't see
> > a significant advantage on nomal systems compared to a in HAL solution(or
> > something like a addon/callout).
>
> Isn't it that case that you currently need to restart hal to reload
> fdis? (di_init_rules is only called when no fdi's have been parsed and
> cached yet)
Not sure if this is currently the case, but in the past you could copy a new
fdi-file to the related directory, (re)plug the related hardware and the
fdi-file was read in (IIRC).
The point is: if my both points not work, it's maybe acceptable for a embedded
device, but not for a normal desktop/laptop or a server (where HAL start need
several minutes or more as in the past).
Danny
More information about the hal
mailing list