From: Jon Masters <jonmasters@gmail.com>
To: linuxppc <linuxppc@4bridgeworks.com>
Cc: Linux PPC Dev <linuxppc-dev@ozlabs.org>
Subject: Re: Problem with PPC 440 GX Transmit Path
Date: Thu, 21 Oct 2004 15:53:56 +0100 [thread overview]
Message-ID: <35fb2e5904102107535069206b@mail.gmail.com> (raw)
In-Reply-To: <C18BA5DDB58DD511BD0700C0DF0DD4502941E6@NTSERVER4>
On Thu, 21 Oct 2004 15:20:55 +0100, linuxppc <linuxppc@4bridgeworks.com> wrote:
> Any help or guidance
> will be appreciated, for now I am going to try and implement gdb.....
Perhaps *any* form of useful output or description would be useful.
Could you please provide the specific line of debugging that you need
to retain at least?
Jon.
next prev parent reply other threads:[~2004-10-21 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 14:20 Problem with PPC 440 GX Transmit Path linuxppc
2004-10-21 14:53 ` Jon Masters [this message]
2004-10-21 17:49 ` Eugene Surovegin
-- strict thread matches above, loose matches on Subject: below --
2004-10-21 14:59 Daren Hayward
2004-10-21 21:02 Daren Hayward
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=35fb2e5904102107535069206b@mail.gmail.com \
--to=jonmasters@gmail.com \
--cc=jonathan@jonmasters.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc@4bridgeworks.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;
as well as URLs for NNTP newsgroup(s).