uvesafb is a generic driver for VBE2+ compliant video cards; an enhanced
version of vesafb and a direct successor of vesafb-tng [1].
This is the second version of this patch, and it incorporates all fixes
and cleanups suggested on the lkml. My thanks to everyone who took
their time to review the first version.
uvesafb uses a userspace helper application (v86d, [2]) to run the x86
Video BIOS code. This makes it possible to include in uvesafb all the
standard features (refresh rate control, video mode changes etc) that
are missing from vesafb without resorting to ugly hacks such as the ones
used in [1]. The current implementation of v86d can use either LRMI or
x86emu to run the BIOS code and supports both x86 and x86_64.
[1] http://dev.gentoo.org/~spock/projects/vesafb-tng/
[2] http://dev.gentoo.org/~spock/projects/uvesafb/
Best regards.
--
Michal Januszewski JID: [email protected]
Gentoo Linux Developer http://people.gentoo.org/spock
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
>I've already updated the patch on my website, so next time
>you download it, the error messages should be gone.
the latest uvesafb (rc3-2.6.22.patch)
and v86d(0.1-rc4) doesn't work against 2.6.22.1 ;(
dmesg:
uvesafb: Getting VBE info block failed (eax=0x4f00, err=-3)
uvesafb: vbe_init() failed with -22
uvesafb: probe of uvesafb.0 failed with error -22
distr slackware 12 with my own kernel 2.6.22.1 (on 2.6.21.5 works fine)
lspci :
VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev
b2) (prog-if 00 [VGA])
--
Pozdrawiam/Regards
Zibi K.