All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Schnelle <svens@linux.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	Dave Hansen <dave.hansen@intel.com>,
	Lu Baolu <baolu.lu@linux.intel.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org,
	Chunfeng Yun <chunfeng.yun@mediatek.com>
Subject: Re: earlyprintk=xdbc seems broken
Date: Tue, 25 Jan 2022 14:09:18 +0100	[thread overview]
Message-ID: <yt9dbl00rmgx.fsf@linux.ibm.com> (raw)
In-Reply-To: <Ye/w/lOf4f8+8fDt@hirez.programming.kicks-ass.net> (Peter Zijlstra's message of "Tue, 25 Jan 2022 13:45:50 +0100")

Peter Zijlstra <peterz@infradead.org> writes:

> Now the documentation states we need this super speed A<->A cable, but
> could you also update the documentation for usb-c ? There's a fair
> number of usb-c only devices out there now.

Stupid beginners question: Would every USB3 A-A cable work, or are the
debug cables special? I've read the RX/TX pairs have to be swapped, but
to me it looks like that's always the case?

I'm just asking because i tried to debug a before-framebuffer crash on
my Thinkpad X1, but didn't have any luck getting xdbc running. Maybe
because of the bug above. Would be nice if someone could confirm whether
that should work with every USB3 A-A cable.

Thanks,
Sven

  reply	other threads:[~2022-01-25 13:12 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-02 15:22 earlyprintk=xdbc seems broken Peter Zijlstra
2021-12-03  0:52 ` Lu Baolu
2021-12-03 14:31   ` Mathias Nyman
2021-12-03 15:22     ` Dave Hansen
2021-12-03 15:29       ` Greg KH
2021-12-17 11:01         ` Mathias Nyman
2021-12-17 13:55           ` Peter Zijlstra
2021-12-17 15:19             ` Greg KH
2021-12-20 14:40               ` Peter Zijlstra
2021-12-20 15:06                 ` Greg KH
2021-12-20 17:01                   ` Peter Zijlstra
2021-12-20 14:34             ` Mathias Nyman
2021-12-20 15:51               ` Peter Zijlstra
2021-12-21  9:40             ` Peter Zijlstra
2021-12-21  9:41               ` Peter Zijlstra
2022-01-14  8:47               ` Peter Zijlstra
2022-01-14 19:31                 ` Mathias Nyman
2022-01-15 16:06                   ` Peter Zijlstra
2022-01-24 14:55                     ` Mathias Nyman
2022-01-24 16:39                       ` Peter Zijlstra
2022-01-24 16:46                         ` Peter Zijlstra
2022-01-25  8:51                           ` Mathias Nyman
2022-01-25 10:47                             ` Peter Zijlstra
2022-01-25 10:54                               ` Peter Zijlstra
2022-01-25 12:45                       ` Peter Zijlstra
2022-01-25 13:09                         ` Sven Schnelle [this message]
2022-01-25 13:54                           ` Peter Zijlstra
2022-01-25 14:01                             ` Sven Schnelle
2022-01-25 17:13                               ` Mathias Nyman
2022-01-25 16:24                           ` Dave Hansen
2022-02-17  3:44                             ` Randy Dunlap
2022-01-25 19:39                         ` Rajaram R

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=yt9dbl00rmgx.fsf@linux.ibm.com \
    --to=svens@linux.ibm.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=chunfeng.yun@mediatek.com \
    --cc=dave.hansen@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=peterz@infradead.org \
    --cc=x86@kernel.org \
    /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.