Tom Horsley wrote:
> Speaking of mode setting, is there any legitimate reason for
> dragging stuff like that into the kernel? Isn't that normally
> the sort of thing that gets moved out of the kernel?
Not really, hardware drivers normally belong in the kernel (at least
low-level stuff).
There are a lot of reasons for doing this, starting with simple
robustness. It would also enable better suspend and resume support,
and better handling of panics: if the system goes into an oops, an
in-kernel mode-setting routine can switch back to a text mode,
allowing the oops text to actually be read.
(During an oops, userspace isn’t running, so the kernel can’t rely on X
to do mode switching. During suspend and resume, doing modesetting in
the kernel rather than in userspace means the kernel has a better idea
of the state the graphics are in, and can display diagnostics while
userspace isn’t running).
There is a lot of interest in supporting multiple, simultaneous X
sessions on the same screen without using Linux virtual terminals;
the goal here is to enable fast switching between user accounts. And
there is interest in H.264 acceleration, facilitating the display of
important things like HDTV. It seems that even contemporary CPUs can
have trouble keeping up with HDTV streams.
– http://lwn.net/Articles/218380/
Hope this helps,
James.
--
E-mail: james@ | WARNING: Pressing CTRL+ALT+DEL again will restart your
aprilcottage.co.uk | computer. Then again, what won't? You will lose unsaved
| information, and even supposedly saved information, in
| any case. -- David P. Murphy
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
