linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: Torrey Hoffman <thoffman@arnor.net>, gaxt <gaxt@rogers.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux firewire devel <linux1394-devel@lists.sourceforge.net>
Subject: Re: Firewire
Date: Thu, 24 Jul 2003 22:19:55 -0400	[thread overview]
Message-ID: <20030725021955.GV1512@phunnypharm.org> (raw)
In-Reply-To: <20030725020027.GG23196@ruvolo.net>

On Thu, Jul 24, 2003 at 07:00:27PM -0700, Chris Ruvolo wrote:
> On Thu, Jul 24, 2003 at 09:29:08PM -0400, Ben Collins wrote:
> > Could both you guys try this workaround? Should prove or disprove my
> > theory.
> 
> Similar output (debug).  Diff of output and then full output follows.

Just noticed that this doesn't even have anything to do with ohci1394.
It's all local requests for config rom reads. Can you send me the debug
with the below patch applied?

Index: linux-2.6/drivers/ieee1394/ieee1394_core.c
===================================================================
--- linux-2.6/drivers/ieee1394/ieee1394_core.c	(revision 1013)
+++ linux-2.6/drivers/ieee1394/ieee1394_core.c	(working copy)
@@ -611,6 +611,7 @@
 
         list_for_each(lh, &host->pending_packets) {
                 packet = list_entry(lh, struct hpsb_packet, list);
+		HPSB_DEBUG("Checking tlabel %d\n", tlabel);
                 if ((packet->tlabel == tlabel)
                     && (packet->node_id == (data[1] >> 16))){
                         break;


-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/

  reply	other threads:[~2003-07-25  2:15 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24 13:34 Firewire gaxt
2003-07-24 22:35 ` Firewire Chris Ruvolo
2003-07-24 22:36   ` Firewire Ben Collins
2003-07-24 23:09     ` Firewire Chris Ruvolo
2003-07-24 23:14       ` Firewire Ben Collins
2003-07-24 23:48         ` Firewire Chris Ruvolo
2003-07-24 23:45           ` Firewire Ben Collins
2003-07-25  0:07             ` Firewire Chris Ruvolo
2003-07-25  0:14           ` Firewire Chris Ruvolo
2003-07-25  1:13       ` Firewire Torrey Hoffman
2003-07-25  1:27         ` Firewire Chris Ruvolo
2003-07-25  1:29           ` Firewire Ben Collins
2003-07-25  2:00             ` Firewire Chris Ruvolo
2003-07-25  2:19               ` Ben Collins [this message]
2003-07-25  3:23             ` Firewire Sam Bromley
2003-07-25  4:12               ` Firewire Ben Collins
2003-07-25  5:39                 ` Firewire Chris Ruvolo
2003-07-25 13:34                   ` Firewire Ben Collins
2003-07-25 14:06                     ` Firewire gaxt
2003-07-25 13:47                       ` Firewire Ben Collins
2003-07-25 14:23                         ` Firewire gaxt
2003-07-25 15:28                           ` Firewire gaxt
2003-07-25 14:29                     ` Firewire Chris Ruvolo
2003-07-25 14:29                       ` Firewire Ben Collins
2003-07-25 15:40                         ` Firewire Ben Collins
2003-07-25 16:07                           ` Firewire Chris Ruvolo
2003-07-25 16:18                             ` Firewire Ben Collins
2003-07-25 17:02                               ` Firewire Chris Ruvolo
2003-07-25 17:07                                 ` Firewire Ben Collins
2003-07-25 17:51                               ` Firewire Torrey Hoffman
2003-07-25 18:13                                 ` Firewire Chris Ruvolo
2003-07-25 18:12                                   ` Firewire Ben Collins
2003-07-25 18:43                                     ` Firewire gaxt
2003-07-25 18:26                                       ` Firewire Ben Collins
2003-07-25 18:45                                         ` Firewire Ben Collins
2003-07-25 19:16                                           ` Firewire gaxt
2003-07-25 19:35                                           ` Firewire Chris Ruvolo
2003-07-25 20:11                                             ` Firewire Ben Collins
2003-07-25 21:48                                               ` Firewire gaxt
2003-07-26  4:41                                               ` Firewire (One fix worked, now getting oops) Sam Bromley
2003-07-26 15:12                                                 ` Ben Collins
2003-07-26 17:41                                                   ` Sam Bromley
2003-07-26 17:45                                                     ` Ben Collins
2003-07-26 16:52                                               ` Firewire Chris Ruvolo
2003-07-26 17:45                                                 ` Firewire Ben Collins
2003-07-25 20:48                                             ` Firewire Torrey Hoffman
2003-07-25 20:44                                               ` Firewire Ben Collins
2003-07-25 18:18                                   ` Firewire Torrey Hoffman
2003-07-25 18:33                                   ` Firewire gaxt
2003-07-25 16:28                           ` Firewire gaxt
2003-07-25 15:53                         ` Firewire Chris Ruvolo
2003-07-25 15:47                           ` Firewire Ben Collins
2003-07-25 16:14                             ` Firewire Chris Ruvolo
2003-07-25 13:34                   ` Firewire Ben Collins

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=20030725021955.GV1512@phunnypharm.org \
    --to=bcollins@debian.org \
    --cc=gaxt@rogers.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=thoffman@arnor.net \
    /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).