All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	airlied@linux.ie, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/3] drm: Move several files from DRM core into modules
Date: Thu, 21 Oct 2021 14:21:56 +0200	[thread overview]
Message-ID: <28ca3e87-4fbb-d7bb-d5ce-520981e7ee2d@suse.de> (raw)
In-Reply-To: <YXFUe355D41ebf8q@phenom.ffwll.local>


[-- Attachment #1.1: Type: text/plain, Size: 1817 bytes --]

Hi

Am 21.10.21 um 13:52 schrieb Daniel Vetter:
> On Wed, Oct 20, 2021 at 03:19:38PM +0200, Thomas Zimmermann wrote:
>> Move a number of files into modules and behind config options.
>>
>> So far, early boot graphics was provided by fbdev. With simpledrm, and
>> possibly other generic DRM drivers, it's now possible to have general
>> early-boot output with DRM. This requires the DRM core to be linked into
>> the kernel binary image.
>>
>> The reduction in size here is only ~1%, but the patchset is part of a
>> larger effort to reduce the size of the DRM core module.
>>
>> Thomas Zimmermann (3):
>>    drm: Build drm_irq.o only if CONFIG_DRM_LEGACY has been set
>>    drm: Link several object files into drm_kms_helper.ko
>>    drm: Move GEM memory managers into modules
> 
> Assuming it all compiles still in all combos, on the series:
> 
> Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>

Thanks for the A-b. I built with DRM_LEGACY set and unset.

The GEM changes shouldn't be affected by the config. With the CMA 
helpers in a separate module, we could maybe remove 
CONFIG_DRM_KMS_CMA_HELPER and link drm_fb_cma_helper.o if 
CONFIG_DRM_KMS_HELPER has been selected.

Best regards
Thomas

>>
>>   drivers/gpu/drm/Kconfig                |  4 ++--
>>   drivers/gpu/drm/Makefile               | 26 +++++++++++++++-----------
>>   drivers/gpu/drm/drm_gem_cma_helper.c   |  4 ++++
>>   drivers/gpu/drm/drm_gem_shmem_helper.c |  4 ++++
>>   drivers/gpu/drm/drm_irq.c              |  2 --
>>   5 files changed, 25 insertions(+), 15 deletions(-)
>>
>> --
>> 2.33.0
>>
> 

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2021-10-21 12:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20 13:19 [PATCH 0/3] drm: Move several files from DRM core into modules Thomas Zimmermann
2021-10-20 13:19 ` [PATCH 1/3] drm: Build drm_irq.o only if CONFIG_DRM_LEGACY has been set Thomas Zimmermann
2021-10-20 13:19 ` [PATCH 2/3] drm: Link several object files into drm_kms_helper.ko Thomas Zimmermann
2021-10-20 13:19 ` [PATCH 3/3] drm: Move GEM memory managers into modules Thomas Zimmermann
2021-10-21 11:52 ` [PATCH 0/3] drm: Move several files from DRM core " Daniel Vetter
2021-10-21 12:21   ` Thomas Zimmermann [this message]
2021-10-21 12:38 ` Jani Nikula
2021-10-21 13:34   ` Thomas Zimmermann
2021-10-21 16:51   ` 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=28ca3e87-4fbb-d7bb-d5ce-520981e7ee2d@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@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 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.