All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 110830] [nouveau] GeForce GTX 1660 Ti (mobile) not supported (NV168/TU116)
Date: Fri, 14 Jun 2019 21:28:25 +0000	[thread overview]
Message-ID: <bug-110830-8800-Mu5TqvcXNg@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110830-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 691 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=110830

--- Comment #13 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
(In reply to Marcin Zajaczkowski from comment #12)
> [1]. Is it just needed to add a new entry for my GTX 1660 in nv_driver.c?

Mmmmaybe. You'd have to kill Accel for it too, since none of the other
functions will work either.

> Anyway, do you think using nouveau_drv.so instead of "modesetting" can
> change anything?

Not in the reverse prime case -- it can only make things worse. IIRC
nouveau_drv expects acceleration support for handling reverse prime.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1598 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2019-06-14 21:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03 13:30 [Bug 110830] New: [nouveau] GeForce GTX 1660 Ti (mobile) not supported (NV168/TU116) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-110830-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2019-06-03 13:32   ` [Bug 110830] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-03 18:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-07  9:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-07 10:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-07 10:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-07 13:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-07 20:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-07 20:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-07 21:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-14 15:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-14 15:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-14 21:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-14 21:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2019-07-09 18:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-09 18:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-110830-8800-Mu5TqvcXNg@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.