On 12/13/06, Stefan Richter <[EMAIL PROTECTED]> wrote:
How about leaving ohci1394 as it is but document tag_mask better in
libraw1394's inline doxygen(?) comments, and maybe add an enum or macros
to be used as values of raw1394_iso_recv_start's tag_mask argument?
/* can be ORed together */
On 12/13/06, Stefan Richter [EMAIL PROTECTED] wrote:
How about leaving ohci1394 as it is but document tag_mask better in
libraw1394's inline doxygen(?) comments, and maybe add an enum or macros
to be used as values of raw1394_iso_recv_start's tag_mask argument?
/* can be ORed together */
Robert Crocombe wrote:
> I was setting the tag to -1 in a certain spot (which indicates
> that you want to see all packets, regardless of their tag), but
> unhelpfully changing it to 0 before calling raw1394_iso_recv_start...
>
> ...dangit, though. Looking at the data stream, the tag *is* zero.
On 11/29/06, Keith Curtis <[EMAIL PROTECTED]> 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
On 11/29/06, Keith Curtis [EMAIL PROTECTED] 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
Robert Crocombe wrote:
I was setting the tag to -1 in a certain spot (which indicates
that you want to see all packets, regardless of their tag), but
unhelpfully changing it to 0 before calling raw1394_iso_recv_start...
...dangit, though. Looking at the data stream, the tag *is* zero.
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
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
know, but I'm not sure where to start at this point.
Keith
-Original Message-
From: Robert Crocombe [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 28, 2006 4:59 PM
To: Keith Curtis; linux1394-devel; linux-kernel
Subject: isochronous receives?
Keith, et. al,
I am having problems
know, but I'm not sure where to start at this point.
Keith
-Original Message-
From: Robert Crocombe [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 28, 2006 4:59 PM
To: Keith Curtis; linux1394-devel; linux-kernel
Subject: isochronous receives?
Keith, et. al,
I am having problems
Keith, et. al,
I am having problems with isochronous receives, and remembered just as
I was getting ready to dig into the source that there was a message
about this stuff. Lo and behold your message to linux1394-user from
September 7:
I'm trying to receive isochronous streams (using
Keith, et. al,
I am having problems with isochronous receives, and remembered just as
I was getting ready to dig into the source that there was a message
about this stuff. Lo and behold your message to linux1394-user from
September 7:
I'm trying to receive isochronous streams (using
12 matches
Mail list logo
