mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Jun Koi <junkoi2004@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Jason Wessel <jason.wessel@windriver.com>,
	Bernhard Kaindl <bk@suse.de>
Subject: Re: Firewire debugging tools - firedump & fireproxy?
Date: Thu, 30 Jul 2009 08:36:58 +0300	[thread overview]
Message-ID: <1248932218.27010.8.camel@maxim-laptop> (raw)
In-Reply-To: <fdaac4d50907042242s6534d63at12a26df47a0f3b2a@mail.gmail.com>

On Sun, 2009-07-05 at 14:42 +0900, Jun Koi wrote:
> Hi,
> 
> I am doing some debugging via firewire. I found some references to
> some tools named firedump & fireproxy, made by Bernhard Kaindl,
> supposed put at following addresses:
> 
> ftp://ftp.suse.de/private/bk/firewire/tools/firedump-0.1.tar.bz2
> ftp://ftp.suse.de/private/bk/firewire/tools/fireproxy-0.33.tar.bz2
> 
> However, these URLs are nolonger available. I am wondering if they
> have been moved to somewhere else? Anybody know?
> 
> Thanks,
> J
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Me having the same question. I have just bought everything for firewire
debugging.

Jason Wessel, what the fate of kgdbom ?
(and kgdboe btw ....)

Best regards,
	Maxim Levitsky



  reply	other threads:[~2009-07-30  5:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-05  5:42 Jun Koi
2009-07-30  5:36 ` Maxim Levitsky [this message]
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

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=1248932218.27010.8.camel@maxim-laptop \
    --to=maximlevitsky@gmail.com \
    --cc=bk@suse.de \
    --cc=jason.wessel@windriver.com \
    --cc=junkoi2004@gmail.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

all inboxes | Powered by JetHome®