From: Ian R. <id...@us...> - 2004-03-12 23:30:57
|
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? > > Is there any easy way to find out from the card itself. I've got a PCI > 220 here. Dunno. > The drivers I've touched which handle PCI bus (VIA, S3 (trying to > ressurect it) and SIS6326 (buggy still)) all use their own memory > allocators for the PCI side and don't go into PCIGART world. SiS > supports only linear textures/buffers in main memory via PCI which is a > problem to use because of the Linux memory allocator. From reading some other messages in the archives, I think the G200 and G400, at the very least, work that way. That basically limits the driver to using 64k chunks, right? I don't think that should be a problem for vertex data, command buffers, and texture uploads. It just means you lose the ability to texture from PCI memory. I'm willing to make that sacrifice ATM. |