Tell me more ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.
up vote 7 down vote favorite
1

With KMS, the graphics drivers are moved into the kernel. Since the framebuffer was already in the kernel, I wouldn't expect this to affect framebuffer operation. Yet, I read that KMS supercedes the fb, augments the fb, requires the fb, and requires fb support to be removed. What the heck? The answer I'm looking for is an explanation of the relationship between KMS and the framebuffer.

I have been using uvesafb to get native resolution at the tty. My purpose here is to understand how that is going to work on a system with KMS. It would also help to cover things like.. Is scrolling faster with KMS? Do utilities like fbterm and fbida work the same? Is stability better?

share|improve this question

1 Answer

up vote 2 down vote

KMS sets display resolution and depth in the kernel space rather than user space. So yes it supersedes it. It enables native resolution in the framebuffer.

Kernel Mode Setting

share|improve this answer
2  
Wiki articles about KMS are easy to find, but the explanations are terrible. How can KMS supersede the fb and at the same time enable it? The fb already supported native resolution, so what is different? Do fb utilities work with KMS? – user5184 Jun 28 '11 at 15:29
i don't think framebuffer support native resolution, especially when the monitor is widescreen. for example, native resolution of my LCD monitor is 1680x1050, however, framebuffer only detect 1280x1024 resolution – LiuYan 刘研 Oct 28 '12 at 9:34

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.