From: Gabriel C <nix.or.die@googlemail.com>
To: spock@gentoo.org
Cc: linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, hpa@zytor.com
Subject: Re: [PATCH v2 0/5] uvesafb: a general description
Date: Sat, 30 Jun 2007 22:48:07 +0200 [thread overview]
Message-ID: <4686C187.3090308@googlemail.com> (raw)
In-Reply-To: <20070630163101.GA3838@spock.one.pl>
Michal Januszewski wrote:
> uvesafb is a generic driver for VBE2+ compliant video cards; an enhanced
> version of vesafb and a direct successor of vesafb-tng [1].
>
>
Hi Michal,
I've just tested uvesafb on my workstation ( which has a really old
GeForce2 MX 400 Nvidia card ) and it didn't worked here.
If I remember right vesafb-ntg worked here and vesafb works for sure :)
Here the error from dmesg :
....
[ 37.397298] uvesafb: Getting VBE info block failed (eax=0x4f00, err=-3)
[ 37.397358] uvesafb: vbe_init() failed with -22
[ 37.397411] uvesafb: probe of uvesafb.0 failed with error -22
....
Here some infos I got with read-edid[1] tool:
./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 300
VBE string at 0x11110 "NVidia"
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 successful
.....
./parse-edid: parse-edid version 1.4.1
./parse-edid: EDID checksum passed.
# EDID version 1 revision 3
Section "Monitor"
# Block type: 2:0 3:ff
# Block type: 2:0 3:fd
# Block type: 2:0 3:fc
Identifier "GD 7000S"
VendorName "GRC"
ModelName "GD 7000S"
# Block type: 2:0 3:ff
# Block type: 2:0 3:fd
HorizSync 30-83
VertRefresh 50-75
# Max dot clock (video bandwidth) 140 MHz
# Block type: 2:0 3:fc
# DPMS capabilities: Active off:yes Suspend:yes Standby:yes
Mode "1280x1024" # vfreq 60.013Hz, hfreq 63.974kHz
DotClock 108.500000
HTimings 1280 1344 1472 1696
VTimings 1024 1025 1028 1066
Flags "+HSync" "+VSync"
EndMode
# Block type: 2:0 3:ff
# Block type: 2:0 3:fd
# Block type: 2:0 3:fc
EndSection
...
Let me know if you need more infos.
Regards,
Gabriel C
[1] http://john.fremlin.de/programs/linux/read-edid/
PS: You have an typo on line 702 in the patch from your website
s/vesafb/uvesafb/ in that printk
next prev parent reply other threads:[~2007-06-30 20:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 16:31 [PATCH v2 0/5] uvesafb: a general description Michal Januszewski
2007-06-30 16:31 ` Michal Januszewski
2007-06-30 20:48 ` Gabriel C [this message]
2007-07-03 23:05 ` Gabriel C
2007-07-05 17:38 ` Ryan Hope
2007-07-06 19:53 ` Michal Januszewski
2007-07-06 19:53 ` Michal Januszewski
-- strict thread matches above, loose matches on Subject: below --
2007-08-06 17:04 Zbigniew
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=4686C187.3090308@googlemail.com \
--to=nix.or.die@googlemail.com \
--cc=hpa@zytor.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=spock@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.