mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Mattock <justinmattock@gmail.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Subject: Re: [PATCH] Update the e-mail for the userspace tools to use  ohci1394_dma=early for debugging.
Date: Sun, 4 Oct 2009 17:23:21 -0700	[thread overview]
Message-ID: <dd18b0c30910041723p9b503f3ta84867d6ec241db9@mail.gmail.com> (raw)
In-Reply-To: <tkrat.f4970b0de587f089@s5r6.in-berlin.de>

On Sat, Oct 3, 2009 at 1:15 AM, Stefan Richter
<stefanr@s5r6.in-berlin.de> wrote:
> On 29 Sep, Justin P. Mattock wrote:
>> ---
>>  Documentation/debugging-via-ohci1394.txt |    8 ++++----
>>  1 files changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/Documentation/debugging-via-ohci1394.txt b/Documentation/debugging-via-ohci1394.txt
>> index 59a91e5..8be3c78 100644
>> --- a/Documentation/debugging-via-ohci1394.txt
>> +++ b/Documentation/debugging-via-ohci1394.txt
>> @@ -64,14 +64,14 @@ be used to view the printk buffer of a remote machine, even with live update.
>>
>>  Bernhard Kaindl enhanced firescope to support accessing 64-bit machines
>>  from 32-bit firescope and vice versa:
>> -- ftp://ftp.suse.de/private/bk/firewire/tools/firescope-0.2.2.tar.bz2
>> +- http://halobates.de/firewire/firescope-0.2.2.tar.bz2
>>
>>  and he implemented fast system dump (alpha version - read README.txt):
>> -- ftp://ftp.suse.de/private/bk/firewire/tools/firedump-0.1.tar.bz2
>> +- http://halobates.de/firewire/firedump-0.1.tar.bz2
>>
>>  There is also a gdb proxy for firewire which allows to use gdb to access
>>  data which can be referenced from symbols found by gdb in vmlinux:
>> -- ftp://ftp.suse.de/private/bk/firewire/tools/fireproxy-0.33.tar.bz2
>> +- http://halobates.de/firewire/fireproxy-0.33.tar.bz2
>>
>>  The latest version of this gdb proxy (fireproxy-0.34) can communicate (not
>>  yet stable) with kgdb over an memory-based communication module (kgdbom).
>> @@ -178,7 +178,7 @@ Step-by-step instructions for using firescope with early OHCI initialization:
>>
>>  Notes
>>  -----
>> -Documentation and specifications: ftp://ftp.suse.de/private/bk/firewire/docs
>> +Documentation and specifications: http://halobates.de/firewire/
>>
>>  FireWire is a trademark of Apple Inc. - for more information please refer to:
>>  http://en.wikipedia.org/wiki/FireWire
>
> I don't see this patch in linux-next yet, hence I picked it up committed
> it to linux1394-2.6.git.
> --
> Stefan Richter
> -=====-==--= =-=- ---==
> http://arcgraph.de/sr/
>
>

Alright cool.

-- 
Justin P. Mattock

      parent reply	other threads:[~2009-10-05  0:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29 22:13 Update_e-mail-for-debugging-via-ohci1394.txt Justin P. Mattock
2009-09-29 22:13 ` [PATCH] Update the e-mail for the userspace tools to use ohci1394_dma=early for debugging. Signed-off-by: Justin P. Mattock <justinmattock@gmail.com> Justin P. Mattock
2009-10-03  8:15   ` [PATCH] Update the e-mail for the userspace tools to use ohci1394_dma=early for debugging Stefan Richter
2009-10-03  8:17     ` [PATCH] ieee1394: add documentation entry to MAINTAINERS Stefan Richter
2009-10-05  0:23     ` Justin Mattock [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=dd18b0c30910041723p9b503f3ta84867d6ec241db9@mail.gmail.com \
    --to=justinmattock@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=stefanr@s5r6.in-berlin.de \
    /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®