[PATCH] platform/x86: uniwill-laptop: Add TUXEDO Stellaris 16 - Gen8 - Intel

[PATCH] platform/x86: uniwill-laptop: Add TUXEDO Stellaris 16 - Gen8 - Intel

[Werner Sembach]

Same features as the Gen7. Just 2 new entries for the new boardnames.

I wrote the ident the same way the system product dmi string is written,
which itself now follows how the device is listed in your online shop. The
only actual change was adding the '-' with spaces around.

Signed-off-by: Werner Sembach <wse@tuxedocomputers.com>
---
This commit was built on top of Armins latest series:
https://lore.kernel.org/all/20261110165318.631010-1-W_Armin@gmx.de/

 drivers/platform/x86/uniwill/uniwill-acpi.c | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/drivers/platform/x86/uniwill/uniwill-acpi.c b/drivers/platform/x86/uniwill/uniwill-acpi.c
index dc99bf8a8568c..e2a6a704e942e 100644
--- a/drivers/platform/x86/uniwill/uniwill-acpi.c
+++ b/drivers/platform/x86/uniwill/uniwill-acpi.c
@@ -3629,6 +3629,22 @@ static const struct dmi_system_id uniwill_dmi_table[] __initconst = {
 		},
 		.driver_data = &gmxixxx_xxxx45xx_xxxx55xx_xxxx57xx_descriptor,
 	},
+	{
+		.ident = "TUXEDO Stellaris 16 - Gen8 - Intel",
+		.matches = {
+			DMI_MATCH(DMI_SYS_VENDOR, "TUXEDO"),
+			DMI_EXACT_MATCH(DMI_BOARD_NAME, "XxAF5xxx"),
+		},
+		.driver_data = &gmxixxx_xxxx45xx_xxxx55xx_xxxx57xx_descriptor,
+	},
+	{
+		.ident = "TUXEDO Stellaris 16 - Gen8 - Intel",
+		.matches = {
+			DMI_MATCH(DMI_SYS_VENDOR, "TUXEDO"),
+			DMI_EXACT_MATCH(DMI_BOARD_NAME, "XxAF5xxx_mLED"),
+		},
+		.driver_data = &gmxixxx_xxxx45xx_xxxx55xx_xxxx57xx_descriptor,
+	},
 	{
 		.ident = "TUXEDO Book BA15 Gen10 AMD",
 		.matches = {
-- 
2.43.0

Re: [PATCH] platform/x86: uniwill-laptop: Add TUXEDO Stellaris 16 - Gen8 - Intel

[Ilpo Järvinen]

On Wed, 11 Nov 2026, Werner Sembach wrote:

> Same features as the Gen7. Just 2 new entries for the new boardnames.

The changelog should be readable as standalone, which this clearly isn't.

> I wrote the ident the same way the system product dmi string is written,

Don't use personalized terms like "I wrote".

> which itself now follows how the device is listed in your online shop. The
> only actual change was adding the '-' with spaces around.

What online shop have is irrelevant detail when it comes to kernel changes.

--
 i.

> Signed-off-by: Werner Sembach <wse@tuxedocomputers.com>
> ---
> This commit was built on top of Armins latest series:
> https://lore.kernel.org/all/20261110165318.631010-1-W_Armin@gmx.de/
> 
>  drivers/platform/x86/uniwill/uniwill-acpi.c | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
> 
> diff --git a/drivers/platform/x86/uniwill/uniwill-acpi.c b/drivers/platform/x86/uniwill/uniwill-acpi.c
> index dc99bf8a8568c..e2a6a704e942e 100644
> --- a/drivers/platform/x86/uniwill/uniwill-acpi.c
> +++ b/drivers/platform/x86/uniwill/uniwill-acpi.c
> @@ -3629,6 +3629,22 @@ static const struct dmi_system_id uniwill_dmi_table[] __initconst = {
>  		},
>  		.driver_data = &gmxixxx_xxxx45xx_xxxx55xx_xxxx57xx_descriptor,
>  	},
> +	{
> +		.ident = "TUXEDO Stellaris 16 - Gen8 - Intel",
> +		.matches = {
> +			DMI_MATCH(DMI_SYS_VENDOR, "TUXEDO"),
> +			DMI_EXACT_MATCH(DMI_BOARD_NAME, "XxAF5xxx"),
> +		},
> +		.driver_data = &gmxixxx_xxxx45xx_xxxx55xx_xxxx57xx_descriptor,
> +	},
> +	{
> +		.ident = "TUXEDO Stellaris 16 - Gen8 - Intel",
> +		.matches = {
> +			DMI_MATCH(DMI_SYS_VENDOR, "TUXEDO"),
> +			DMI_EXACT_MATCH(DMI_BOARD_NAME, "XxAF5xxx_mLED"),
> +		},
> +		.driver_data = &gmxixxx_xxxx45xx_xxxx55xx_xxxx57xx_descriptor,
> +	},
>  	{
>  		.ident = "TUXEDO Book BA15 Gen10 AMD",
>  		.matches = {
>