From: Dave Jones <davej@codemonkey.org.uk>
To: James Simmons <jsimmons@infradead.org>
Cc: Brett <generica@email.com>,
linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: CONFIG_VIDEO_SELECT stole my will to live
Date: Tue, 20 May 2003 18:24:28 +0100 [thread overview]
Message-ID: <20030520172428.GA32478@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0305201752240.28600-100000@phoenix.infradead.org>
On Tue, May 20, 2003 at 05:55:41PM +0100, James Simmons wrote:
> > Possibly the card's VGA BIOS has 'issues' with that call.
> This is most likely the case. I just tested out the configuration he has
> and it worked for me. I'm running vga=5 right now. For teh majority it
> works but as usual there are some broken BIOS that cause issues.
Or possibly..
It looks to me that the store_edid function is unconditionally calling
the READ EDID function without first having called the installation
check function. (Int 10h ax=4f15 bx=0)
Ralf Brown's interrupt list (which is pretty much definitive afaik)
also notes that for the READ EDID function, dx should be 0, we are
using 1. Is there a reason for this ?
Dave
-------------------------------------------------------
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
next prev parent reply other threads:[~2003-05-20 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-20 18:05 Petr Vandrovec
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=20030520172428.GA32478@suse.de \
--to=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).