lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240516091645.GB1421138@black.fi.intel.com>
Date: Thu, 16 May 2024 12:16:45 +0300
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Esther Shimanovich <eshimanovich@...omium.org>
Cc: Lukas Wunner <lukas@...ner.de>,
	Mario Limonciello <mario.limonciello@....com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Bjorn Helgaas <bhelgaas@...gle.com>, linux-pci@...r.kernel.org,
	linux-kernel@...r.kernel.org, Rajat Jain <rajatja@...gle.com>
Subject: Re: [PATCH v4] PCI: Relabel JHL6540 on Lenovo X1 Carbon 7,8

Hi,

On Wed, May 15, 2024 at 02:53:54PM -0400, Esther Shimanovich wrote:
> > For the clarity, Intel integrated Thunderbolt 3 controller first in Ice
> > Lake, then Thunderbolt 4 controller in Tiger Lake and forward (Alder
> > Lake, Raptor Lake, Meteor Lake). Anything else, including Comet Lake and
> > the like are using discrete controllers such as Alpine Ridge, Titan
> > Ridge (both Thunderbolt 3) and Maple Ridge (Thunderbolt 4), and Barlow
> > Ridge (Thunderbolt 5) where the controller is either soldered on the
> > motherboard or connected to a PCIe slot.
> 
> Thanks for the explanation!
> This patch worked smoothly on the device I tried. I'd be happy to go
> forward with this patch, and test it on more devices.
> Is that fine? Or should I try something else on the build I made with
> Lukas's commits?

I suggest trying on more devices just to be sure it covers all of them.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ