From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: nvidiafb, monitor A & B and CRTC 0 & 1
Date: Sat, 31 Mar 2007 17:48:36 -0700 [thread overview]
Message-ID: <460F0164.9080600@vc.cvut.cz> (raw)
In-Reply-To: <1175341893.4420.1.camel@daplas>
Antonino A. Daplas wrote:
> On Sun, 2007-03-25 at 06:01 -0700, Petr Vandrovec wrote:
>> Hello,
>> how much are you sure that monitor A i2c should use ddc_base 0x3E,
>> and monitor B base 0x36 ?
>
> This was chosen arbitrarily, hoping that the code will sort out which is
> which. If reversing the ports worked for you, I will not disagree with
> the patch.
Yes. Without patch two analogs work fine (well, in that case nvidiafb
does not care about maximum resolution), as well as analog+digital or
digital+analog. Only configuration which does not work correctly are
two digital monitors. With patch all four configurations work correctly
on my hardware. I do not have access to any other dual-dvi nvidia card,
so I cannot tell whether BFGTech screwed up or whether there is some
other problem. Windows detect which display is first and which second
correctly...
Petr
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2007-04-01 0:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-25 13:01 nvidiafb, monitor A & B and CRTC 0 & 1 Petr Vandrovec
2007-03-31 11:51 ` Antonino A. Daplas
2007-04-01 0:48 ` Petr Vandrovec [this message]
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=460F0164.9080600@vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=adaplas@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).