mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Keith Curtis <Keith.Curtis@digeo.com>
Cc: Robert Crocombe <rcrocomb@gmail.com>,
	linux1394-devel <linux1394-devel@lists.sourceforge.net>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: isochronous receives?
Date: Fri, 01 Dec 2006 11:30:53 +0100	[thread overview]
Message-ID: <4570045D.40100@s5r6.in-berlin.de> (raw)
In-Reply-To: <DD2010E58E069B40886650EE617FCC0CBA8EC9@digeo-mail1.digeo.com>

Keith Curtis wrote:
> I never resolved the problem. I turned on the excessive debugging output, but it 
> didn't print out info about receiving packets or interrupts. My test 
> app claimed there were no packets received although the bus analyzer 
> showed lots of packets going by.  
> 
> If I can help out, let me know, but I'm not sure where to start at this point.
...
> -----Original Message-----
> From: Robert Crocombe [mailto:rcrocomb@gmail.com]
> Sent: Tuesday, November 28, 2006 4:59 PM
...
> Did you ultimately have any success getting this going?  Funnily
> enough, when I tested isochronous stuff in July, I just did iso
> transmit since I figured receives *must* be working since everyone has
> camcorders and whatnot.  My currently my iso xmit stuff does appear to
> be working, but iso receives are not.
> 
> I have a Firespy and no reason not to trust it, so I can see the junk
> I'm spewing out.  I've tried transmitting on channels 4 and 63 (per
> your advice), but neither works for me.  I suppose it could my
> stuff... nah.

I don't know much about the mechanisms, but I suppose there could be one
of the following causes:
 - The IR DMA context was never set up for the respective channel in the
   first place.
 - The context was set up but the interrupt event masks weren't switched
   on, i.e. IntMask as per OHCI clause 6.2 and isoRecvIntMask as per
   clause 6.3.2.
 - The context and masks were set up, but then one or both of the masks
   were switched off again, similar to the bus reset bug which Robert
   reported: http://bugzilla.kernel.org/show_bug.cgi?id=7569
-- 
Stefan Richter
-=====-=-==- ==-- ----=
http://arcgraph.de/sr/

  reply	other threads:[~2006-12-01 10:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AccTUZEOi7v6J84+R+eLGKj8lA2txQAz+0pA>
2006-11-30  1:57 ` Keith Curtis
2006-12-01 10:30   ` Stefan Richter [this message]
2006-12-13 14:30   ` Robert Crocombe
2006-12-13 18:27     ` Stefan Richter
2006-12-13 23:15       ` Stefan Richter
2006-12-14 18:23       ` Robert Crocombe
2006-11-29  0:59 Robert Crocombe

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=4570045D.40100@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=Keith.Curtis@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=rcrocomb@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

all inboxes | Powered by JetHome®