From: Timur Tabi <ttabi@nvidia.com>
To: "airlied@gmail.com" <airlied@gmail.com>
Cc: "nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [Nouveau] [PATCH 3/3] nouveau/gsp: add some basic registry entries.
Date: Tue, 7 Nov 2023 19:02:45 +0000 [thread overview]
Message-ID: <769bb600f28f24d4bf9251e36fd3b13dba50d928.camel@nvidia.com> (raw)
In-Reply-To: <CAPM=9tyvAPf2iNZ6utEN9FuE_wo17u4D9uCMXJSd0+w3VPHcLw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 201 bytes --]
On Wed, 2023-11-08 at 04:54 +1000, Dave Airlie wrote:
yes that is probably the right answer for this, if we want to reuse
the structs that we get from the nvidia driver.
ok, I'll submit a patch.
[-- Attachment #2: Type: text/html, Size: 529 bytes --]
next prev parent reply other threads:[~2023-11-07 19:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 5:18 [Nouveau] nouveau/gsp: move to latest fw and small fixes Dave Airlie
2023-10-31 5:18 ` Dave Airlie
2023-10-31 5:18 ` [Nouveau] [PATCH 1/3] nouveau/gsp: move to 535.113.01 Dave Airlie
2023-10-31 5:18 ` Dave Airlie
2023-10-31 5:18 ` [Nouveau] [PATCH 2/3] nouveau/gsp: fix message signature Dave Airlie
2023-10-31 5:18 ` Dave Airlie
2023-10-31 5:18 ` [Nouveau] [PATCH 3/3] nouveau/gsp: add some basic registry entries Dave Airlie
2023-10-31 5:18 ` Dave Airlie
2023-10-31 15:52 ` [Nouveau] " Timur Tabi
2023-10-31 19:29 ` Dave Airlie
2023-10-31 20:02 ` Timur Tabi
2023-11-07 18:51 ` Timur Tabi
2023-11-07 18:54 ` Dave Airlie
2023-11-07 19:02 ` Timur Tabi [this message]
2023-11-27 20:47 ` Timur Tabi
2023-11-27 21:32 ` Dave Airlie
2023-11-03 2:03 ` [Nouveau] nouveau/gsp: move to latest fw and small fixes Danilo Krummrich
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=769bb600f28f24d4bf9251e36fd3b13dba50d928.camel@nvidia.com \
--to=ttabi@nvidia.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=nouveau@lists.freedesktop.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.