All of lore.kernel.org
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Nick Krause <xerofoify@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	USB list <linux-usb@vger.kernel.org>
Subject: Re: Kernel Debugging Support
Date: Mon, 04 Aug 2014 10:29:43 -0400	[thread overview]
Message-ID: <53DF98D7.7030106@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1408041007330.1169-100000@iolanthe.rowland.org>

[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]

On 2014-08-04 10:21, Alan Stern wrote:
> On Mon, 4 Aug 2014, Austin S Hemmelgarn wrote:
> 
>> On 2014-08-02 09:48, Alan Stern wrote:
>>> On Sat, 2 Aug 2014, Nick Krause wrote:
>>>
>>>> Hey Sharp,
>>>> After reading around seems people want support for usb debugging in
>>>> kgdb or other usb based solutions.
>>>> 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.
>>>
>>> Doesn't kgdb already support USB for debugging?
>>>
>>> Alan Stern
>>
>> AFAICT, on x86 it only supports using either a console capable serial
>> port (so you could do that over USB if you have USB serial console
>> support built-in, but most people I know don't compile that in, and in
>> fact that is the only reason that i compile USB serial support in
>> instead of making it a module), and an AT compatible keyboard with any
>> console option.
> 
> What about with a USB debugging device (CONFIG_EARLY_PRINTK_DBGP)?  
> That's how debugging over USB is _supposed_ to be done.
Yes, except those are really expensive, and on some it's pretty easy if
you don't know what you are doing to really screw things up.
> 
>>  It would be really nice to have USB keyboard support in
>> there so that you don't have to reboot with special options and extra
>> hardware plugged in to get to the debugger, although doing something
>> that supports more than just the HID boot protocol will probably be tricky.
> 
> Is there some reason why kgdb doesn't simply use the kernel's input 
> layer?  If there is, that same reason probably prevents it from using 
> USB.
> 
I believe it's to minimize the in-kernel dependencies.



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2967 bytes --]

  reply	other threads:[~2014-08-04 14:29 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 [this message]
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
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=53DF98D7.7030106@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --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 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.