From: Andi Kleen <ak@muc.de>
To: George Anzinger <george@mvista.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [discuss] Re: kgdb for x86_64 2.6 kernels
Date: Thu, 15 Jan 2004 09:02:38 +0100 [thread overview]
Message-ID: <m3ptdlwsf5.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <1e3fi-4nG-5@gated-at.bofh.it> (George Anzinger's message of "Thu, 15 Jan 2004 01:10:08 +0100")
George Anzinger <george@mvista.com> writes:
>> Raw USB? Or some kind of USB to serial device?
>> Remember, USB needs interrupts to work, see the kdb patches for the
>> mess
>> that people have tried to go through to send usb data without interrupts
>> (doesn't really work...)
>
> I gave up on USB when I asked the following questions:
There is a special "USB debugport" specification available that allows
to drive USB very simply using PIO without too much set up. It should
be implemented in most chipsets by now because that other operating
system is using it.
See e.g. http://www.usb.org/developers/presentations/pres0602/john_keys.pdf
It works with a simple "debug dongle", that is identical to the
USB networking cables that are often sold cheaply.
If you want to port kgdb to use USB I would use that. USB console
would also be very useful for debugging laptops and some systems
with no USB.
-Andi
next parent reply other threads:[~2004-01-15 8:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1cd9t-4Su-65@gated-at.bofh.it>
[not found] ` <1coR2-42n-19@gated-at.bofh.it>
[not found] ` <1d3r0-1tw-3@gated-at.bofh.it>
[not found] ` <1dbI9-89t-7@gated-at.bofh.it>
[not found] ` <1dEqx-F0-1@gated-at.bofh.it>
[not found] ` <1dMRc-6DQ-3@gated-at.bofh.it>
[not found] ` <1e2Mk-6YA-17@gated-at.bofh.it>
[not found] ` <1e2Mo-6YA-31@gated-at.bofh.it>
[not found] ` <1e3fi-4nG-5@gated-at.bofh.it>
2004-01-15 8:02 ` Andi Kleen [this message]
2004-01-15 8:36 ` [discuss] Re: kgdb for x86_64 2.6 kernels George Anzinger
2004-01-15 8:52 ` Andi Kleen
2004-01-16 1:15 ` Matt Mackall
2004-01-16 18:04 ` Randy.Dunlap
2004-01-16 21:07 ` Andi Kleen
[not found] <000e01c3d476$2ebe03a0$4008720a@shivram.wipro.com>
[not found] ` <1073603622.993.353.camel@new.localdomain>
[not found] ` <20040108153243.11e45156.akpm@osdl.org>
[not found] ` <200401091031.41493.amitkale@emsyssoft.com>
2004-01-09 22:16 ` George Anzinger
2004-01-10 10:41 ` Amit S. Kale
2004-01-10 15:03 ` Pavel Machek
2004-01-10 18:14 ` Pavel Machek
2004-01-12 14:32 ` Amit S. Kale
2004-01-10 19:30 ` Pavel Machek
2004-01-12 14:31 ` Amit S. Kale
2004-01-12 6:00 ` George Anzinger
2004-01-12 9:47 ` Pavel Machek
2004-01-13 20:55 ` George Anzinger
2004-01-12 14:50 ` Amit S. Kale
2004-01-13 21:26 ` George Anzinger
2004-01-14 6:31 ` Matt Mackall
2004-01-14 20:02 ` George Anzinger
2004-01-14 23:26 ` Greg KH
2004-01-15 0:02 ` George Anzinger
2004-01-15 0:19 ` Pavel Machek
2004-01-15 3:28 ` George Anzinger
2004-01-15 0:23 ` Greg KH
2004-01-15 3:30 ` George Anzinger
2004-01-14 13:24 ` Amit S. Kale
2004-01-14 22:32 ` George Anzinger
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=m3ptdlwsf5.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=george@mvista.com \
--cc=linux-kernel@vger.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