Page 4 of 4 FirstFirst ... 234
Results 31 to 35 of 35

Thread: Another New KMS Graphics Driver Tips Up

  1. #31
    Join Date
    Apr 2011
    Posts
    114

    Default

    Quote Originally Posted by curaga View Post
    - flicker free boot
    - faster VT switch
    - kernel errors visible if X hangs

    Now, which of these is important in a server?
    Userspace modesetting is incompatible with UEFI Secure Boot, so if you want to run X on a server using it then KMS is the only option.

  2. #32
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,414

    Default

    Quote Originally Posted by Qaridarium View Post
    this makes me sad :-( for Linux only low-end... they always push open-source in the low-end corner.
    It shouldn't make you sad. Besides, midrange cards are actually a better fit than low end cards. I think you've said this yourself in the past as well.

    Optimizing a driver to take full advantage of high end hardware without getting bottlenecked on CPU usage is a *lot* of work, doesn't significantly benefit users of low end and midrange hardware, and adds a lot of complexity to the stack which makes it harder to maintain for everyone. Doesn't mean it won't happen, just that it doesn't seem like a smart thing to spend a lot of time until the more broadly useful areas have been addressed.

    Quote Originally Posted by Qaridarium View Post
    thats just a crime!
    Sure it's a crime, like when you take the elevator to the 50th floor you have to go past the 25th floor on the way. Criminal.

  3. #33
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    5,034

    Default

    Quote Originally Posted by mjg59 View Post
    Userspace modesetting is incompatible with UEFI Secure Boot, so if you want to run X on a server using it then KMS is the only option.
    Huh, why is that?

  4. #34
    Join Date
    Apr 2011
    Posts
    114

    Default

    Quote Originally Posted by curaga View Post
    Huh, why is that?
    Because letting userspace have direct access to PCI devices means userspace could DMA arbitrary data over the kernel and firmware, compromising the security.

  5. #35
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    5,034

    Default

    Ah, you're talking about it used positively No wonder that didn't come to mind.

    In the usual case Secure Boot is a swearword and it's just wanted out of the way, then the kernel can do what it wants.

Posting Permissions

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