From a system designer's perspective, there are reasons why a simple
microcontroller in the chipset could be very useful. There are lots of low-level maintenance things (like setting fan speed) that would otherwise have to be added to every OS; it makes sense for this to be completely automatic from the OS perspective. In fact, lots of things are off-loaded from the host CPU to other controllers, like many aspects of networking, audio, and graphics.
This article describes a controller that's much more central to the system than some of these other things, and I agree that it can be used for nefarious purposes, but the world is filled with countless useful things that can be abused, like the internet, authority, and sharp cooking knives. So, let's not get too worked up over these things. But at the same time, let's be aware of the potential abuses and always be on the push for more open systems that fully disclose their behaviors so that we can better understand them and protect ourselves from the abuse. On 6/28/07, Raphaël Jacquot <[EMAIL PROTECTED]> wrote:
after open graphics, I think there's a need to work on the rest: http://marc.info/?l=openbsd-misc&m=118302016430106&w=2 this sort of thing scares me to death _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
-- Timothy Normand Miller http://www.cse.ohio-state.edu/~millerti Open Graphics Project _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
