On Fri, Mar 29, 2019 at 05:33:41PM -0500, Douglas R. Reno via blfs-dev wrote:
>
> On 3/29/19 5:14 PM, Ken Moffat via blfs-dev wrote:
> > >
> >
> > AFAICS, all that changes is which drivers get compiled : specifying
> > them the way we currently do gives a small subset for modern
> > machines, letting 'auto' decide gives all of them.
> >
> > But I'm coming to the conclusion that most people do not want to
> > build everything, and probably an option noting that "if those three
> > defines are not set then all drivers and platforms will be built"
> > is probably best.
> >
> > ĸen
>
> I'd like to suggest moving to auto actually. I can think of multiple
> advantages for this, but only one disadvantage - a larger build size. At the
> minimum, we should add virtio to the list of supported drivers - that's the
> infrastructure that most VMs use nowadays.
>
I'm still getting my head around the options (and probably won't try
any more test builds for a couple of days), but I'm all infavour of
listing all the available **x86** drivers and platforms, to let
people choose (e.g. if I reinstate my Kaveri which has slowish DDR3
RAM and lacks L3 cache, I really don't want to build things it can't
use).
I think 'virtio' is a DRI driver and should be added to the list of
what is available. I'm not sure that mentioning the surfaceless,
haiku, android platforms is useful. And several of the gallium
drivers don't build on X86 (e.g. tegra, etnaviv).
I think it would be nice to cut this down to just X86 (sorry, ARM
users) with a note that other drivers and platforms exist for other
architectures and systems (so, android drops into "other systems" -
it is linux, but not as we know it).
Unfortunately, the link to Mesa's Supported Systems and Drivers
appears to be pretty old, and hard to navigate for details of the
current drivers.
As a *guess*, if building *only* for a VM, I imagine the useful
settings would be:
-Ddri-drivers="swrast,virtio"
-Dgallium-drivers="svga,swrast"
with platforms not specified (i.e. auto).
And for VMs, I guess that gallium-nine is irrelevant.
Do those suggestions sound sensible ?
ĸen
--
It is said that there are two great unsolved problems in computer
science: naming, cache invalidation, and off-by-one errors.
-- Ben Bullock
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
