В сообщении от 17 Сентябрь 2003 19:40 Alex Deucher написал:
> I don't think the drivers S3 released will work properly on savage3D
> based cores like the MX/IX chips. They were designed for savage4 cores
> like the prosavage and twister. You may want to compare the S3 driver
> to the utah-glx sav
В сообщении от 17 Сентябрь 2003 19:16 Rafael Maximo написал:
> I'm getting a similar problem on my xfree86 4.3.0, the 2D screen is
> corrupted but it looks better than yours :)
the screen corruption represented on my screenshot happens only whith
enlightenment window manager other WMs haven't th
Title: the relationship between Local Graphics Memory and Frame buffer?
Now I am reading intel northbridge 440BX spec(look page 88:Memory System Address Space)
And i have a box with 440BX
I look /proc/iomem,i find that Framebuffer's size is 16MB(i open vesa before kernel using vga=788)
And
I forgot to mention, i also want an opinion about this line on XFree86
log:
(II) SAVAGE(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0,
hwp->PIOOffset is 0x
This line is repeated several times and I would like to know what
does it mean. Is this normal?
bye.
At 11:06 PM 17/9/2003, Rafael Maximo w
I know that the 2D driver is in
xc/programs/Xserver/hw/xfree86/drivers/savage but there are a lot of files
there and i was expecting something more specific :) i'm trying to avoid a
few weeks of studying 2D driver :)
I compiled it from savage-1_0_0_-branch and i think it's with
On Wed, 2003-09-17 at 19:06, Rafael Maximo wrote:
> Hi,
>
> Some of you already know that i'm trying to work on the savage
> driver, i'm working on the 3D driver (/lib/GL/mesa/src/drv) and now it is
> compiling and i'll test it but i got some other problems. After compiling
> everythin
for 3D, what version of mesa are you using? are you using the right
libGL?
For 2D look in xc/programs/Xserver/hw/xfree86/drivers/savage
Try the 2D driver with 3D disabled and see if you still get corruption.
it may be that the 3D side is stomping on the something from the 2D
side.
Alex
--- Ra
Hi,
Some of you already know that i'm trying to work on the savage
driver, i'm working on the 3D driver (/lib/GL/mesa/src/drv) and now it is
compiling and i'll test it but i got some other problems. After compiling
everything (2D, 3D, kernel modules, etc.) my screen on xfree 4.3.0 is a
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-17-09 10:37 ---
ACPI is also alloting IRQs.
I don't think the drivers S3 released will work properly on savage3D
based cores like the MX/IX chips. They were designed for savage4 cores
like the prosavage and twister. You may want to compare the S3 driver
to the utah-glx savage driver. the utah driver only supports savage3D
cores, but not s
I'm getting a similar problem on my xfree86 4.3.0, the 2D screen is
corrupted but it looks better than yours :) but here glxinfo reports Direct
Rendering disable. Your XFree86 log shows something not good:
(--) SAVAGEInitMC: There is no enough memory!
Someone also reported a similar problem usin
В сообщении от 17 Сентябрь 2003 16:44 Dimitry N. Naldaev написал:
I'v practicaly duplicateded message of Rick Harris two week ago
Sorry
> After that I force init DRI by doing
>
[ snip ]
>
> but when I start glxgears Xserver crashes
> full X log also attached
| (--) SAVAGE(0): SavageMatchBiosM
GART range a physical bus address including a size value,
which will get fixed up by PCI config process in BIOS.
It should not need any touching at a later time on sane systems.
It can be reprogrammed in most cases but only with full system awareness.
I dont know a regular reason why to do that on
The mainboard chipset provides two things in respect to the keyword AGP.
- a high speed bus interface to the graphics controller
- a memory paging uint exposed to the graphics controller and the CPU
the 2nd is just a remapped view of the main memory,
resembling some/any page of main memory in a
Martin Spott <[EMAIL PROTECTED]> wrote:
> I just did a small test with FlightGear against the recent CVS checkout
> from freedesktop and I'm delighted. Everything works as expected,
I forgot to mention, that I'm running stock DRM kernel modules
from Linux-2.6.0-test5 (Radeon7500),
Martin.
--
I find aperture base address in North bridge PCI offset 0x10h,for example,in my
box,it is 0xb0 00 00 00
the base address is bus address or virtual address?
It points to somewhere in system memory?
-原始邮件-
发件人: Ryan Underwood [mailto:[EMAIL PROTECTED]
发送时间: 2003年9月17日 15:51
收件人: [EMAIL
On Tue, 2003-09-16 at 06:42, Daniel Vogel wrote:
> FWIW, a G450 is below minimum system requirements and I'm curious to hear
> how well cards like the Radeon 8500, which currently is the fastest DRI
> accelerated card out there if I'm not mistaken, handle running the game.
I've tried the demo (ut
[This e-mail has been automatically generated.Please do not reply to this
email- if you want to comment on the bug, go to the URL shown below and enter
your comments there.]
You have one or more bugs assigned to you in the Bugzilla
bugsystem (http://bugs.xfree86.org/) that require
attention
I just did a small test with FlightGear against the recent CVS checkout
from freedesktop and I'm delighted. Everything works as expected,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
-
Hi,
On Wed, Sep 17, 2003 at 03:30:09PM +0800, "Tao, Qian ( IES)" wrote:
>I am a newbee in dri.
>Now i am reading agp source code in linux kernel.
>I am not clear about 'Graphics Aperture'
>I download AGP spec 2.0,but it don't say a word about it.
>what's the relationship b
Title: what's the meaning of 'Graphics Aperture' in AGP?
I am a newbee in dri.
Now i am reading agp source code in linux kernel.
I am not clear about 'Graphics Aperture'
I download AGP spec 2.0,but it don't say a word about it.
what's the relationship between the aperture with graphics me
21 matches
Mail list logo
