Commen=
t # 12
on bug 98964<=
/a>
from Zolt=C3=A1n B=C3=B6sz=C3=B6rm=C3=A9n=
yi
(In reply to Emil Velikov from comment #11)
> Above all: yes using hard links is nasty.
Thanks for confirming. :-)
> If you're having a single (or multiple fixed) GP=
U system then building
> multiple drivers is a _very_ bad idea. If you're doing that for embedd=
ed
> systems then it gets even worse. Thus having separate $driver subpacka=
ges
> makes no sense :-(
I never said it is the same machine all across the board. All of them are
single GPU ones, but historically we have systems with:
AMD RS780
NVIDIA (ION1, ION2 and some third one, for our workload, Nouveau is enough)
AMD Kabini
AMD Kaveri
Intel D525
Most recently Intel J1900
The same OS must run on all of them, so it does make sense to build differe=
nt
drivers into Mesa but it was also a necessity to save space where we can. H=
ence
the symlink solution. Custom made OS based on Yocto.
Even if the hardlinks are used, bitbake in Yocto has a separate packaging s=
tage
after "make install" that copies files instead of moving them so =
even a single
subpackage containing all drivers would end up with broken hardlinks, thus
requiring multiples of what is needed solely for the gallium_dri.so and
mesa_dri_drivers.so megadrivers. Maybe the megadrivers idea is the elephant=
in
the room. I know it was created for a miniscule performance gain.