I like your idea of initializing the device tree.
> Actually, a third method is necessary -- supplying driver names
on
>the 'command line' to the kernel, so that you don't have to hard-code the
>driver(s) used to access the harddrive to read the file to parse to
>generate the device tree. (You should also be able to replace drivers on
>the fly, though this would entail support in the driver being replaced in
>most cases -- because many drivers are persistent in the sense that
>replacing a driver in the Factory does not replace instances of that
>driver that may well be cached by an application or system process.)
I personally prefer the JavaOS for Business solution to this: instead of
giving an exact reference to the device when asked for, the device factory
instead returns a handler. When the device itself is removed, it sends a
signal to all registered handlers telling them that the device is being
removed. We could have a similar option for swapping devices.
>-_Quinn
-Matt
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
