From: Andi Kleen <andi@firstfloor.org>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>, Jun Koi <junkoi2004@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Firewire debugging tools - firedump & fireproxy?
Date: Thu, 30 Jul 2009 17:49:04 +0200 [thread overview]
Message-ID: <20090730154904.GD4534@basil.fritz.box> (raw)
In-Reply-To: <1248968242.3624.28.camel@maxim-laptop>
> Don't know what to say about what I could do to help...
> I could help to make this tool better, don't know how much time will
> permit me, or at least I think that kgdbom can be merged almost as is
> already.
Cleaning up the patch and submitting it would be great yes.
One problem with firewire as it stands is that it doesn't support
more 4GB of memory and doesn't work with IOMMUs. But for limited
situations it's quite good.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2009-07-30 15:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-05 5:42 Firewire debugging tools - firedump & fireproxy? Jun Koi
2009-07-30 5:36 ` Maxim Levitsky
2009-07-30 7:01 ` Jun Koi
2009-07-30 8:31 ` Jason Wessel
2009-07-30 20:57 ` Maxim Levitsky
2009-07-30 21:10 ` Jason Wessel
2009-07-31 4:55 ` Maxim Levitsky
2009-07-30 9:43 ` Andi Kleen
2009-07-30 15:37 ` Maxim Levitsky
2009-07-30 15:49 ` Andi Kleen [this message]
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=20090730154904.GD4534@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=junkoi2004@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maximlevitsky@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