From: John Hubbard <jhubbard@nvidia.com>
To: Alexandre Courbot <acourbot@nvidia.com>,
Eliot Courtney <ecourtney@nvidia.com>
Cc: airlied@redhat.com, Danilo Krummrich <dakr@kernel.org>,
David Airlie <airlied@gmail.com>,
nova-gpu@lists.linux.dev, dri-devel@lists.freedesktop.org,
dri-devel <dri-devel-bounces@lists.freedesktop.org>
Subject: Re: [PATCH] gpu: nova-core: make pramin/buddy optional
Date: Fri, 30 Oct 2026 14:42:53 -0700 [thread overview]
Message-ID: <1791cdd4-02b0-4c98-870e-8377237afe6a@nvidia.com> (raw)
In-Reply-To: <DMI4UK02HZB8.1KEPETWUOZ7E5@nvidia.com>
On 10/30/26 4:23 AM, Alexandre Courbot wrote:
> On Fri Oct 30, 2026 at 4:57 PM JST, Eliot Courtney wrote:
>> On Mon Oct 26, 2026 at 1:24 PM JST, Dave Airlie via B4 Relay wrote:
>>> From: Dave Airlie <airlied@redhat.com>
...
> Typically "a helper method on Chipset" means that we want a HAL method.
> It just so happens that we already have a FB HAL, and a `vidmem_size`
> method on it. I don't know if a vidmem size of `0` can always be
> interpreted as "no framebuffer", but if not maybe we can rework it to
> add that information, or just add a new method.
Open RM never infers zero FB from a size. The FB sizes that it reports
are 0 because "bGpuArchIsZeroFb" is set, and it does not read the FB
size registers to decide.
thanks,
--
John Hubbard
next prev parent reply other threads:[~2026-10-30 21:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 4:24 [PATCH] gpu: nova-core: make pramin/buddy optional Dave Airlie via B4 Relay
2026-10-26 6:58 ` sashiko-bot
2026-10-26 18:50 ` Danilo Krummrich
2026-10-30 3:51 ` Alexandre Courbot
2026-10-30 6:18 ` David Airlie
2026-10-30 11:28 ` Alexandre Courbot
2026-10-30 7:54 ` Eliot Courtney
2026-10-30 21:30 ` John Hubbard
2026-10-30 7:57 ` Eliot Courtney
2026-10-30 11:23 ` Alexandre Courbot
2026-10-30 21:42 ` John Hubbard [this message]
2026-10-30 21:34 ` John Hubbard
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=1791cdd4-02b0-4c98-870e-8377237afe6a@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dakr@kernel.org \
--cc=dri-devel-bounces@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ecourtney@nvidia.com \
--cc=nova-gpu@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox