eta at lclark.edu
Thu Aug 4 18:48:33 PDT 2005
LÏ . ÚÄ .. MÏ èCVS MÏ . LÏ .. NÏ
Repository OÏ ÔEntries he 3d and optionally 2d engines for command
> > submission, DMA, interrupt handling, etc. radeon.(k)o for all radeon
> > chips. resides in your kernel module tree.
> > Driver is maintained in dri cvs
> I see. I'd read this distinction before, but never with specific examples.
> It's the DDX part I was hitherto unclear on. Thanks for the elucidation.
> If I understand then, prior to the r300 driver, I would have been using
> the radeon DDX driver, which is what the 'Driver "radeon"' line is about,
> and all the "DRI" lines in xorg.conf are to trigger the loading of the
> appropriate DRI library. Which library is to be loaded isn't explicitly
> specified anywhere so it must figure that out internally. Is that right?
that's correct. you don't specify the 3d driver anywhere. the DDX
actually picks the right one which is then loaded by libGL when a GL
client accesses it.
> Am I to understand then that before the r300 library, my DRI lines where
> effectively ignored because the internal mechanism whereby it determines
> which DRI library to load found no DRI library matching my hardware?
All you need to enable the DRI from the xorg.conf perspective is:
in your modules section.
> Then the DRM is the same for any radeon card?
yes. radeon.ko. it's usually automatically loaded by the Xserver.
> I do appreciate your enlightening me on this matter. It's something about
> which I've been curious for some time.
More information about the xorg