From: Valdis.Kletnieks@vt.edu
To: Paul Zimmerman <Paul.Zimmerman@synopsys.com>
Cc: Sarah Sharp <sarah.a.sharp@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"Nyman, Mathias" <mathias.nyman@intel.com>,
Nick Krause <xerofoify@gmail.com>
Subject: Re: Kernel Debugging Support
Date: Mon, 04 Aug 2014 16:27:43 -0400 [thread overview]
Message-ID: <62334.1407184063@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 04 Aug 2014 19:40:15 -0000." <A2CA0424C0A6F04399FB9E1CD98E0304844C4061@US01WEMBX2.internal.synopsys.com>
[-- Attachment #1: Type: text/plain, Size: 519 bytes --]
On Mon, 04 Aug 2014 19:40:15 -0000, Paul Zimmerman said:
> Ah, you didn't read far enough down the page :)
I'm willing to bet a large pizza with everything but anchovies that
out in the real world, a lot of implementors didn't read further either. :)
> So I have to believe there are a *lot* of systems out there that do support xHCI debug.
Possibly. But enough to make an actual critical mass to motivate somebody
to write code? Or do you get more bang-for-buck by fixing kgdb to support
debugging over Ethernet?
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
next prev parent reply other threads:[~2014-08-04 20:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-02 4:47 Nick Krause
2014-08-02 13:48 ` Alan Stern
2014-08-03 1:40 ` Nick Krause
2014-08-04 11:37 ` Austin S Hemmelgarn
2014-08-04 14:21 ` Alan Stern
2014-08-04 14:29 ` Austin S Hemmelgarn
2014-08-04 14:45 ` Richard Weinberger
2014-08-04 16:46 ` Sarah Sharp
2014-08-04 19:07 ` Paul Zimmerman
2014-08-04 19:23 ` Valdis.Kletnieks
2014-08-04 19:40 ` Paul Zimmerman
2014-08-04 20:27 ` Valdis.Kletnieks [this message]
2014-08-04 21:55 ` Paul Zimmerman
2014-08-04 22:49 ` Nick Krause
2014-08-04 23:03 ` Paul Zimmerman
2014-08-04 23:11 ` Nick Krause
2014-08-05 0:12 ` Sarah Sharp
2014-08-05 1:33 ` Nick Krause
2014-08-05 3:18 ` Nick Krause
2014-08-05 5:32 ` Nick Krause
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=62334.1407184063@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=Paul.Zimmerman@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=sarah.a.sharp@linux.intel.com \
--cc=xerofoify@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
all inboxes | Powered by JetHome®