From: Parag Warudkar <kernel-stuff@comcast.net>
To: "Clyde Griffin" <CGRIFFIN@novell.com>
Cc: linux-kernel@vger.kernel.org, "Jan Beulich" <JBeulich@novell.com>
Subject: Re: Novell Linux Kernel Debugger (NLKD)
Date: Thu, 23 Jun 2005 17:14:26 -0400 [thread overview]
Message-ID: <200506231714.27022.kernel-stuff@comcast.net> (raw)
In-Reply-To: <s2bae938.075@sinclair.provo.novell.com>
On Thursday 23 June 2005 18:54, Clyde Griffin wrote:
> At this point the intent of this project is to gather comments and
> suggestions on how to improve NLKD and make it possible for NLKD to be
> included as a native (mainline) kernel debugger for Linux. Novell
> engineering will be actively involved in reviewing comments regarding NLKD
> and submitting and receiving patches for the support of NLKD.
Does / Will it support remote debugging over firewire ports? I think this
would be a great opportunity to get rid of the serial port requirement for
debugging.
Parag
next prev parent reply other threads:[~2005-06-23 23:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 22:54 Novell Linux Kernel Debugger (NLKD) Clyde Griffin
2005-06-23 21:14 ` Parag Warudkar [this message]
2005-06-23 23:43 ` Greg KH
2005-06-24 0:24 ` Christoph Lameter
2005-06-24 0:35 ` John W. Linville
2005-06-24 0:17 ` jmerkey
2005-06-24 1:56 ` Rik Van Riel
2005-06-24 0:31 ` jmerkey
2005-06-24 6:21 ` Jan Beulich
2005-06-24 4:59 ` jmerkey
2005-06-24 11:50 ` Chris Mason
2005-06-24 15:55 ` jmerkey
2005-06-24 18:16 ` Chris Mason
2005-06-24 17:15 ` jmerkey
2005-06-24 19:29 ` Lee Revell
2005-06-24 19:49 ` Christoph Lameter
2005-06-24 0:46 ` Christoph Lameter
2005-06-24 1:36 ` Rik Van Riel
2005-06-24 2:15 ` Keith Owens
2005-06-27 18:14 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2005-06-24 6:29 Jan Beulich
2005-06-24 7:38 Jan Beulich
2005-06-24 6:44 ` jmerkey
2005-06-24 8:26 ` Keith Owens
2005-06-24 12:02 ` Rik Van Riel
2005-06-27 6:46 ` Jan Beulich
2005-06-24 18:03 Clyde Griffin
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=200506231714.27022.kernel-stuff@comcast.net \
--to=kernel-stuff@comcast.net \
--cc=CGRIFFIN@novell.com \
--cc=JBeulich@novell.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