linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: Brett <generica@email.com>,
	linux-kernel@vger.kernel.org,
	linux-fbdev-devel@lists.sourceforge.net, jsimmons@infradead.org
Subject: Re: CONFIG_VIDEO_SELECT stole my will to live
Date: Tue, 20 May 2003 20:05:12 +0200	[thread overview]
Message-ID: <2110DE22C31@vcnet.vc.cvut.cz> (raw)

On 20 May 03 at 18:18, Dave Jones wrote:
> On Tue, May 20, 2003 at 05:55:41PM +0100, James Simmons wrote:
> 
>  > > Wasn't the EDID stuff getting backed out anyways ?
>  > Only in the VESA driver. Some people did have luck with the BIOS EDID info 
>  > so I like to keep the BIOS call in there. 
> 
> That code runs way earlier than before we get to do any PCI quirks,
> so fixing that one up could be interesting.

On my system (G450 + Compaq MV600 + TV) this EDID call takes about 
5 seconds (fortunately it does not die), so I'll be happy if I can config
this out - especially as matroxfb gives you DDC access from inside Linux.
                                            Thanks,
                                                Petr Vandrovec
                                                vandrove@vc.cvut.cz



-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

             reply	other threads:[~2003-05-20 18:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20 18:05 Petr Vandrovec [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-20 14:14 CONFIG_VIDEO_SELECT stole my will to live Brett
2003-05-20 15:51 ` Dave Jones
2003-05-20 16:55   ` James Simmons
2003-05-20 17:18     ` Dave Jones
2003-05-20 17:24     ` Dave Jones

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=2110DE22C31@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=davej@codemonkey.org.uk \
    --cc=generica@email.com \
    --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).