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>,
	linux-kernel@vger.kernel.org
Subject: Re: [Linux-fbdev-devel] [PATCH]: EDID parser
Date: Thu, 3 Apr 2003 16:15:30 +0200	[thread overview]
Message-ID: <20030403141530.GA8858@iliana> (raw)
In-Reply-To: <4E5C514B42@vcnet.vc.cvut.cz>

On Thu, Apr 03, 2003 at 03:55:48PM +0200, Petr Vandrovec wrote:
> On  3 Apr 03 at 15:48, Sven Luther wrote:
> > 
> > Ideally, the EDID reading would be done just after the user request an
> > output mapping change for the first time, and then stored privately to
> > each output. mode changes and such would be done after the output has
> > been assigned only, and you would have the EDID by then. You could even
> > reread it regularly, in case the monitor is hot swapped or something such.
> 
> 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 ?

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 ?

If that is so, then it is ok still, since you would do the EDID read and
the mode setting at the moment you activate the video output. At this
time, you know what monitor is attached (since you can probe it) and can
check the mode with respect of what you know is possible. The main point
here is to do the mode setting based on what the ouptu can support, not
on what the fbdev thinks is right.

Friendly,

Sven Luther

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

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-03 13:55 [Linux-fbdev-devel] [PATCH]: EDID parser Petr Vandrovec
2003-04-03 14:15 ` Sven Luther [this message]
2003-04-03 15:21   ` Alan Cox
2003-04-03 16:21     ` Sven Luther
2003-04-03 16:18       ` 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-03 16:29             ` [Linux-fbdev-devel] " Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2003-04-03 14:38 Petr Vandrovec
2003-04-03 13:48 ` Sven Luther
2003-04-03 14:05 Petr Vandrovec
2003-04-03 13:11 ` Sven Luther
2003-04-03 11:05 Petr Vandrovec
2003-04-03 12:20 ` Benjamin Herrenschmidt
2003-04-03 12:38 ` Sven Luther
2003-04-03  2:07 Petr Vandrovec
2003-04-03  7:40 ` Sven Luther
2003-04-02 15:41 Antonino Daplas
2003-04-02 21:55 ` [Linux-fbdev-devel] " James Simmons
2003-04-02 22:20   ` Benjamin Herrenschmidt
2003-04-03  0:45   ` Antonino Daplas
2003-04-03  6:44     ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-04-03  7:05       ` Benjamin Herrenschmidt

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=20030403141530.GA8858@iliana \
    --to=luther@dpt-info.u-strasbg.fr \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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 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).