On Wed, May 11, 2005 at 09:59:25AM -0700, Ian Romanick wrote:
> Ville Syrjälä wrote:
> >On Tue, May 10, 2005 at 02:59:49PM -0700, Ian Romanick wrote:
> 
> >>all or do they just have to be in the same "address space" as the 
> >>primary DMA buffer?
> >
> >If by "address space you mean AGP aperture vs. other memory then no they 
> >don't have be in the same address space. You can choose to use PCI or AGP 
> >transfers every time you submit a new buffer to the hardware.
> 
> Yeah, that's what I meant.  The selection is made by setting bit one of 
> the address to 0 for PCI or 1 for AGP, right?

Yep.

> >>4. AGP textures.  Without an IOMMU, we pretty much have to punt here. 
> >>Performance will be bad, but I can live with that.
> >>
> >>If these assumptions are at least /mostly/ correct, I think I have a 
> >>pretty good idea how I'll change the init process around.  I'd like to, 
> >>basically, pull most of MGADRIAgpInit into the kernel.  There will be a 
> >>single device-specific command called something like 
> >>DRM_MGA_DMA_BOOTSTRAP.  The DDX will pass in the desired AGP mode and 
> >>size.  The DRM will do some magic and fill in the rest of the structure. 
> >>The structure used will probably look something like below.  Notice 
> >>that the DDX *never* needs to know anything about the WARP microcode in 
> >>this arrangement.
> >
> >Why would the DDX need to know anything about the DMA buffers or AGP mode?
> 
> Two reasons, I think.  The DDX tells the DRI driver where this stuff is. 

Ok. I forgot how weird the current system is :(

>  Doesn't the DDX also use the DMA buffers for 2D drawing commands?

Last time I looked the DDX only did MMIO. That was quite a long time ago 
though so maybe things have changed.

-- 
Ville Syrjälä
[EMAIL PROTECTED]
http://www.sci.fi/~syrjala/


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_ids93&alloc_id281&op=click
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to