Nouveau Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 70972] [NV67] Modesetting failure at 1280x800
Date: Sun, 03 Sep 2017 16:34:08 +0000	[thread overview]
Message-ID: <bug-70972-8800-7TQMteHDYo@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-70972-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #41 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
All of the modesetting logic (for pre-G80 chips) lives in

drivers/gpu/drm/nouveau/dispnv04

This is mostly an adaptation of xf86-video-nv to work in the kernel, with some
IMHO misguided "cleanups" that were applied to some of the incomprehensible
clock/etc calculation code. Unfortunately those are also mixed in with legit
fixes, so it's hard to undo.

Either way, since xf86-video-nv also reputedly can't make 1280x800 work,
reading that source is unlikely to be of much help. However at least the NV1A
and NV1F IGP's tend to have their own very special clock calculation logic, so
perhaps that's missing (might look at what e.g. NV4C/NV4E do, as those
allegedly work well).

There are already traces of both the blob and nouveau and how they perform the
modesetting (see attachments in this bug). What's largely missing is
identifying what nouveau does differently, and then coming up with a way to fix
it.

You can use 'demmio' from envytools to help analyze the traces
(https://github.com/envytools/envytools).

If you have questions about the tooling or the code, feel free to join in
#nouveau on irc.freenode.net.

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

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

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

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

  parent reply	other threads:[~2017-09-03 16:34 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 22:01 [Bug 70972] New: Nouveau fails with broken screen on nv40 with kernel 3.12 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-70972-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-11-09 20:51   ` [Bug 70972] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-10  0:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-10  1:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-10 18:35   ` [Bug 70972] [NV67] Modesetting failure at 1280x800 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-13  5:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 20:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 21:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 21:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 22:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-23 15:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-23 16:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-25 20:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-22  0:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-22  0:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-22  1:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-22 19:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-22 19:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-22 19:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-22 20:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-20 17:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-20 17:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-22 18:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-22 18:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-27 16:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 14:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 15:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 20:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 20:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 20:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 20:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 21:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 21:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 21:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 21:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 21:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 21:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 21:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-12 21:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-02 18:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-03 14:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-03 15:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-03 15:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-03 15:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-03 16:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-03 16:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2019-12-04  8:39   ` 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-70972-8800-7TQMteHDYo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox