From: Thomas Zimmermann <tzimmermann@suse.de>
To: Javier Martinez Canillas <javierm@redhat.com>,
daniel.vetter@ffwll.ch, patrik.r.jakobsson@gmail.com
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v4 1/9] drm/gma500: Use drm_aperture_remove_conflicting_pci_framebuffers
Date: Thu, 6 Apr 2023 10:53:54 +0200 [thread overview]
Message-ID: <520414ed-46b7-ae0d-a567-bc2a7c898487@suse.de> (raw)
In-Reply-To: <87r0sx8kso.fsf@minerva.mail-host-address-is-not-set>
[-- Attachment #1.1: Type: text/plain, Size: 1783 bytes --]
Hi
Am 06.04.23 um 10:41 schrieb Javier Martinez Canillas:
> Thomas Zimmermann <tzimmermann@suse.de> writes:
>
>> From: Daniel Vetter <daniel.vetter@ffwll.ch>
>>
>> This one nukes all framebuffers, which is a bit much. In reality
>> gma500 is igpu and never shipped with anything discrete, so there should
>> not be any difference.
>>
>> v2: Unfortunately the framebuffer sits outside of the pci bars for
>> gma500, and so only using the pci helpers won't be enough. Otoh if we
>> only use non-pci helper, then we don't get the vga handling, and
>> subsequent refactoring to untangle these special cases won't work.
>>
>> It's not pretty, but the simplest fix (since gma500 really is the only
>> quirky pci driver like this we have) is to just have both calls.
>>
>> v4:
>> - fix Daniel's S-o-b address
>>
>
> I believe they want to have their Intel S-o-B as well. I know that dim
> complains but that's what usually happens with danvet's patches AFAIK.
I'll do as you suggest and add both.
>
>> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>> Cc: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
>> Cc: Thomas Zimmermann <tzimmermann@suse.de>
>> Cc: Javier Martinez Canillas <javierm@redhat.com>
>> ---
>
> Patch looks good to me. Although I wonder if should just be dropped in
> favour of yours patch since are now part of the same series?
That might require a rework of some other patches in this series. So
let's just merge both of them.
Best regards
Thomas
>
> Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2023-04-06 8:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 8:32 [PATCH v4 0/9] video/aperture: Ignore firmware framebuffers with non-primary devices Thomas Zimmermann
2023-04-06 8:32 ` [PATCH v4 1/9] drm/gma500: Use drm_aperture_remove_conflicting_pci_framebuffers Thomas Zimmermann
2023-04-06 8:41 ` Javier Martinez Canillas
2023-04-06 8:53 ` Thomas Zimmermann [this message]
2023-04-06 9:01 ` Javier Martinez Canillas
2023-04-06 8:32 ` [PATCH v4 2/9] video/aperture: use generic code to figure out the vga default device Thomas Zimmermann
2023-04-06 8:32 ` Thomas Zimmermann
2023-04-06 8:32 ` [PATCH v4 3/9] drm/aperture: Remove primary argument Thomas Zimmermann
2023-04-06 8:32 ` Thomas Zimmermann
2023-04-06 8:32 ` Thomas Zimmermann
2023-04-06 8:32 ` Thomas Zimmermann
2023-04-06 8:32 ` [PATCH v4 4/9] video/aperture: Only kick vgacon when the pdev is decoding vga Thomas Zimmermann
2023-04-06 8:32 ` Thomas Zimmermann
2023-04-06 8:32 ` [PATCH v4 5/9] video/aperture: Move vga handling to pci function Thomas Zimmermann
2023-04-06 8:32 ` Thomas Zimmermann
2023-04-06 8:32 ` [PATCH v4 6/9] video/aperture: Drop primary argument Thomas Zimmermann
2023-04-06 8:32 ` Thomas Zimmermann
2023-04-06 8:32 ` [PATCH v4 7/9] video/aperture: Only remove sysfb on the default vga pci device Thomas Zimmermann
2023-04-06 8:32 ` Thomas Zimmermann
2023-04-06 8:32 ` [PATCH v4 8/9] fbdev: Simplify fb_is_primary_device for x86 Thomas Zimmermann
2023-04-06 8:32 ` [PATCH v4 9/9] video/aperture: Provide a VGA helper for gma500 and internal use Thomas Zimmermann
2023-04-06 8:40 ` Daniel Vetter
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=520414ed-46b7-ae0d-a567-bc2a7c898487@suse.de \
--to=tzimmermann@suse.de \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=patrik.r.jakobsson@gmail.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.