From: Helge Deller <deller@gmx.de>
To: Javier Martinez Canillas <javierm@redhat.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
drawat.floss@gmail.com, decui@microsoft.com, wei.liu@kernel.org,
haiyangz@microsoft.com, kys@microsoft.com, daniel@ffwll.ch,
airlied@gmail.com
Cc: linux-hyperv@vger.kernel.org, linux-fbdev@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/4] drm/hyperv: Remove firmware framebuffers with aperture helper
Date: Mon, 8 Jan 2024 10:33:28 +0100 [thread overview]
Message-ID: <4095003c-20a5-45af-8765-d772cd054f0b@gmx.de> (raw)
In-Reply-To: <87a5pgdvll.fsf@minerva.mail-host-address-is-not-set>
On 1/8/24 10:26, Javier Martinez Canillas wrote:
> Thomas Zimmermann <tzimmermann@suse.de> writes:
>
> Hello Thomas,
>
>> Replace use of screen_info state with the correct interface from
>> the aperture helpers. The state is only for architecture and firmware
>> code. It is not guaranteed to contain valid data. Drivers are thus
>> not allowed to use it.
>>
>> For removing conflicting firmware framebuffers, there are aperture
>> helpers. Hence replace screen_info with the correct function that will
>> remove conflicting framebuffers for the hyperv-drm driver. Also
>> move the call to the correct place within the driver.
>>
>> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
>> ---
>
> Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
Series applied to fbdev git tree.
Thanks,
Helge
next prev parent reply other threads:[~2024-01-08 9:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 10:15 [PATCH 0/4] hyperv, sysfb: Do not use screen_info in drivers Thomas Zimmermann
2024-01-03 10:15 ` [PATCH 1/4] drm/hyperv: Remove firmware framebuffers with aperture helper Thomas Zimmermann
2024-01-08 9:26 ` Javier Martinez Canillas
2024-01-08 9:33 ` Helge Deller [this message]
2024-01-03 10:15 ` [PATCH 2/4] fbdev/hyperv_fb: Remove firmware framebuffers with aperture helpers Thomas Zimmermann
2024-01-08 9:27 ` Javier Martinez Canillas
2024-01-03 10:15 ` [PATCH 3/4] firmware/sysfb: Clear screen_info state after consuming it Thomas Zimmermann
2024-01-08 9:35 ` Javier Martinez Canillas
2024-01-03 10:15 ` [PATCH 4/4] fbdev/hyperv_fb: Do not clear global screen_info Thomas Zimmermann
2024-01-08 9:36 ` Javier Martinez Canillas
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=4095003c-20a5-45af-8765-d772cd054f0b@gmx.de \
--to=deller@gmx.de \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=decui@microsoft.com \
--cc=drawat.floss@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=haiyangz@microsoft.com \
--cc=javierm@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=tzimmermann@suse.de \
--cc=wei.liu@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox