From: Thomas Zimmermann <tzimmermann@suse.de>
To: Kevin Brace <kevinbrace@gmx.com>, dri-devel@lists.freedesktop.org
Cc: Kevin Brace <kevinbrace@bracecomputerlab.com>
Subject: Re: [PATCH v3 30/32] drm/via: Add Kconfig
Date: Tue, 26 Jul 2022 09:28:39 +0200 [thread overview]
Message-ID: <af72d22c-323d-abb9-dd77-b8b5eda4d7df@suse.de> (raw)
In-Reply-To: <20220725235359.20516-11-kevinbrace@gmx.com>
[-- Attachment #1.1: Type: text/plain, Size: 1527 bytes --]
Hi
Am 26.07.22 um 01:53 schrieb Kevin Brace:
> From: Kevin Brace <kevinbrace@bracecomputerlab.com>
>
> Signed-off-by: Kevin Brace <kevinbrace@bracecomputerlab.com>
> ---
> drivers/gpu/drm/via/Kconfig | 9 +++++++++
> 1 file changed, 9 insertions(+)
> create mode 100644 drivers/gpu/drm/via/Kconfig
>
> diff --git a/drivers/gpu/drm/via/Kconfig b/drivers/gpu/drm/via/Kconfig
> new file mode 100644
> index 000000000000..7c4656a1d473
> --- /dev/null
> +++ b/drivers/gpu/drm/via/Kconfig
> @@ -0,0 +1,9 @@
> +config DRM_OPENCHROME
I would keep the driver option named DRM_VIA, as it has been so far. To
build the existing DRI1 driver, rather introduce a new config symbol
that enables it. The rule looks something like this:
config DRM_VIA_DRI1
boolean "DRI1 support"
depends on DRM_VIA && DRM_LEGACY
help
Build for DRI1-based userspace drivers.
It will show up as an option if the user selects both DRM_VIA and
DRM_LEGACY.
Best regards
Thomas
> + tristate "OpenChrome (VIA Technologies Chrome)"
> + depends on DRM && PCI && X86
> + select DRM_KMS_HELPER
> + select DRM_TTM
> + help
> + Choose this option if you have VIA Technologies UniChrome or
> + Chrome9 integrated graphics. If M is selected the module will
> + be called via.
> --
> 2.35.1
>
--
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:[~2022-07-26 7:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 23:53 [PATCH v3 20/32] drm/via: Add via_pll.c Kevin Brace
2022-07-25 23:53 ` [PATCH v3 21/32] drm/via: Add via_pm.c Kevin Brace
2022-07-25 23:53 ` [PATCH v3 22/32] drm/via: Add via_sii164.c Kevin Brace
2022-07-25 23:53 ` [PATCH v3 23/32] drm/via: Add via_tmds.c Kevin Brace
2022-07-25 23:53 ` [PATCH v3 24/32] drm/via: Add via_ttm.c Kevin Brace
2022-07-25 23:53 ` [PATCH v3 25/32] drm/via: Add via_vt1632.c Kevin Brace
2022-07-25 23:53 ` [PATCH v3 26/32] drm/via: Add via_drm.h Kevin Brace
2022-07-26 17:41 ` Sam Ravnborg
2022-07-26 18:18 ` Thomas Zimmermann
2022-07-26 20:20 ` Dave Airlie
2022-07-27 7:36 ` Thomas Zimmermann
2022-07-29 1:06 ` Kevin Brace
2022-07-31 2:14 ` Kevin Brace
2022-07-26 18:24 ` Thomas Zimmermann
2022-07-30 22:48 ` Kevin Brace
2022-08-01 14:40 ` Sam Ravnborg
2022-08-02 0:10 ` Kevin Brace
2022-08-02 11:09 ` Sam Ravnborg
2022-08-02 18:12 ` Kevin Brace
2022-08-01 18:49 ` Thomas Zimmermann
2022-08-02 3:45 ` Kevin Brace
2022-08-02 11:38 ` Thomas Zimmermann
2022-08-03 1:49 ` Kevin Brace
2022-08-04 12:20 ` Thomas Zimmermann
2022-08-04 15:09 ` Sam Ravnborg
2022-07-25 23:53 ` [PATCH v3 27/32] drm/via: Add new VIA Technologies Chrome supporting PCI IDs to DRM Kevin Brace
2022-07-25 23:53 ` [PATCH v3 28/32] drm/via: Zero out chip type field Kevin Brace
2022-07-25 23:53 ` [PATCH v3 29/32] drm/via: Add new VIA Technologies PCI device IDs related to graphics Kevin Brace
2022-07-25 23:53 ` [PATCH v3 30/32] drm/via: Add Kconfig Kevin Brace
2022-07-26 7:28 ` Thomas Zimmermann [this message]
2022-07-31 1:49 ` Kevin Brace
2022-08-01 10:36 ` Thomas Zimmermann
2022-07-25 23:53 ` [PATCH v3 31/32] drm/via: Add Makefile Kevin Brace
2022-07-26 7:29 ` Thomas Zimmermann
2022-07-31 1:55 ` Kevin Brace
2022-07-25 23:53 ` [PATCH v3 32/32] drm/via: Modify DRM core to be able to build OpenChrome DRM Kevin Brace
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=af72d22c-323d-abb9-dd77-b8b5eda4d7df@suse.de \
--to=tzimmermann@suse.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=kevinbrace@bracecomputerlab.com \
--cc=kevinbrace@gmx.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;
as well as URLs for NNTP newsgroup(s).