All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Steev Klimaszewski <steev-4jv++OSWV9OTkO8mciVlQg@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Issue with a SOYO monitor and Trimslice
Date: Mon, 11 Nov 2013 10:46:26 +0100	[thread overview]
Message-ID: <20131111094625.GJ3884@ulmo.nvidia.com> (raw)
In-Reply-To: <CAKCjkJY4nYte00jj-f78G_cohXuXSw-krrubJh1dgANtvRhJkA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]

On Sun, Sep 22, 2013 at 06:26:11AM -0500, Steev Klimaszewski wrote:
> Hi all,
> 
> Was talking on IRC in #tegra and it was suggested that I email here as
> a reminder to tagr (Sorry, I don't know your real name!)
> 
> When I boot Linus' tree (3.12-rc1 at commit
> c43a3855f41a25330326570d8e8d54e9927b3f56 ) my monitor, which has only
> dvi and vga input, simply shows a box that states "Out of Range".  I
> am able to ssh into the machine, and run startx (using the modesetting
> driver) and then use xrandr to change the resolution from 1680x1050 to
> something like 1024x768. However, in dmesg with drm.debug=0xf I see
> the following:

Hi Steev,

I just remembered this thread from a while ago. There were some patches
to fix DVI support that will be merged into 3.13. You can find them in
the drm/for-next branch here:

	http://cgit.freedesktop.org/tegra/linux

Specifically:

	http://cgit.freedesktop.org/tegra/linux/commit/?h=drm/for-next&id=9f1591231aa72edd2cdad507520ad4088682262a

I'm not sure if it fixes the issue that you were seeing, but it might be
worth a try.

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2013-11-11  9:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-22 11:26 Issue with a SOYO monitor and Trimslice Steev Klimaszewski
     [not found] ` <CAKCjkJY4nYte00jj-f78G_cohXuXSw-krrubJh1dgANtvRhJkA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-23 11:28   ` Steev Klimaszewski
2013-11-11  9:46   ` Thierry Reding [this message]
     [not found]     ` <20131111094625.GJ3884-AwZRO8vwLAwmlAP/+Wk3EA@public.gmane.org>
2013-11-11 11:49       ` Steev Klimaszewski
     [not found]         ` <CAKCjkJaGvW80ycb_oh62_0WXUS0k8HJ=rMaPO+Gad_ZYAxbR_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-11 12:50           ` Thierry Reding

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=20131111094625.GJ3884@ulmo.nvidia.com \
    --to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=steev-4jv++OSWV9OTkO8mciVlQg@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.