From: Denys Dmytriyenko <denis@denix.org>
To: rs@ti.com
Cc: reatmon@ti.com, meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti] [dunfell][PATCH] ti-img-rogue-*: Bump the graphics recipes
Date: Tue, 11 Oct 2022 19:16:49 -0400 [thread overview]
Message-ID: <20221011231649.GE22689@denix.org> (raw)
In-Reply-To: <7YXLJR.BJWKMOUWUVN01@ti.com>
On Tue, Oct 11, 2022 at 04:20:31PM -0500, Randolph Sapp via lists.yoctoproject.org wrote:
> On Mon, Oct 10 2022 at 09:44:03 PM -0400, Denys Dmytriyenko
> <denis@denix.org> wrote:
> >Any useful changelog between the 2 SRCREVs, besides removal of BVNC?
>
> Yeah, actually. Two main things. The default precision for GL
> fragmentation shaders was bumped up, which helps with some visual
> bugs in applications like glmark2. In addition to this, a firmware
> patch was added that should help some of the hardware recoveries
> clients were experiencing on am62.
>
> This is roughly the latest commit message for the selected UM version.
>
> KM was really only a Makefile cleanup because I was tired of trying
> to remember what platform had what BVNC and there were a few legacy
> variables being set that had no effect.
Should these be mentioned in the git commit message?
--
Denys
next prev parent reply other threads:[~2022-10-11 23:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 23:41 [dunfell][PATCH] ti-img-rogue-*: Bump the graphics recipes Randolph Sapp
2022-10-11 1:44 ` [meta-ti] " Denys Dmytriyenko
2022-10-11 21:20 ` [EXTERNAL] " Sapp, Randolph
2022-10-11 23:16 ` Denys Dmytriyenko [this message]
2022-10-12 16:32 ` Sapp, Randolph
2022-10-12 17:28 ` Denys Dmytriyenko
2022-10-12 17:43 ` [EXTERNAL] " Sapp, Randolph
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=20221011231649.GE22689@denix.org \
--to=denis@denix.org \
--cc=meta-ti@lists.yoctoproject.org \
--cc=reatmon@ti.com \
--cc=rs@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.