Hi !
The radeon DRM has some interesting bug that paul and I discovered to
cause all sort of problems like crashing the machine on suspend/resume
(go figure ...) etc...
dev_priv->gart_vm_start = dev_priv->fb_location
+ RADEON_READ( RADEON_CONFIG_APER_SIZE )
On Mon, May 02, 2005 at 01:27:55PM -0400, The Slash wrote:
> well since there is no DRI support for the SiS m650, and according to
> what I heard there never will be, I have decided to write my own. I
> have never written my own driver before, and I'm a little confused as
> to where to begin. I kno
Hi,
I'm having a problem with the DRI driver for SiS 730S...
I've set it up using the howto at http://www.winischhofer.at/linuxsisvga.shtml,
except i've set
Option "MaxXFBMem" "4096"
since there only seems to be 8mb videoram, and if the framebuffer gets it all
DRI can't do anything. There is
On Monday 02 May 2005 13:27, The Slash wrote:
> well since there is no DRI support for the SiS m650, and according to
> what I heard there never will be, I have decided to write my own. I
> have never written my own driver before, and I'm a little confused as
> to where to begin. I know that SiS do
On Monday 02 May 2005 09:56, David Kesselring wrote:
> When looking at the Mesa source I see processor specific directories in
> Mesa-x.x.x/src/mesa. I see x86,sparc,ppc. What happens in a build for ARM?
The processor-specific subdirs are only built if you selected that processor's
config at make
Am Montag, 2. Mai 2005 16:56 schrieb Brian Paul:
> This weekend I finished updating the DRI drivers to work with the new
> framebuffer/renderbuffer changes. My DRI test system is terribly out
> of date so I haven't run any tests. I'm tempted to just check in the
> changes now and help people fix
On 5/2/05, David Kesselring <[EMAIL PROTECTED]> wrote:
> When looking at the Mesa source I see processor specific directories in
> Mesa-x.x.x/src/mesa. I see x86,sparc,ppc. What happens in a build for ARM?
It uses the c version not the asm optimized functions. If i'm not wrong
arm proc doesn't hav
This weekend I finished updating the DRI drivers to work with the new
framebuffer/renderbuffer changes. My DRI test system is terribly out
of date so I haven't run any tests. I'm tempted to just check in the
changes now and help people fix any problems that arise, rather than
spend a few days
On 5/2/05, The Slash <[EMAIL PROTECTED]> wrote:
> well since there is no DRI support for the SiS m650, and according to
> what I heard there never will be, I have decided to write my own. I
> have never written my own driver before, and I'm a little confused as
> to where to begin. I know that SiS
When looking at the Mesa source I see processor specific directories in
Mesa-x.x.x/src/mesa. I see x86,sparc,ppc. What happens in a build for ARM?
Thanks,
David Kesselring
Atmel MMC
[EMAIL PROTECTED]
919-462-6587
---
This SF.Net email is spons
well since there is no DRI support for the SiS m650, and according to
what I heard there never will be, I have decided to write my own. I
have never written my own driver before, and I'm a little confused as
to where to begin. I know that SiS does not normally distribute there
hardware specs, so i
11 matches
Mail list logo
