matthias.clasen at gmail.com
Wed Jan 23 19:38:55 PST 2008
On Jan 23, 2008 10:15 PM, Michael Biebl <mbiebl at gmail.com> wrote:
> Well, CK was conceived to provide this kind of information. So e.g.
> HAL can easily query them before executing the shutdown request.
> There is no good reason why the reboot/stop functionality has to be
> put into CK. It only violates the layer boundaries for no good reason.
I don't see any layer boundaries being violated here.
What layers are there in your perspective, and why does reboot fit in
the hal layer,
but not the CK layer ?
And if CK starts using information from hal to assemble seat
configuration, what are
we going to do then ?
More information about the hal