From: Sven Luther <luther@dpt-info.u-strasbg.fr>
To: James Simmons <jsimmons@infradead.org>
Cc: Jurriaan Kalkman <thunder7@xs4all.nl>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: will the new edid functionality allow vesafb to set a frequency?
Date: Fri, 11 Apr 2003 10:09:48 +0200 [thread overview]
Message-ID: <20030411080948.GA2338@iliana> (raw)
In-Reply-To: <Pine.LNX.4.44.0304102241430.23050-100000@phoenix.infradead.org>
On Thu, Apr 10, 2003 at 10:42:30PM +0100, James Simmons wrote:
>
> > As the owner of a NVidia card, whose evil proprietary driver won't work
> > with rivafb, but would possibly work with vesafb (I see mixed messages
> > on usenet about this), I have the following question:
> >
> > will the new edid-functionality that is currently in heavy development
> > allow linux (somewhere in the future) to set a vertical refresh frequency
> > with vesafb? I did notice that this Ti500 card has a VESA/VBE 3.0
> > compatible BIOS, so it should be possible.
>
> Yes. Also long as your monitor supports EDID correctly. I tested it on my
> laptop and the data was botched :-(
BTW, what about monitors having a dual input (vga and dvi). I think they
give back the same edid on both entries, yet clearly the dvi entry
cannot do scaling and support less monitor modes, at lest for my Sony
SDM-X52. BTW, get-edid failed to read the entries :
get-edid: get-edid version 1.4.1
Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
Function supported
Call successful
VBE version 200
VBE string at 0x11148 " P9"
VBE/DDC service about to be called
Report DDC capabilities
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
Function supported
Call successful
Monitor and video card combination does not support DDC1 transfers
Monitor and video card combination supports DDC2 transfers
0 seconds per 128 byte EDID block transfer
Screen is not blanked during DDC transfer
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 7 more blocks left
*********** Something special has happened!
Please contact the author, John Fremlin
E-mail: one of vii@altern.org,vii@mailcc.com,vii@mailandnews.com
Please include full output from this program (especially that to stderr)
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 255 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 255 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 255 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 255 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 255 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 255 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 7 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
ÿÿÿÿÿÿ\0MÙP \x01\x01\x01\x01&\f\x01\x03€\x1e\x17xê~© XN–%\x1eHL¡\b\0\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01d\x19\0@A\0&0\x18ˆ6\00ä\x10\0\0\x18\0\0\0ý\09?\x1c1\a\0
\0\0\0ü\0SDM-X52
\0\0\0ÿ\04518830
\0\aÿ\0MÙP \x01\x01\x01\x01&\f\x01\x03€\x1e\x17xê~© XN–%\x1eHL¡\b\0\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01d\x19\0@A\0&0\x18ˆ6\00ä\x10\0\0\x18\0\0\0ý\09?\x1c1\a\0
\0\0\0ü\0SDM-X52
\0\0\0ÿ\04518830
\0\aÿÿÿÿÿÿÿÿ\0MÙP \x01\x01\x01\x01&\f\x01\x03€\x1e\x17xê~© XN–%\x1eHL¡\b\0\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01d\x19\0@A\0&0\x18ˆ6\00ä\x10\0\0\x18\0\0\0ý\09?\x1c1\a\0
\0\0\0ü\0SDM-X52
\0\0\0ÿ\04518830
\0\aÿÿÿÿÿÿÿÿ\0MÙP \x01\x01\x01\x01&\f\x01\x03€\x1e\x17xê~© XN–%\x1eHL¡\b\0\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01d\x19\0@A\0&0\x18ˆ6\00ä\x10\0\0\x18\0\0\0ý\09?\x1c1\a\0
\0\0\0ü\0SDM-X52
\0\0\0ÿ\04518830
\0\aÿÿÿÿÿÿÿÿ\0MÙP \x01\x01\x01\x01&\f\x01\x03€\x1e\x17xê~© XN–%\x1eHL¡\b\0\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01d\x19\0@A\0&0\x18ˆ6\00ä\x10\0\0\x18\0\0\0ý\09?\x1c1\a\0
\0\0\0ü\0SDM-X52
\0\0\0ÿ\04518830
\0\aÿÿÿÿÿÿÿÿ\0MÙP \x01\x01\x01\x01&\f\x01\x03€\x1e\x17xê~© XN–%\x1eHL¡\b\0\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01d\x19\0@A\0&0\x18ˆ6\00ä\x10\0\0\x18\0\0\0ý\09?\x1c1\a\0
\0\0\0ü\0SDM-X52
\0\0\0ÿ\04518830
\0\aÿÿÿÿÿÿÿÿ\0MÙP \x01\x01\x01\x01&\f\x01\x03€\x1e\x17xê~© XN–%\x1eHL¡\b\0\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01d\x19\0@A\0&0\x18ˆ6\00ä\x10\0\0\x18\0\0\0ý\09?\x1c1\a\0
\0\0\0ü\0SDM-X52
\0\0\0ÿ\04518830
\0\aÿÿÿÿÿÿÿÿ\0MÙP \x01\x01\x01\x01&\f\x01\x03€\x1e\x17xê~© XN–%\x1eHL¡\b\0\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01d\x19\0@A\0&0\x18ˆ6\00ä\x10\0\0\x18\0\0\0ý\09?\x1c1\a\0
\0\0\0ü\0SDM-X52
\0\0\0ÿ\04518830
\0\aÿ
Friendly,
Sven Luther
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
prev parent reply other threads:[~2003-04-11 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-03 12:02 will the new edid functionality allow vesafb to set a frequency? Jurriaan Kalkman
2003-04-10 21:42 ` James Simmons
2003-04-11 8:09 ` Sven Luther [this message]
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=20030411080948.GA2338@iliana \
--to=luther@dpt-info.u-strasbg.fr \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=thunder7@xs4all.nl \
/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).