From: Clemens Ladisch <clemens@ladisch.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org
Subject: Re: firewire-lib: an issue to generate packet with 'no data' in blocking mode
Date: Fri, 22 Nov 2013 12:47:46 +0100 [thread overview]
Message-ID: <528F4462.3000909@ladisch.de> (raw)
In-Reply-To: <528EF2DE.9060700@sakamocchi.jp>
Takashi Sakamoto wrote:
> I have a question about generate packet with 'no data' in blocking mode.
> I think there is out of specification in current firewire-lib.
>
> In my understanding of IEC 61883-6, there are two ways:
>
> 1. generate 'empty packet' defined in IEC 61883-1
> - size of packet is 2 quadlets
> - FDF = sfc
> - packet includes just CIP headers
>
> 2. generate 'special non-empty packet' defined in IEC 61883-6
> - size of packet is following to blocking mode
> - FDF = 0xff ('NO-DATA' code)
> - packet includes dummy data
>
> But current implementation is a strange combination of them.
> - size of packet is 2 (way 1)
> - FDF = 0xff (way 2)
It's an empty NO-DATA packet. ;-)
I guess I just didn't notice that empty packets don't need to change
their FDF field. This is a bug.
> If this is a qurk for some devices, I'll prepare patches to switch
> generating mode because BeBoB cannot sound with current firewire-lib. If
> this is a bug, then I want to discuss which is better for firewire-lib.
Empty packets should be fine for all devices. (NO-DATA packets would
waste DMA bandwidth.)
Regards,
Clemens
next prev parent reply other threads:[~2013-11-22 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 5:59 firewire-lib: an issue to generate packet with 'no data' in blocking mode Takashi Sakamoto
2013-11-22 11:47 ` Clemens Ladisch [this message]
2013-11-22 13:53 ` Takashi Sakamoto
2013-11-22 13:58 ` Clemens Ladisch
2013-11-22 14:50 ` Takashi Iwai
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=528F4462.3000909@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=o-takashi@sakamocchi.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.