On Tue, 16 Jan 2001, Tigran Aivazian wrote:
> Fixing this requires either a new filesystem type (drifs) or
> (simpler!) redesigning dri to separate common things into a separate
> dri_core thing shared amongst them.
just for completeness -- there is the 3rd option -- one could just fix the
hack
Hi Bobo,
To fix this just link in only the support that corresponds to your
hardware. The design of dri is such that (one could paraphrase) each
driver-specific part includes its own copy of what should be
"driver-independent shared dri_core engine" (e.g. proc handling stuff).
Fixing this
Hi Bobo,
To fix this just link in only the support that corresponds to your
hardware. The design of dri is such that (one could paraphrase) each
driver-specific part includes its own copy of what should be
"driver-independent shared dri_core engine" (e.g. proc handling stuff).
Fixing this
On Tue, 16 Jan 2001, Tigran Aivazian wrote:
Fixing this requires either a new filesystem type (drifs) or
(simpler!) redesigning dri to separate common things into a separate
dri_core thing shared amongst them.
just for completeness -- there is the 3rd option -- one could just fix the
hack
Hi,
I'm running kernel 2.4.0 on Redhat 7.0. I tried to get direct
rendering running (it failed, but that's another story). Today I
noticed something strange in /proc: dri appears there 4 times.
ls /proc:
...
-r--r--r--1 root root0 Jan 16 08:57 dma
dr-xr-xr-x3 root
5 matches
Mail list logo
