From: Pavel Machek <pavel@ucw.cz>
To: Sander ten Broek <sander@telefabel.cjb.net>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Use EDID/DDC data to set better refreshrates on VBE3.0+ videocards on boot
Date: Mon, 11 Aug 2003 01:39:49 +0200 [thread overview]
Message-ID: <20030810233949.GA3898@elf.ucw.cz> (raw)
In-Reply-To: <3F2DAD6D.2010605@telefabel.cjb.net>
Hi!
>
> The following patch requests EDID data from the monitor/graphics card,
> check it against the vga= setting the user set and when it finds a match
> sets the refresh rate to the EDID supplied mode (So should be safe, even
> on broken biosses). This makes working in vesafb mode _allot_ better for
> your eyes. If either no vesa 3.0 card or VBE/DC EDID data is available
> it just sets the vesa graphic mode the old tried and tested way (60Hz ugh!).
>
> I have tested the patch on the following cards with different feature
> support (All same type monitor though):
>
> - Geforce2 MX/MX 400: Working at 85hz
> - Geforce 256 SDR: Working at 85Hz
> - GeForce2 - nForce GPU: Not working, no EDID data available
> - VMWare v4: Not working, not a VBE v3.00 card
>
> Not working, in this case, means that it just used normal 60hz vesa
> mode. The graphic mode was otherwise working fine.
>
> What do you think? :)
This is really needed for vesafb to be usefull on non-LCD displays...
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-08-10 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 0:48 [PATCH] Use EDID/DDC data to set better refreshrates on VBE3.0+ videocards on boot Sander ten Broek
2003-08-10 23:39 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-04 8:03 Daniel Blueman
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=20030810233949.GA3898@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=sander@telefabel.cjb.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