From: "Sapp, Randolph" <rs@ti.com>
To: Danny <dadleyy@gmail.com>, Denys Dmytriyenko <denis@denix.org>
Cc: "Eatmon, Ryan" <reatmon@ti.com>,
"danny@sizethreestudios.com" <danny@sizethreestudios.com>,
"meta-ti@lists.yoctoproject.org" <meta-ti@lists.yoctoproject.org>
Subject: Re: [EXTERNAL] Re: [meta-ti] [kirkstone] mesa compilation failures when setting PREFERRED_PROVIDER for virtual/gpudriver = "ti-sgx-ddk-km"
Date: Thu, 16 Mar 2023 16:50:46 +0000 [thread overview]
Message-ID: <566c9789f1884b42bb971ca3e32e1272@ti.com> (raw)
In-Reply-To: <CADEQF5H-7MLBBms9FR-=PtBqHKmMOhrVpzgXftPPR8OdJ9iB3A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 726 bytes --]
Yeah,
In hindsight we should have started with no graphics recipes (software rendering) and slowly incorporated drivers as they are verified on this new branch. Would have been clearer what we were doing and prevent any suggestions of feature regression in the utilities themselves, but unfortunately I only came into this situation after the decision to clone everything was made.
I'm still working on fixing SGX and hopefully with the way I'm integrating it, we can cut down on future maintenance delays in the future. Unfortunately that means a little more upfront delay with hints in the layers incorrectly informing people that the driver is still operational. Sorry about that.
Regards,
Randolph Sapp
[-- Attachment #2: Type: text/html, Size: 1164 bytes --]
prev parent reply other threads:[~2023-03-16 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mail.64133faf.3771.17352b0439bf0805@storage.wm.amazon.com>
2023-03-16 16:11 ` [kirkstone] mesa compilation failures when setting PREFERRED_PROVIDER for virtual/gpudriver = "ti-sgx-ddk-km" danny
2023-03-16 16:28 ` [meta-ti] " Ryan Eatmon
2023-03-16 16:34 ` Denys Dmytriyenko
2023-03-16 16:43 ` Danny
2023-03-16 16:50 ` Sapp, Randolph [this message]
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=566c9789f1884b42bb971ca3e32e1272@ti.com \
--to=rs@ti.com \
--cc=dadleyy@gmail.com \
--cc=danny@sizethreestudios.com \
--cc=denis@denix.org \
--cc=meta-ti@lists.yoctoproject.org \
--cc=reatmon@ti.com \
/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.