The sound driver doesn't map and copy big chunks of memory around. More to
the point, compare the number of crashes from Alan's sound driver work to
those during fbcon development. Likewise, NT stability (granted, always an
iffy proposition) took a turn for the worse when Microsoft moved video
drivers into ring 0 during the NT4 beta cycle, and it hasn't recovered.
Then there's the OS/2 model: minimal drivers to map memory in ring 0, the
rest of the privileged part of the drivers live in ring 2 (not 3). (This
would also work for the sound drivers, come to think of it.)
You're doing your best to paint the situation as all one or all the other,
nothing in between. I regard such as overly simplistic and therefore
strawmen.
| screen, and if the screen is hosed I still get it in my syslog. When X
+--->8
...try the scrollback/<Return> tricks recently mentioned on this list.
-- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering carnegie mellon university (bsa@kf8nh is still valid.)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html