From: "Dave Airlie" <airlied@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Andrew Morton <akpm@osdl.org>, Petr Vandrovec <vandrove@vc.cvut.cz>
Subject: Re: [PATCH] nvidiafb: Fix reversed DDC port
Date: Mon, 2 Apr 2007 09:07:57 +1000 [thread overview]
Message-ID: <21d7e9970704011607h3d901car4cdfe466396e7797@mail.gmail.com> (raw)
In-Reply-To: <460F7CF4.60006@gmail.com>
> After I added some debugging printks I've found that code became a bit
> confused because it believed that primary monitor is 1920x540, but later
> it found in CRTC0's registers that panel size is 1920x1200 (Windows also
> agree that 1920x1200 is primary monitor, and 1920x1080i secondary one).
>
> When I applied attached patch then my monitor became as happy as it was
> before I connected HDMI cable to secondary output.
>
I don't think this will do much except break other peoples cards,
different nvidia cards map the i2c to outputs differently, the correct
way to fix it is to read a table in the BIOS called the DCB table (for
NV4x and above...) guess what? we don't know how to do that properly
because nvidia are very unfriendly...
Dave.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-04-01 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 9:35 [PATCH] nvidiafb: Fix reversed DDC port Antonino A. Daplas
2007-04-01 23:07 ` Dave Airlie [this message]
2007-04-01 23:33 ` Antonino A. Daplas
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=21d7e9970704011607h3d901car4cdfe466396e7797@mail.gmail.com \
--to=airlied@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=vandrove@vc.cvut.cz \
/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;
as well as URLs for NNTP newsgroup(s).