From: Alan H. <aho...@va...> - 2001-05-23 14:44:52
|
This will be fixed in the next release. Either that or grab the current CVS. Alan. On Wed, May 23, 2001 at 02:29:33PM +0100, Stephen Davies wrote: > Hi, > > Beginners question, I suspect, but: > > I have a Voodoo3 3000 board, 16MB of RAM. I run it in 1024x768x16 And I'm > trying to display 768x576 video through Xvideo. > > It appears that my board is running out of video ram. Is that possible? > > Relevant XFree boot messages look like so: > > > (II) TDFX(0): Softbooting the board (through the int10 interface). > (II) TDFX(0): Primary V_BIOS segment is: 0xc000 > (II) TDFX(0): Softbooting the board succeeded. > (**) TDFX(0): Depth 16, (--) framebuffer bpp 16 > (==) TDFX(0): RGB weight 565 > (==) TDFX(0): Default visual is TrueColor > (--) TDFX(0): Chipset: "3dfx Voodoo3" > (--) TDFX(0): Linear framebuffer at 0xE2000000 > (--) TDFX(0): MMIO registers at addr 0xDE000000 > (--) TDFX(0): PIO registers at addr 0xD800 > (--) TDFX(0): VideoRAM: 16384 kByte Mapping 32768 kByte > > (II) Loading sub module "int10" > (II) LoadModule: "int10" > (II) Reloading /usr/X11R6/lib/modules/linux/libint10.a > (II) TDFX(0): initializing int10 > (II) TDFX(0): Primary V_BIOS segment is: 0xc000 > (II) TDFX(0): VESA BIOS detected > (II) TDFX(0): VESA VBE Version 3.0 > (II) TDFX(0): VESA VBE Total Mem: 16384 kB > (II) TDFX(0): VESA VBE OEM: 3dfx Interactive, Inc. > (II) TDFX(0): VESA VBE OEM Software Rev: 1.0 > (II) TDFX(0): VESA VBE OEM Vendor: Elpin Systems, Inc. > (II) TDFX(0): VESA VBE OEM Product: 3dfx Avenger > (II) TDFX(0): VESA VBE OEM Product Rev: Version 1.00 > > (==) TDFX(0): Write-combining range (0xe2000000,0x2000000) > (II) TDFX(0): Changing back offset from 0x00cff000 to 0x00cfe000 > (II) TDFX(0): Textures Memory 9.83 MB > (II) TDFX(0): Cursor Offset: [0x00000000,0x00001000) > (II) TDFX(0): Fifo Offset: [0x00001000, 0x00100000) > (II) TDFX(0): Front Buffer Offset: [0x00100000, 0x00329000) > (II) TDFX(0): Texture Offset: [0x00329000, 0x00CFE000) > (II) TDFX(0): BackOffset: [0x00CFE000, 0x00E7E000) > (II) TDFX(0): DepthOffset: [0x00E7F000, 0x00FFF000) > (II) TDFX(0): 338 lines of offscreen memory available for 2D and video > (II) TDFX(0): [drm] loaded kernel module "tdfx" > (II) TDFX(0): [drm] created "tdfx" driver at busid "PCI:1:0:0" > (II) TDFX(0): [drm] added 4096 byte SAREA at 0xccf26000 > (II) TDFX(0): [drm] mapped SAREA 0xccf26000 to 0x40016000 > (II) TDFX(0): [drm] framebuffer handle = 0xe2000000 > (II) TDFX(0): [drm] added 1 reserved context for kernel > (II) TDFX(0): [drm] Registers = 0xde000000 > (II) TDFX(0): visual configs initialized > (II) TDFX(0): Using XFree86 Acceleration Architecture (XAA) > Screen to screen bit blits > Solid filled rectangles > 8x8 mono pattern filled rectangles > Indirect CPU to Screen color expansion > Solid Lines > Dashed Lines > Offscreen Pixmaps > Driver provided NonTEGlyphRenderer replacement > Setting up tile and stipple cache: > 16 128x128 slots > (==) TDFX(0): Backing store disabled > > > How do I interpret this all correctly? > > 338 "lines" of memory for video? Does that mean 338 lines by 1024 > pixels? That's 346112 pixels - or maximum of 450x768 (if you can even > remap the memory in that way?). > > How do I increase the memory for video? I certainly don't need nearly 10 > megs of texture memory, I don't think (I'm not doing any 3d - I just want > the XVideo support - so can I trade? > > Regards and thanks for any help or suggestions, > > Steve Davies > > > > > > _______________________________________________ > Dri-users mailing list > Dri...@li... > http://lists.sourceforge.net/lists/listinfo/dri-users |