Hi Richard,

On 19-06-14 11:55, Richard Purdie wrote:
> On Thu, 2019-06-13 at 19:54 +0200, Marco Felsch wrote:
> > Most of the time we are compiling for embedded targets which have
> > dedicated hardware combinations. Enabling swrast by default isn't a
> > good
> > solution for such devices because if the hardware render node has an
> > issue or doesn't support a special format/request Mesa will fallback
> > to
> > the software renderer. This will make it harder to debug performance
> > issues.
> > 
> > A better way is to let the user decide if a software renderer is
> > needed e.g. if the system has no hardware renderer or to have such a
> > fallback device. This way the user knows that the software renderer
> > is
> > enabled.
> > 
> > Signed-off-by: Marco Felsch <[email protected]>
> > ---
> > v3
> > - rebased on current master-next branch
> 
> I think this breaks the autobuilder:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/57/builds/694

thanks for covering that. Why didn't I get a email? Anyway thats
interessting. IMHO it isn't a good solution to rely on that fact that
the package have some 'random' default enabled drivers. Should we fix
the qemu configs or should I add:

PACKAGECONFIG_append_qemuall = " swrast"

Regards,
  Marco

> Cheers,
> 
> Richard
> 
> 

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
-- 
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to