Hmm, I was able to get the driver working, but I have some more
questions; let me first give you some background.
My box is a Dell PowerEdge 1600SC server with an integrated ATI Rage XL:
$ sudo lspci -vs 0e
00:0e.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
Subsystem: Dell Device 0135
Flags: bus master, VGA palette snoop, stepping, medium devsel,
latency 32
Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
I/O ports at e800 [size=256]
Memory at fe121000 (32-bit, non-prefetchable) [size=4K]
[virtual] Expansion ROM at c0000000 [disabled] [size=128K]
Capabilities: [5c] Power Management version 2
I'm fairly sure it has 8M of video RAM -- not sure why that says 16M.
Perhaps that's just the size of the window but only 8M is physically
present.
I have compiled the kernel mach64 DRM driver from Archlinux, posted by
Alexander Lam (many thanks for that), and it seems I can enable DRI
with 1024x768x16, but I get the following (EE):
(II) MACH64(0): [DRI] installation complete
(II) MACH64(0): [drm] Added 128 16384 byte DMA buffers
(II) MACH64(0): [drm] Mapped 128 DMA buffers at 0xb66db000
(EE) MACH64(0): [drm] Couldn't find IRQ for bus id 0:14:0
(II) MACH64(0): [drm] Falling back to irq-free operation
(II) MACH64(0): Direct rendering enabled
Given the (II) following it, this seems to be more of a warning.
Indeed, the device doesn't have an IRQ in lspci or /proc/interrupts.
Is there anything I can do about this? Any particular performance
issues I should see due to lack of an IRQ?
The other question is regarding running DRI with a higher resolution,
1280x1024x16 (since that's my LCD's native resolution ;-) ). I get the
following:
(II) MACH64(0): [drm] Will request asynchronous DMA mode
(==) MACH64(0): [drm] Using 2 MB for DMA buffers
(II) MACH64(0): [pci] ring handle = 0x36224000
(II) MACH64(0): [pci] Ring mapped at 0xb699d000
(II) MACH64(0): [drm] register handle = 0xfe121000
(II) MACH64(0): [dri] Visual configs initialized
(II) MACH64(0): [dri] Block 0 base at 0xfe121400
(WW) MACH64(0): Not enough memory for local textures, disabling DRI
(II) MACH64(0): [drm] removed 1 reserved context for kernel
(II) MACH64(0): [drm] unmapping 8192 bytes of SAREA 0xf8035000 at 0xb69a1000
(II) MACH64(0): [drm] Closed DRM master.
(II) MACH64(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
[...]
(II) MACH64(0): Direct rendering disabled
Is there any way to get DRI with this higher resolution? Perhaps by
reducing the (2 MB) DMA allocation?
It seems to me like 1280x1024x16 / 8 = 2.5 MBytes should fit pretty
easily.. why do I seem to need a lot more memory for this resolution?
And lastly, with 1024x768x16 and DRI enabled, I still see (relatively)
high CPU usage by Xorg when dragging windows around (70% on a 2 GHz
P4).. any hints on reducing that?
Thanks,
Catalin
2010/2/7 Catalin Patulea <c...@vv.carleton.ca>:
> 2010/2/7 Kristian Høgsberg <k...@bitplanet.net>:
>> They live in the kernel.
> I can't seem to find them there.. perhaps I'm looking in the wrong place:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree;f=drivers/gpu/drm
>
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
