Page 3 of 5 FirstFirst 12345 LastLast
Results 21 to 30 of 41

Thread: NVIDIA Announces New Legacy Linux Support

  1. #21
    Join Date
    Feb 2012
    Posts
    446

    Default

    Quote Originally Posted by logistiker View Post
    I guess I'm a newcomer to this. Please explain how I can use the nvidia blob to switch to a console quickly without having to load vesa?
    You can't. Because nvidia doesn't provide a fbcon driver. But that's something separate from modesetting.

  2. #22
    Join Date
    Sep 2012
    Posts
    13

    Default

    Quote Originally Posted by Gusar View Post
    You can't. Because nvidia doesn't provide a fbcon driver. But that's something separate from modesetting.
    Isn't fast VT switching a feature of kernel mode setting regardless?

  3. #23
    Join Date
    Feb 2012
    Posts
    446

    Default

    Quote Originally Posted by logistiker View Post
    Isn't fast VT switching a feature of kernel mode setting regardless?
    Having modesetting in the kernel is a means to achieve it. But you need a fbcon driver for that. KMS drivers have it. Nvidia doesn't.

  4. #24
    Join Date
    Sep 2012
    Posts
    13

    Default

    Quote Originally Posted by logistiker View Post
    Isn't fast VT switching a feature of kernel mode setting regardless?
    i.e. without loading an external fbcon driver.

  5. #25
    Join Date
    Sep 2012
    Posts
    13

    Default

    Quote Originally Posted by Gusar View Post
    Having modesetting in the kernel is a means to achieve it. But you need a fbcon driver for that. KMS drivers have it. Nvidia doesn't.
    So how does the absence of this fbcon driver in the nvidia blob which is key to having KMS support consider the blob as having KMS support?

  6. #26
    Join Date
    Sep 2012
    Posts
    13

    Default

    Quote Originally Posted by Gusar View Post
    Having modesetting in the kernel is a means to achieve it. But you need a fbcon driver for that. KMS drivers have it. Nvidia doesn't.
    Maybe we're debating semantics here. I see what you mean by a "framework" but I'm not sure if it can be considered as KMS support if you have everything but the fbcon driver built in.

  7. #27
    Join Date
    Feb 2012
    Posts
    446

    Default

    Quote Originally Posted by logistiker View Post
    So how does the absence of this fbcon driver in the nvidia blob which is key to having KMS support consider the blob as having KMS support?
    One, fbcon is not key to having KMS. It's just that KMS drivers provide it. But they could just as well not. KMS is an implementation of modesetting in the kernel. Nothing less, nothing more.

    Two, the blob doesn't have KMS support, I never said that. It has an implementation of modesetting in the kernel. A different one from KMS.

  8. #28
    Join Date
    Sep 2012
    Posts
    13

    Default

    Quote Originally Posted by Gusar View Post
    One, fbcon is not key to having KMS. It's just that KMS drivers provide it. But they could just as well not. KMS is an implementation of modesetting in the kernel. Nothing less, nothing more.

    Two, the blob doesn't have KMS support, I never said that. It has an implementation of modesetting in the kernel. A different one from KMS.
    So linux kernel modesetting support (separate from the nvidia blob kernel modesetting - how do you differentiate between the two -- prefix one with nvidia and the other with linux?) doesn't require having a built in fbcon? Hmm, seems like multiple phoronix articles point to this as being a feature of kernel modesetting in the linux kernel. Do you have a source that mentions fbcon is optional with the linux kernel-based implementation (not nvidia) of kernel mode setting?

  9. #29
    Join Date
    Jan 2010
    Posts
    364

    Default

    If by "KMS" you mean the standard mode setting framework in the kernel, the blob will never be able to implement it due to license issues.

  10. #30
    Join Date
    Sep 2012
    Posts
    13

    Default

    Quote Originally Posted by brent View Post
    If by "KMS" you mean the standard mode setting framework in the kernel, the blob will never be able to implement it due to license issues.
    So since nvidia has their own kernel mode setting implementation, then I suppose they could just pretend KMS (linux kernel-based - not nvidia-base - kernel mode setting) doesn't exist and implement their own proprietary fbcon driver and accomplish fast VT switching. Then whatever licensing issues that stops them from using KMS can be bypassed right?

Posting Permissions

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