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 47846] Nouveau -> overscan using HDMI
Date: Thu, 07 Jan 2016 22:21:21 +0000	[thread overview]
Message-ID: <bug-47846-8800-fEKXcF22kn@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-47846-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #21 from lameventanas-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org ---
(In reply to ITwrx from comment #20)
> @lameventanas-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
> 
> i ran "kodi -send --action='ActivateWindow(screencalibration)'"
> 
> but it just opened up kodi in default fashion and underscan was still not
> accounted for. was "screencalibration" above just an example?
> 
> thanks

You have to run this (don't insert a space):
"kodi-send --action='ActivateWindow(screencalibration)'"

once Kodi is already running, it will trigger the screen calibration dialog,
where you can compensate for overscan/underscan by yourself (in Kodi).  You can
also find it somewhere in the Settings window.

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

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

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

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

  parent reply	other threads:[~2016-01-07 22:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-25 16:35 [Bug 47846] New: Nouveau -> overscan using HDMI bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-47846-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-03-25 16:54   ` [Bug 47846] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-03-25 22:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-03-26  7:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-03-27 20:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-04-13  6:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-04-13  8:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-04-16 21:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-04-17  6:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-04-17 12:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-04-19 23:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-04-20 21:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-04-23  3:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-06  9:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-16 23:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-17  0:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-17  0:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-13 13:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-05 14:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-05 15:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-07 19:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-07 22:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2019-12-04  8:27   ` 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-47846-8800-fEKXcF22kn@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.