On Mon, 2003-10-20 at 18:14, Michel Dänzer wrote:
> On Wed, 2003-10-08 at 04:34, Vladimir Dergachev wrote:
> > On Wed, 8 Oct 2003, Michel [ISO-8859-1] Dnzer wrote:
> > 
> > > > > Does the aperture ever (have to) move during the X server life though?
> > > >
> > > > I would not care. However, I know that at least Window 98 drivers have
> > > > default position (0) unless capture is enabled. Also, I suspect that when
> > > > one calls Video BIOS with framebuffer position anywhere other than 0 the
> > > > BIOS then toggles the hard reset line.
> > >
> > > Why? (CC'ing Hui Yu, who should be able to comment on this)
> > 
> > No idea why it does it.
> 
> Any news on this? I haven't taken this into account in
> 
> http://penguinppc.org/~daenzer/DRI/radeon-memory-transition.diff
> 
> which is my first take on this. As discussed before, this should handle
> any combination of new and old components gracefully, in particular it
> fixes up the client state in the DRM if necessary (and in the process
> always checks them and returns an error if they lie outside the
> framebuffer or GART apertures), so old 3D drivers work with the new 2D
> driver and DRM.

One small problem in radeon_fb_location ioctl:  For OS-independence, so
far filp has been an opaque void pointer.  I'm wondering if maybe we
want to pass the drm_file_t * as part of DRM_IOCTL_ARGS, or just
resurrect DRM_PRIV to get the drm_file_t * based on filp.

(The problem here is that *BSD don't easily have the per-open device
private area, so we use a hack in drm_fops.h to simulate it)

-- 
Eric Anholt                                [EMAIL PROTECTED]          
http://people.freebsd.org/~anholt/         [EMAIL PROTECTED]




-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to