linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Sven Schnelle <svens@linux.ibm.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	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 08:24:53 -0800	[thread overview]
Message-ID: <a34be5ca-47e7-95a6-602f-da054e409e85@intel.com> (raw)
In-Reply-To: <yt9dbl00rmgx.fsf@linux.ibm.com>

On 1/25/22 05:09, Sven Schnelle wrote:
>> 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?

My understanding is that the 5v line is disconnected.  Here's one cable 
I have:

> https://designintools.intel.com/SVT_DCI_DbC2_3_A_to_A_Debug_Cable_1_Meter_p/itpdciamam1m.htm

I think they snip that line to prevent any chance of current flowing 
between devices.  The cable isn't expensive, but I do remember being 
astounded at how much Intel charged itself for shipping it. ;)

That said, I've also used the same cable Peter has: just a cheap A-to-A 
cable I had lying around.  It surely has VBUS connected, so I usually 
plumb it through a USB hub with a power switch.  This surely isn't the 
"right" way to do it, but it does seem to work in some situations.

  parent reply	other threads:[~2022-01-25 16:27 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
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 [this message]
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=a34be5ca-47e7-95a6-602f-da054e409e85@intel.com \
    --to=dave.hansen@intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=chunfeng.yun@mediatek.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=svens@linux.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).