All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Koen Kooi <koen@dominion.thruhere.net>,
	Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: How to handle mesa customization in BSP layers
Date: Sat, 24 Oct 2015 18:00:50 -0400	[thread overview]
Message-ID: <562BFF92.9020407@gmail.com> (raw)
In-Reply-To: <65454D5E-98C5-4BA7-828B-05BBD56FB3E5@dominion.thruhere.net>

On 10/20/15 05:37, Koen Kooi wrote:
>> Op 20 okt. 2015, om 11:32 heeft Nicolas Dechesne <nicolas.dechesne@linaro.org> het volgende geschreven:
>>
>>
>> The issue is that mesa is arch specific, not machine specific. So if
>> you start mixing machines from the same arch, we are getting
>> unexpected/wrong rebuilds.
> In this specific case I think we should enable freedreno for armv7/armv8 in OE-core, but the problem remains for other recipes like this.

Are you suggesting that every armv7 device should have their mesa tuned
for freedreno and freedreno added to their filesystem? That seems quite
overly-broad!

On the surface[1] it would seem as though the decisions as to how one
builds mesa and which graphics solution to install is more similar to
the decision as to which DEFAULTTUNE to use, rather than which
architecture is involved?







[1] which is my way of saying "I don't have the experience of actually
having done this, unlike you people" ;-)


  reply	other threads:[~2015-10-24 22:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20  9:32 How to handle mesa customization in BSP layers Nicolas Dechesne
2015-10-20  9:37 ` Koen Kooi
2015-10-24 22:00   ` Trevor Woerner [this message]
2015-10-25 12:22     ` Nicolas Dechesne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=562BFF92.9020407@gmail.com \
    --to=twoerner@gmail.com \
    --cc=koen@dominion.thruhere.net \
    --cc=nicolas.dechesne@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.