PCI MGA support (was Re: [Dri-devel] mga cvs changes)

2004-03-12 Thread Ian Romanick
Ville Syrjälä wrote: On Tue, Nov 11, 2003 at 10:50:01AM -0800, Ian Romanick wrote: I must say that I am very impressed with how far the MGA driver has come since you started working on it. Now the only thing that's missing is support for PCI cards. ;) A quick fix would be simply enabling PCI ca

Re: PCI MGA support (was Re: [Dri-devel] mga cvs changes)

2004-03-12 Thread Alex Deucher
--- Ian Romanick <[EMAIL PROTECTED]> wrote: > Ville Syrjälä wrote: > > On Tue, Nov 11, 2003 at 10:50:01AM -0800, Ian Romanick wrote: > > > >>I must say that I am very impressed with how far the MGA driver has > come > >>since you started working on it. Now the only thing that's missing > is > >

Re: PCI MGA support (was Re: [Dri-devel] mga cvs changes)

2004-03-12 Thread Alan Cox
On Gwe, 2004-03-12 at 21:40, Ian Romanick wrote: > MGADRIPciInit wouldn't be a complete duplication of MGADRIAgpInit > because I don't intend to (initially) support PCIGART. Even when > PCIGART is supported, not all chips in the MGA family support it. Is > the PCI G450 the only one? Is there

Re: PCI MGA support (was Re: [Dri-devel] mga cvs changes)

2004-03-12 Thread Ian Romanick
Alex Deucher wrote: There was a website with support for the PCI G450 (for alpha I think): http://www.instmath.rwth-aachen.de:8000/linux/G450-PCI/ However it seems to be down at the moment. Someone on the ML knew the guy who was doing the work. perhaps they an find out the state of it. It's been

Re: PCI MGA support (was Re: [Dri-devel] mga cvs changes)

2004-03-12 Thread Ian Romanick
Alan Cox wrote: On Gwe, 2004-03-12 at 21:40, Ian Romanick wrote: MGADRIPciInit wouldn't be a complete duplication of MGADRIAgpInit because I don't intend to (initially) support PCIGART. Even when PCIGART is supported, not all chips in the MGA family support it. Is the PCI G450 the only one? I

Re: PCI MGA support (was Re: [Dri-devel] mga cvs changes)

2004-03-12 Thread Alex Deucher
--- Ian Romanick <[EMAIL PROTECTED]> wrote: > Alex Deucher wrote: > > > There was a website with support for the PCI G450 (for alpha I > think): > > http://www.instmath.rwth-aachen.de:8000/linux/G450-PCI/ > > However it seems to be down at the moment. Someone on the ML knew > the > > guy who was

Re: PCI MGA support (was Re: [Dri-devel] mga cvs changes)

2004-03-12 Thread Ian Romanick
Alex Deucher wrote: --- Ian Romanick <[EMAIL PROTECTED]> wrote: Alex Deucher wrote: As I recall the G450-PCI cards were just AGP chips with an agp to pci bridge. Perhaps you need to hack up an agpgart driver for the bridge? Also, for the pci g450, matrox only supported 3D on motherboards with in

Re: PCI MGA support (was Re: [Dri-devel] mga cvs changes)

2004-03-12 Thread Benjamin Herrenschmidt
> Then comes the kernel. :( I started looking that the ILOAD code in > mga_state.c. Basically, it looks like everything assume the source > buffers are in AGP space. I'm guessing that I could just look at the > flags field in the drm_device_dma structure and only set the > MGA_SRCACC_AGP bi

Re: PCI MGA support (was Re: [Dri-devel] mga cvs changes)

2004-03-13 Thread Ville Syrjälä
On Fri, Mar 12, 2004 at 01:40:30PM -0800, Ian Romanick wrote: > > I want to initially support this by just "disabling" AGP texturing. I > looked in the DRI driver, and it looks like this can be done with some > trivial changes in mga_xmesa.c. Basically, the code just needs to > handle the cas

Re: PCI MGA support (was Re: [Dri-devel] mga cvs changes)

2004-03-13 Thread Ville Syrjälä
On Fri, Mar 12, 2004 at 03:39:50PM -0800, Alex Deucher wrote: > > > As I recall the G450-PCI cards were just AGP chips with an agp to > > pci > > > bridge. Perhaps you need to hack up an agpgart driver for the > > bridge? > > > Also, for the pci g450, matrox only supported 3D on motherboards > >

Re: PCI MGA support (was Re: [Dri-devel] mga cvs changes)

2004-03-29 Thread Ian Romanick
Benjamin Herrenschmidt wrote: Then comes the kernel. :( I started looking that the ILOAD code in mga_state.c. Basically, it looks like everything assume the source buffers are in AGP space. I'm guessing that I could just look at the flags field in the drm_device_dma structure and only set th

Re: PCI MGA support (was Re: [Dri-devel] mga cvs changes)

2004-03-29 Thread Benjamin Herrenschmidt
> > The current PCI interface to the iommu doesn't allow you to explicitely > > ask an sg list to be force-merged into a single segment though that > > could be added via some platform hooks. That would probably work if > > that is the only DMA allocation you do on this TCE table. Those machines >