Results 1 to 3 of 3

Thread: kernel modesetting?

  1. #1
    Join Date
    Nov 2007
    Posts
    1,355

    Default kernel modesetting?

    I have heard in recent times that development towards a kernel based modesetting scheme is being worked on... What is the benefit of doing that? Wouldnt it be better to let the driver handle modesetting? If the kernel is allowed to handle modesetting would that mean that dula monitors would be supported on virtual consoles? And does this have anything to do with a "flicker free" bootup, and what does that mean anyway?

    Also how would the framebuffer be handled? How would the kernel pass control over to the driver?

    Sorry for the stupid questions, I'm just a little confused?

  2. #2
    Join Date
    May 2007
    Posts
    233

    Default

    Quote Originally Posted by duby229 View Post
    I have heard in recent times that development towards a kernel based modesetting scheme is being worked on... What is the benefit of doing that? Wouldnt it be better to let the driver handle modesetting? If the kernel is allowed to handle modesetting would that mean that dula monitors would be supported on virtual consoles? And does this have anything to do with a "flicker free" bootup, and what does that mean anyway?

    Also how would the framebuffer be handled? How would the kernel pass control over to the driver?

    Sorry for the stupid questions, I'm just a little confused?
    Take a look at:

    http://mirror.linux.org.au/pub/linux...-intel-gfx.pdf

    Basicly it's yes to every of your questions. And explaining how framebuffer, i guess you mean linux framebuffer, is handled would need to go into a lot of technical details, so i should just say it will work but you shoud not use this API anymore.

    Oh and kernel modesetting means that the driver in kernel, do the stuff. So i don't see what you are thinking about when you ask if it wouldn't be better to have the driver do it.

  3. #3
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,578

    Default

    Yep. Kernel modesetting is mostly about moving modesetting code from the user mode X driver to the kernel mode DRM driver and starting it up earlier in the boot process (X starts pretty late) so that the same code can be used by all the different processes needing to write to the screen.

    Right now there are a number of different drivers accessing the graphics hardware, and if they don't all use HW the same way" you can get some evil suspend/resume problems.
    Last edited by bridgman; 04-18-2008 at 12:11 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •