From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Nick Krause <xerofoify@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org, "Nyman,
Mathias" <mathias.nyman@intel.com>
Subject: Re: Kernel Debugging Support
Date: Mon, 4 Aug 2014 09:46:33 -0700 [thread overview]
Message-ID: <20140804164633.GA28436@xanatos> (raw)
In-Reply-To: <CAPDOMVj5nifG8VQBB_UzNESBc+arxpCQ5sEOAYdb6Rr-KkDSHw@mail.gmail.com>
On Sat, Aug 02, 2014 at 12:47:59AM -0400, Nick Krause wrote:
> Hey Sharp,
Hi Krause,
Please Cc the new xHCI driver maintainer, Mathias Nyman. I'm officially
retired from USB development and have moved onto other projects. :)
> After reading around seems people want support for usb debugging in
> kgdb or other usb based solutions.
Yes, early boot USB debug over xHCI has been a low-priority feature
request.
Unfortunately, USB debug is an optional feature for xHCI host
controllers, so many of them don't have USB debug ports. Even if it is
included, the USB debug ports are often either routed to internal USB
ports or not exposed on the board altogether. Since it's not widely
available, it's not a high priority to implement.
> If you and the other developers are able to help me out a bit as I am
> new I can definitively write this
> area of kgdb support.
The kgdb support is all there. It's the xHCI host controller driver
debug port support that is needed.
Hmm, I only see one commit from your email address in Greg's tree. I
think you should work on some smaller clean ups and bug fixes, and get
some more patches into mainline before you go on to tackle a larger
feature like this. Perhaps Mathias has a smaller task that would be
good for you to tackle?
There's a good tutorial here on how to create a kernel patch, and
respond properly to patch review and rework requests:
http://kernelnewbies.org/OPWfirstpatch
And here's my personal philosophy on how to create a patchset:
http://sarah.thesharps.us/2013/05/08/patchsets-for-dinner/
> Regards Nick
> P.S. If you want Sharp I can change the commit message on my other
> commit you didn't like if me or you
> talk to Greg in order to remove in from mainline, if no that's OK too.
I don't understand what the above sentence means. What commit message
are you referencing? What do you mean by "remove in from mainline"?
Try again?
Sarah Sharp
next prev parent reply other threads:[~2014-08-04 16:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-02 4:47 Kernel Debugging Support 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 [this message]
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
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=20140804164633.GA28436@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@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;
as well as URLs for NNTP newsgroup(s).