linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <luther@dpt-info.u-strasbg.fr>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: Sven Luther <luther@dpt-info.u-strasbg.fr>,
	James Simmons <jsimmons@infradead.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH]: EDID parser
Date: Thu, 3 Apr 2003 19:15:42 +0200	[thread overview]
Message-ID: <20030403171542.GD1092@iliana> (raw)
In-Reply-To: <51136F3B7C@vcnet.vc.cvut.cz>

On Thu, Apr 03, 2003 at 06:38:44PM +0200, Petr Vandrovec wrote:
> On  3 Apr 03 at 18:21, Sven Luther wrote:
> > On Thu, Apr 03, 2003 at 04:21:14PM +0100, Alan Cox wrote:
> > > On Iau, 2003-04-03 at 15:15, Sven Luther wrote:
> > > > > Read is not enough. If you have connected one /dev/fbx to two
> > > > > monitors, you must find highest common denominator for them, and use
> > > > > this one.
> > > > 
> > > > Err, i don't understand this ? Do you mean you are outputing to two
> > > > monitors at the same time ?
> 
> Yes. With matroxfb you can output same signal to all three outputs.
> It is default if you have g450 or g550 with recent driver.
> 
> > > > If that is so maybe you mean, speaking in graphic card terminology, and
> > > > not in fbdev one, that you are sharing one common framebuffer between
> > > > two outputs, right, possibly doing mirroring tricks or something such ?
> > > 
> > > Classic example is a SiS 6326 driving monitor and TV. You need to keep the
> > > display to TV acceptable ranges.
> > 
> > You mean, driving both display with the same ramdac ?
> 
> See http://www.bglug.ca/matrox_tvout/g450.jpg. Two inputs, three outputs,
> and almost any possible connection between them.

A, ok, you have the CRTC for which you program the timings and such, and
which can then be connected to the DACS or the TMDS or the video output.

You would need to keep a CRTC to output mapping in this case, and read
the DDC buses on the output, fill a table or something, and when the
user change the output mapping, revalidate the video modes in accord to
that. The mapping would not be a bijective one, but you could have more
than one output for one CRTC, i don't think you can have more than one
CRTC for a given output though. You could simply maintain a list of
outputs for each CRTC, and when you need to validate the mode, you have
to validate it for every output linked to each CRTC.

Friendly,

Sven Luther


-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/

  reply	other threads:[~2003-04-03 17:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-03 16:38 [PATCH]: EDID parser Petr Vandrovec
2003-04-03 17:15 ` Sven Luther [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-03 15:21 [Linux-fbdev-devel] " Alan Cox
2003-04-03 16:33 ` Geert Uytterhoeven
2003-04-03 17:10   ` [Linux-fbdev-devel] " Sven Luther
2003-04-03 16:15     ` Alan Cox
2003-04-03 17:18       ` Sven Luther
2003-04-02 21:55 [Linux-fbdev-devel] " James Simmons
2003-04-03  0:45 ` Antonino Daplas
2003-04-01 15:32 Antonino Daplas
2003-04-02 15:41 ` Antonino 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=20030403171542.GD1092@iliana \
    --to=luther@dpt-info.u-strasbg.fr \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=jsimmons@infradead.org \
    --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).