From: Sven Luther <luther@dpt-info.u-strasbg.fr>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Sven Luther <luther@dpt-info.u-strasbg.fr>,
Petr Vandrovec <VANDROVE@vc.cvut.cz>,
James Simmons <jsimmons@infradead.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] [PATCH]: EDID parser
Date: Thu, 3 Apr 2003 18:21:23 +0200 [thread overview]
Message-ID: <20030403162123.GA17123@iliana> (raw)
In-Reply-To: <1049383273.11742.0.camel@dhcp22.swansea.linux.org.uk>
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 ?
>
> I think you mean lowest common denominator.
>
> > 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 ?
Friendly,
Sven Luther
next prev parent reply other threads:[~2003-04-03 16:21 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
2003-04-03 15:21 ` Alan Cox
2003-04-03 16:21 ` Sven Luther [this message]
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=20030403162123.GA17123@iliana \
--to=luther@dpt-info.u-strasbg.fr \
--cc=VANDROVE@vc.cvut.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--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).