From: "Tomasz Moń" <desowin@gmail.com>
To: Stefan Hoffmeister <stefan.hoffmeister@gmail.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
linux-usb@vger.kernel.org
Subject: Re: Thunderbolt: One missing DisplayPort?
Date: Mon, 30 May 2022 10:33:06 +0200 [thread overview]
Message-ID: <ce969e3b4a6ed04584fdecd3234578bd87d52594.camel@gmail.com> (raw)
In-Reply-To: <CALhB_QP8SPqubq-eBNa1BTMuy3kCA65OuajOeJGt5DB9jDRKKg@mail.gmail.com>
On Sun, 2022-05-29 at 21:51 +0200, Stefan Hoffmeister wrote:
> I have managed to wedge the system into a state where it does not
> know about Thunderbolt, and now, on what I presume to be USB-C only
> ("usb_typec_revision" == 1.2? Seems ... low?), both DisplayPort
> outputs on the docking station are now active, and I do get
> meaningful entries from the DRM subsystem (and hence X). I am half-
> way happy: I want exactly that over Thunderbolt for the bandwidth ;)
Could you please tell how did you wedge the system into a state where
it does not know about Thunderbolt?
> Now, when I unwedge the system to enable Thunderbolt again
I am curious about the wedge/unwedge procedure.
Best Regards,
Tomasz Moń
next prev parent reply other threads:[~2022-05-30 8:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 10:22 Thunderbolt: One missing DisplayPort? Stefan Hoffmeister
2022-05-24 10:55 ` Heikki Krogerus
2022-05-24 11:04 ` Mika Westerberg
2022-05-27 6:24 ` Stefan Hoffmeister
2022-05-27 9:10 ` Mika Westerberg
2022-05-28 14:29 ` Stefan Hoffmeister
2022-05-29 19:51 ` Stefan Hoffmeister
2022-05-30 8:33 ` Tomasz Moń [this message]
2022-05-30 9:54 ` Mika Westerberg
2022-05-30 18:57 ` Stefan Hoffmeister
2022-05-31 9:36 ` Mika Westerberg
2022-05-31 19:45 ` Stefan Hoffmeister
2022-06-01 10:51 ` Mika Westerberg
2022-06-02 19:34 ` Tomasz Moń
2022-06-03 5:04 ` Mika Westerberg
2022-06-08 14:27 ` Tomasz Moń
2022-06-11 16:29 ` Tomasz Moń
2022-06-07 17:28 ` Stefan Hoffmeister
2022-05-30 18:02 ` Stefan Hoffmeister
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=ce969e3b4a6ed04584fdecd3234578bd87d52594.camel@gmail.com \
--to=desowin@gmail.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=stefan.hoffmeister@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox