mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Claire DuSoleil <claire.m.dusoleil@gmail.com>
To: Maaz Mombasawala <maaz.mombasawala@broadcom.com>
Cc: "Zack Rusin" <zack.rusin@broadcom.com>,
	"Broadcom internal kernel review list"
	<bcm-kernel-feedback-list@broadcom.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Sumit Semwal" <sumit.semwal@linaro.org>,
	"Christian König" <christian.koenig@amd.com>,
	linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH] drm/vmwgfx: Fix GEM_CLOSE returning -EINVAL for PRIME-imported surfaces
Date: Fri, 18 Sep 2026 14:23:05 -0700	[thread overview]
Message-ID: <CAEcBvW10sKwD2+Ro6o8Fq_9oLwsedq405f=gjQ+OMbY72=+VFA@mail.gmail.com> (raw)
In-Reply-To: <CAEcBvW0+SqM2zHbaDS+JycXxc-ztzvixKtHVSVQby9viVH=+eA@mail.gmail.com>

I had Claude Code generate this patch so I could run Omarchy in a
VMWare virtual machine.  Without the fix, all I see is black screen.
It is currently working but I have to re-apply the patch after every
Omarchy system update.

Claude originally identified the issue as a Hyprland bug but after
further digging, it's really in vmwgfx.  However Mesa has coded around
it and I also had a Hyprland fix that worked as well.  It seemed the
best place to fix it was vmwgfx.

Claire

On Fri, Sep 18, 2026 at 2:17 PM Claire DuSoleil
<claire.m.dusoleil@gmail.com> wrote:
>
> I had Claude Code generate this patch so I could run Omarchy in a VMWare virtual machine.  Without the fix, all I see is black screen.  It is currently working but I have to re-apply the patch after every Omarchy system update.
>
> Claude originally identified the issue as a Hyprland bug but after further digging, it's really in vmwgfx.  However Mesa has coded around it and I also had a Hyprland fix that worked as well.  It seemed the best place to fix it was vmwgfx.
>
> I thought the patch had already been rejected so I do not understand why anyone is still looking at it, especially since this has been a known problem for many years.
>
> Claire
>
> On Fri, Sep 18, 2026 at 1:56 PM Maaz Mombasawala <maaz.mombasawala@broadcom.com> wrote:
>>
>> Hi,
>> This looks llm generated, can you disclose the llm that you have used?
>>
>> As for the patch itself, it is too overly verbose for human review.
>> Could you just describe the issue you were facing and what is the fix you have done?
>> Describing the current behaviour and the overly narrative style is not necessary.
>>
>> --
>> Maaz Mombasawala <maaz.mombasawala@broadcom.com>

  parent reply	other threads:[~2026-09-18 21:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17 18:13 Claire DuSoleil
2026-09-17 20:19 ` Zack Rusin
2026-09-18 11:26 ` kernel test robot
2026-09-18 20:56 ` Maaz Mombasawala
     [not found]   ` <CAEcBvW0+SqM2zHbaDS+JycXxc-ztzvixKtHVSVQby9viVH=+eA@mail.gmail.com>
2026-09-18 21:23     ` Claire DuSoleil [this message]
2026-09-18 23:36       ` Maaz Mombasawala

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='CAEcBvW10sKwD2+Ro6o8Fq_9oLwsedq405f=gjQ+OMbY72=+VFA@mail.gmail.com' \
    --to=claire.m.dusoleil@gmail.com \
    --cc=airlied@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=maaz.mombasawala@broadcom.com \
    --cc=mripard@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=sumit.semwal@linaro.org \
    --cc=tzimmermann@suse.de \
    --cc=zack.rusin@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®