Announcement

Collapse
No announcement yet.

NVIDIA Announces New Legacy Linux Support

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    I now actually read the full announcement. The 304 branch will be supported until the end of 2017! That's a helluva long time. I was thinking two years tops. Five years, that's quite a commitment.

    The 173 branch will be supported until the end of 2013. That's not nearly as much, but still cool.

    Comment


    • #17
      Originally posted by Gusar View Post
      I now actually read the full announcement. The 304 branch will be supported until the end of 2017! That's a helluva long time. I was thinking two years tops. Five years, that's quite a commitment.

      The 173 branch will be supported until the end of 2013. That's not nearly as much, but still cool.
      On top of that, 6000 and 7000 series are quite old. Still capable, but old. By 2017, you'll be able to buy something better for $20. Or you'll have better GPU integrated into the CPU. Either way, losing support at the end of 2017 will hurt less than 1000 users, imho.

      Comment


      • #18
        I'm just glad they squeezed in xrandr support before jettisoning it as legacy so at least I can have proper multiple monitor support on my old geforce 6 desktop and geforce 7 laptop. I agree in an earlier post that it would have been nice to have KMS support as well but then who knows if that will ever be supported by the binary blob?

        Comment


        • #19
          Originally posted by logistiker View Post
          I agree in an earlier post that it would have been nice to have KMS support as well but then who knows if that will ever be supported by the binary blob?
          Here we go *again*...

          The nvidia driver has used kernel modesetting since forever. Since before there was KMS. There's no reason whatsoever for them to use KMS.

          Comment


          • #20
            Originally posted by Gusar View Post
            Here we go *again*...

            The nvidia driver has used kernel modesetting since forever. Since before there was KMS. There's no reason whatsoever for them to use KMS.
            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?

            Comment


            • #21
              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.

              Comment


              • #22
                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?

                Comment


                • #23
                  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.

                  Comment


                  • #24
                    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.

                    Comment


                    • #25
                      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?

                      Comment


                      • #26
                        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.

                        Comment


                        • #27
                          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.

                          Comment


                          • #28
                            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?

                            Comment


                            • #29
                              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.

                              Comment


                              • #30
                                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?

                                Comment

                                Working...
                                X