From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Tiago Martins Araújo" <tiago.martins.araujo@gmail.com>,
"Harry Wentland" <harry.wentland@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Leo Li" <sunpeng.li@amd.com>
Cc: Dave Airlie <airlied@gmail.com>,
dri-devel@lists.freedesktop.org, simona@ffwll.ch,
mpearson-lenovo@squebb.ca
Subject: Re: DisplayID checksum validation blocking hardware capabilities - CSO T3 panel
Date: Thu, 30 Oct 2025 12:51:27 +0200 [thread overview]
Message-ID: <dd8f7fb7214874e085bf6d17d3b8b881dceda42d@intel.com> (raw)
In-Reply-To: <CACRbrPEkT5bqRG_z8C17wNe_nHbDD3+w70iqvRcnmasrTzqxoQ@mail.gmail.com>
On Tue, 28 Oct 2025, Tiago Martins Araújo <tiago.martins.araujo@gmail.com> wrote:
> I've tested your DisplayID quirk patch series [1] and can confirm it works
> perfectly!
Awesome, thanks for testing!
Cc: Harry, Alex, Leo, since this issue is present on both Intel and AMD
based machines, could you find someone to review [1] please?
> Perhaps I should just buy a Thinkpad next time :)
Well, I think the listing at [2] is a more reliable indication for Linux
support from Lenovo than just "ThinkPad".
BR,
Jani.
[1] https://lore.kernel.org/r/cover.1761681968.git.jani.nikula@intel.com
[2] https://support.lenovo.com/us/en/solutions/pd031426-linux-for-personal-systems
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-10-30 10:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-14 15:13 DisplayID checksum validation blocking hardware capabilities - CSO T3 panel Tiago Martins Araújo
2025-09-14 21:43 ` Dave Airlie
2025-09-15 9:24 ` Jani Nikula
2025-09-15 19:22 ` Tiago Martins Araújo
2025-10-28 19:08 ` Jani Nikula
2025-10-28 19:25 ` Tiago Martins Araújo
2025-10-28 20:09 ` Jani Nikula
2025-10-28 21:32 ` Tiago Martins Araújo
2025-10-30 10:51 ` Jani Nikula [this message]
2025-10-31 10:13 ` Jani Nikula
2025-10-31 10:42 ` Tiago Martins Araújo
2025-09-15 8:51 ` Jani Nikula
2025-09-15 9:00 ` Jani Nikula
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=dd8f7fb7214874e085bf6d17d3b8b881dceda42d@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=mpearson-lenovo@squebb.ca \
--cc=simona@ffwll.ch \
--cc=sunpeng.li@amd.com \
--cc=tiago.martins.araujo@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.