* [9fans] Intel X4500 Integrated Graphics support
@ 2011-12-20 7:40 Akshat Kumar
2011-12-20 13:52 ` erik quanstrom
0 siblings, 1 reply; 12+ messages in thread
From: Akshat Kumar @ 2011-12-20 7:40 UTC (permalink / raw)
To: 9fans
My Thinkpad X200s has an Intel X4500 card,
but vga(3) defaults to using vesa. Has anyone
added any support for this card lately? Or is
there any other vga `type' that can be set in
/dev/vgactl, which would offer better
performance than vesa, for this card?
Thanks,
ak
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [9fans] Intel X4500 Integrated Graphics support
2011-12-20 7:40 [9fans] Intel X4500 Integrated Graphics support Akshat Kumar
@ 2011-12-20 13:52 ` erik quanstrom
2011-12-20 14:47 ` Stanley Lieber
` (3 more replies)
0 siblings, 4 replies; 12+ messages in thread
From: erik quanstrom @ 2011-12-20 13:52 UTC (permalink / raw)
To: 9fans
On Tue Dec 20 02:41:29 EST 2011, akumar@mail.nanosouffle.net wrote:
> My Thinkpad X200s has an Intel X4500 card,
> but vga(3) defaults to using vesa. Has anyone
> added any support for this card lately? Or is
> there any other vga `type' that can be set in
> /dev/vgactl, which would offer better
> performance than vesa, for this card?
i think most people are using vesa. unfortunately
that limits one to 4:3 graphics modes.
which kernel are you using? if you get write-combining
going through pat or mtrr, and use double buffering,
things should be pretty good on most hardware.
(true of the kernels you could download today.)
- erik
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: [9fans] Intel X4500 Integrated Graphics support
2011-12-20 13:52 ` erik quanstrom
@ 2011-12-20 14:47 ` Stanley Lieber
2011-12-25 16:09 ` Aram Hăvărneanu
[not found] ` <CAHfqX-qFqRSY9itF3dWzWn-11vmSJrFAjG=j+yC2yjQJHxnnDw@mail.gmail.c>
` (2 subsequent siblings)
3 siblings, 1 reply; 12+ messages in thread
From: Stanley Lieber @ 2011-12-20 14:47 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
On Tue, Dec 20, 2011 at 7:52 AM, erik quanstrom <quanstro@quanstro.net> wrote:
> i think most people are using vesa. unfortunately
> that limits one to 4:3 graphics modes.
Some card/monitor combinations seem to support other aspect ratios
that are technically outside of the VESA spec. For example, my NVidia
GeForce 8400GS coupled with an NEC AccuSync AS221WM 22" via DVI-D[1]
happily runs[2] at the monitor's native resolution of 1680x1050 with
VESA, which is 16:10. I was also able to achieve 1680x1050 on the
AS221WM with an Intel GMA 3000 via VGA. The deciding factor seems to
be whatever modes are contained in the specific VESA BIOS that is in
your specific video card.
Note: depending upon the monitor, and depending upon how the card is
connected to the monitor, the VESA BIOS may present the user with
different available modes. Typically, aux/vga -p will produce
different output when the same hardware is connected via VGA, DVI-D,
HDMI, etc.
-sl
[1]
term% @{rfork n; aux/realemu; aux/vga -p}
fd 000000FD00384C1F5311000A202020202020
vesa flag Ulinear|Hlinear|Fsnarf
vesa sig VESA 3.0
vesa oem NVIDIA 96.134
vesa vendor NVIDIA Corporation
vesa product G86 Board - p413h05
vesa rev Chip Rev
vesa cap 8-bit-dac
vesa mem 14680064
vesa mode 0x100 640x400x8 m8 packed
vesa mode 0x101 640x480x8 m8 packed
vesa mode 0x103 800x600x8 m8 packed
vesa mode 0x105 1024x768x8 m8 packed
vesa mode 0x107 1280x1024x8 m8 packed
vesa mode 0x10e 320x200x16 r5g6b5 direct
vesa mode 0x10f 320x200x32 x8r8g8b8 direct
vesa mode 0x111 640x480x16 r5g6b5 direct
vesa mode 0x112 640x480x32 x8r8g8b8 direct
vesa mode 0x114 800x600x16 r5g6b5 direct
vesa mode 0x115 800x600x32 x8r8g8b8 direct
vesa mode 0x117 1024x768x16 r5g6b5 direct
vesa mode 0x118 1024x768x32 x8r8g8b8 direct
vesa mode 0x11a 1280x1024x16 r5g6b5 direct
vesa mode 0x11b 1280x1024x32 x8r8g8b8 direct
vesa mode 0x130 320x200x8 m8 packed
vesa mode 0x131 320x400x8 m8 packed
vesa mode 0x132 320x400x16 r5g6b5 direct
vesa mode 0x133 320x400x32 x8r8g8b8 direct
vesa mode 0x134 320x240x8 m8 packed
vesa mode 0x135 320x240x16 r5g6b5 direct
vesa mode 0x136 320x240x32 x8r8g8b8 direct
vesa mode 0x13d 640x400x16 r5g6b5 direct
vesa mode 0x13e 640x400x32 x8r8g8b8 direct
vesa mode 0x160 1280x800x8 m8 packed
vesa mode 0x161 1280x800x32 x8r8g8b8 direct
vesa mode 0x162 768x480x8 m8 packed
vesa mode 0x168 1680x1050x8 m8 packed
vesa mode 0x169 1680x1050x32 x8r8g8b8 direct
edid mfr NEC
edid serialstr 03105090TA
edid name AS221WM
edid product 26562
edid serial 0
edid version 1.3
edid mfrdate 2010.10
edid size (cm) 47x30
edid gamma 2.20
edid vert (Hz) 56-76
edid horz (Hz) 31000-83000
edid pclkmax 170000000
edid flags digital standby suspend activeoff
edid 640x480@60Hz
clock=25.175
shb=648 ehb=792 ht=800
vrs=490 vre=492 vt=525
hsync=- vsync=-
edid 640x480@73Hz
clock=31.5
shb=648 ehb=824 ht=832
vrs=489 vre=492 vt=520
hsync=- vsync=-
edid 640x480@75Hz
clock=31.5
shb=640 ehb=840 ht=840
vrs=481 vre=484 vt=500
hsync=- vsync=-
edid 800x600@56Hz
clock=36
shb=800 ehb=1024 ht=1024
vrs=601 vre=603 vt=625
hsync=+ vsync=+
edid 800x600@60Hz
clock=40
shb=800 ehb=1056 ht=1056
vrs=601 vre=605 vt=628
hsync=+ vsync=+
edid 800x600@72Hz
clock=50
shb=800 ehb=1040 ht=1040
vrs=637 vre=643 vt=666
hsync=+ vsync=+
edid 800x600@75Hz
clock=49.5
shb=800 ehb=1056 ht=1056
vrs=601 vre=604 vt=625
hsync=+ vsync=+
edid 1024x768@60Hz
clock=65
shb=1024 ehb=1344 ht=1344
vrs=771 vre=777 vt=806
hsync=- vsync=-
edid 1024x768@70Hz
clock=75
shb=1024 ehb=1328 ht=1328
vrs=771 vre=777 vt=806
hsync=- vsync=-
edid 1024x768@75Hz
clock=78.75
shb=1024 ehb=1312 ht=1312
vrs=769 vre=772 vt=800
hsync=+ vsync=+
edid 1280x1024@75Hz
clock=135
shb=1280 ehb=1688 ht=1688
vrs=1025 vre=1028 vt=1066
hsync=+ vsync=+
edid 1680x1050@60Hz
clock=146.25
shb=1784 ehb=1960 ht=2240
vrs=1053 vre=1059 vt=1089
hsync=- vsync=+
[2] A small change to vgavesa.c allowed for the larger framebuffer on
this NVidia card:
http://code.google.com/p/plan9front/source/detail?r=18198808ff
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: [9fans] Intel X4500 Integrated Graphics support
2011-12-20 14:47 ` Stanley Lieber
@ 2011-12-25 16:09 ` Aram Hăvărneanu
0 siblings, 0 replies; 12+ messages in thread
From: Aram Hăvărneanu @ 2011-12-25 16:09 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
Stanley Lieber wrote:
> erik quanstrom wrote:
>> i think most people are using vesa. unfortunately
>> that limits one to 4:3 graphics modes.
>
> Some card/monitor combinations seem to support other aspect ratios
> that are technically outside of the VESA spec
I confirm, I use 1920x1280x32 with vesa. I'm not sure about the video
card, don't care about these things. It might be some sort of Nvidia
Quadro.
With such a high resolution vesa is slow, but very usable.
--
Aram Hăvărneanu
^ permalink raw reply [flat|nested] 12+ messages in thread
[parent not found: <CAHfqX-qFqRSY9itF3dWzWn-11vmSJrFAjG=j+yC2yjQJHxnnDw@mail.gmail.c>]
* Re: [9fans] Intel X4500 Integrated Graphics support
[not found] ` <CAHfqX-qFqRSY9itF3dWzWn-11vmSJrFAjG=j+yC2yjQJHxnnDw@mail.gmail.c>
@ 2011-12-20 15:03 ` erik quanstrom
2011-12-20 15:32 ` Stanley Lieber
0 siblings, 1 reply; 12+ messages in thread
From: erik quanstrom @ 2011-12-20 15:03 UTC (permalink / raw)
To: 9fans
> Some card/monitor combinations seem to support other aspect ratios
> that are technically outside of the VESA spec. For example, my NVidia
> GeForce 8400GS coupled with an NEC AccuSync AS221WM 22" via DVI-D[1]
> happily runs[2] at the monitor's native resolution of 1680x1050 with
> VESA, which is 16:10. I was also able to achieve 1680x1050 on the
> AS221WM with an Intel GMA 3000 via VGA. The deciding factor seems to
> be whatever modes are contained in the specific VESA BIOS that is in
> your specific video card.
i never considered the advertized modes might depend on
the monitor connected. have you observed this?
also, the old code set paddr to the start of the bar, your code
sets it to whatever the vbe mode returned. have you observed
this, too?
- erik
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: [9fans] Intel X4500 Integrated Graphics support
2011-12-20 15:03 ` erik quanstrom
@ 2011-12-20 15:32 ` Stanley Lieber
0 siblings, 0 replies; 12+ messages in thread
From: Stanley Lieber @ 2011-12-20 15:32 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
On Tue, Dec 20, 2011 at 9:03 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>
> i never considered the advertized modes might depend on
> the monitor connected. have you observed this?
Yes. I have a few combinations of VGA-VGA, DVI-DVI, VGA-DVI, DVI-HDMI,
etc., cables, and, using the same card and monitor, I get different
output from aux/vga -p depending upon the combination. I've observed
this with other cards and monitors as well. It seems like the card
firmware does some kind of autodetection to figure out which modes it
wants to present.
> also, the old code set paddr to the start of the bar, your code
> sets it to whatever the vbe mode returned. have you observed
> this, too?
Attempting 1680x1050x32 was hanging my machine[1]. Cinap identified
the problem and provided the fix. I can't speak much on the code as I
don't really understand the mechanism.
-sl
[1] http://www.flickr.com/photos/stanleylieber/6403274727/in/set-72157627976638191/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [9fans] Intel X4500 Integrated Graphics support
2011-12-20 13:52 ` erik quanstrom
2011-12-20 14:47 ` Stanley Lieber
[not found] ` <CAHfqX-qFqRSY9itF3dWzWn-11vmSJrFAjG=j+yC2yjQJHxnnDw@mail.gmail.c>
@ 2011-12-21 4:56 ` Akshat Kumar
[not found] ` <CABwSpPArfJpw9bJvvk7ymGUcX31ydFzJLfvmBf=N1xQgTht=VQ@mail.gmail.c>
3 siblings, 0 replies; 12+ messages in thread
From: Akshat Kumar @ 2011-12-21 4:56 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
I have tried 1280x800x32 on the laptop and
1280x1024x16 and 1280x1024x32 on a monitor
connected to the laptop via VGA. In all cases,
the result is a very, very incredibly slow and
choppy rio.
I'm using the stock Plan 9 kernel (with a patch
for IL (*shakes fist at the 'Labs*)).
ak
On Tue, Dec 20, 2011 at 5:52 AM, erik quanstrom <quanstro@quanstro.net> wrote:
> i think most people are using vesa. unfortunately
> that limits one to 4:3 graphics modes.
>
> which kernel are you using? if you get write-combining
> going through pat or mtrr, and use double buffering,
> things should be pretty good on most hardware.
> (true of the kernels you could download today.)
>
> - erik
>
^ permalink raw reply [flat|nested] 12+ messages in thread[parent not found: <CABwSpPArfJpw9bJvvk7ymGUcX31ydFzJLfvmBf=N1xQgTht=VQ@mail.gmail.c>]
* Re: [9fans] Intel X4500 Integrated Graphics support
[not found] ` <CABwSpPArfJpw9bJvvk7ymGUcX31ydFzJLfvmBf=N1xQgTht=VQ@mail.gmail.c>
@ 2011-12-21 5:01 ` erik quanstrom
[not found] ` <CABwSpPDZSpu583fzW=TgpCGw9xQ5hVuX5DTpNjfEzKS3TnTa1A@mail.gmail.c>
0 siblings, 1 reply; 12+ messages in thread
From: erik quanstrom @ 2011-12-21 5:01 UTC (permalink / raw)
To: akumar, 9fans
On Tue Dec 20 23:57:09 EST 2011, akumar@mail.nanosouffle.net wrote:
> I have tried 1280x800x32 on the laptop and
> 1280x1024x16 and 1280x1024x32 on a monitor
> connected to the laptop via VGA. In all cases,
> the result is a very, very incredibly slow and
> choppy rio.
>
> I'm using the stock Plan 9 kernel (with a patch
> for IL (*shakes fist at the 'Labs*)).
there could be many things wrong. if you're having
a mtrr issue, then 9atom should fix it, since i gave mtrrs
a pass since they are depricated and require hooks into
the clock interrupt.
but i'm wondering if rio is the only thing that's choppy
on your system. why don't you send pci output? it's too
bad you don't have the 9atom mods to /dev/irqalloc that
would let us know if you have a ringing irq.
- erik
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2012-01-23 15:48 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-12-20 7:40 [9fans] Intel X4500 Integrated Graphics support Akshat Kumar
2011-12-20 13:52 ` erik quanstrom
2011-12-20 14:47 ` Stanley Lieber
2011-12-25 16:09 ` Aram Hăvărneanu
[not found] ` <CAHfqX-qFqRSY9itF3dWzWn-11vmSJrFAjG=j+yC2yjQJHxnnDw@mail.gmail.c>
2011-12-20 15:03 ` erik quanstrom
2011-12-20 15:32 ` Stanley Lieber
2011-12-21 4:56 ` Akshat Kumar
[not found] ` <CABwSpPArfJpw9bJvvk7ymGUcX31ydFzJLfvmBf=N1xQgTht=VQ@mail.gmail.c>
2011-12-21 5:01 ` erik quanstrom
[not found] ` <CABwSpPDZSpu583fzW=TgpCGw9xQ5hVuX5DTpNjfEzKS3TnTa1A@mail.gmail.c>
[not found] ` <cc5ef0c6b767d54f21b7a4f7e565a933@brasstown.quanstro.net>
2011-12-23 4:27 ` Akshat Kumar
2011-12-30 16:32 ` erik quanstrom
2012-01-21 22:55 ` Akshat Kumar
[not found] ` <CABwSpPDM+q2+zoo_ORqRfJ8RbTNhOkiTcPw83E1u3DtoXm-PWQ@mail.gmail.c>
2012-01-23 15:48 ` erik quanstrom
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).