Date: Wed, 2 Dec 2020 08:00:11 +0100 From: Ali Abdallah <ali.abdallah@suse.com> To: Scott Long <scottl@samsco.org> Cc: myfreeweb <greg@unrelenting.technology>, freebsd-current@freebsd.org, Hans Petter Selasky <hps@selasky.org>, Scott Long <scottl@FreeBSD.org> Subject: Re: Issues with USB-C external monitors Message-ID: <20201202070011.amdv7hxpq52x7zjw@frix230> In-Reply-To: <68205920-BE4F-460D-BF70-1A84FE3BC536@samsco.org> References: <20201201131430.ol7pzms24h743iwf@frix230> <342519ee-6f73-98be-29b1-cea7890ccb1e@selasky.org> <BD186C8D-AF73-4182-BF89-89005854F618@unrelenting.technology> <20201201173223.mwmrkogcjmtc4k2j@frix230> <68205920-BE4F-460D-BF70-1A84FE3BC536@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01.12.2020 11:08, Scott Long wrote: > I have a work-in-progress to support Thunderbolt, but that’s not always the same as just DisplayPort-over-USBC. If your connector has the Thunderbolt logo, then it’s Thunderbolt, if it has the DP logo then it’s not. Even then, the Thunderbolt component only controls enable/disable permissions and bandwidth partitioning. The graphics chip and DRM code does the rest of the work, and it sounds like the problems here are with those components. T495 has AMD Ryzen silicon, and AMD never associated Thunderbolt with its Ryzen platforms. The dock connector is just a USB-C. On dock removal, the devd events (system DRM, type HOTPLUG) are correctly generated and received by libudev-devd, but then for some reason UD_ACTION_HOTPLUG is not causing the X server to re-scan drm connectors and to re-configure them. Will dig further into the issue as I feel it should be easy to solve. > > Scott > Ali
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20201202070011.amdv7hxpq52x7zjw>