Comme=
nt # 28
on bug 11078=
1
from =
Richard Thier
Hi Rui!
We should also thank Marek for him proposing a possible fix. I am currently
creating a "less hacky" solution based on that attachment and a b=
etter idea to
not always force VRAM domain, but only if the r300 caller codes ask "V=
RAM or
something" and forcing GTT if it asks "GTT or something - but not=
VRAM". This
basically lead to the driver favoring the domain choice to be in VRAM, but
still supporting other things if the caller asks other domains directly.
Also incorporating the parts that Marek proposes is much better and cleaner
than my hack that just sets the flag right before it is read.
After I am completed with these changes and their testing I will publish it
here and only maybe then have any time to compile an x86_64 version for oth=
er
people. I highly suggest however for you and others to just grab the latest
revision from git and apply the changesets until the solution arrives in me=
sa
releases. I am on a single core, 32bit laptop with 1512-128MB of memory I g=
ot
in 2007 and I think most of the hardware is like from 2005 technology in it=
so
I might be some among the slowest cross-compiling person so please give a s=
hot
to put together a build environment yourself.
It is not that hard to build mesa, this was my first time doing so too! Just
believe in yourself and read the nice docs on the mesa page about building =
with
meson. If you have any questions of the build process look around phoronix =
or
mesa docs and forums or if you give up just you can ask any people. Even I =
can
help now and you will be able too after you build yourself once ;-)