Dan Mick wrote: > >> Heck, I think these prom properties should just be decorations on the >> normal in kernel device tree. There are probably some prom tree nodes >> which need special handling (/chosen?) but there could be a special tree >> for those, too. > > I don't remember any incompatibility between prom and kernel trees, > but it would be interesting to know if there were any; the fact that > there *are* two trees does seem archaic and not useful.
There are things that are in the prom tree which are not devices, and hence are not in the kernel tree. (See, for example, the /chosen node.) Software can change things in the kernel tree, but the prom tree is, as far as I know, immutable. I'm not sure that there exists any software which depends on this behavior. (One would hope not.) "Real code" generally has to examine both trees. This is implicit in the kernel interfaces, but the libdevinfo userland interface treats them totally separately (most annoyingly). -- Garrett D'Amore, Principal Software Engineer Tadpole Computer / Computing Technologies Division, General Dynamics C4 Systems http://www.tadpolecomputer.com/ Phone: 951 325-2134 Fax: 951 325-2191 _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
