From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Jonathan Woithe <jwoithe@just42.net>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org, clemens@ladisch.de,
ffado-devel@lists.sf.net
Subject: Re: [RFC][PATCH 0/3] ALSA: fireface: new driver for RME Fireface series (MIDI only)
Date: Mon, 7 Dec 2015 10:27:08 +0900 [thread overview]
Message-ID: <5664E06C.9080705@sakamocchi.jp> (raw)
In-Reply-To: <20151206215744.GA6103@marvin.atrad.com.au>
Hi,
On Dec 07 2015 06:57, Jonathan Woithe wrote:
> On Sun, Dec 06, 2015 at 10:23:41PM +0900, Takashi Sakamoto wrote:
>> Unfortunately, ffado library can disturb this functionality.
>> In RME::Device::init_hardware() function, the library sends a write transaction
>> to 0x0000801003f4 with invalid value as higher part of address in IEEE 1212 or
>> ISO/IEC 13213. This is a worst case I describe in patch 03.
>
> The number which FFADO writes to this register is not invalid: it is in fact
> the same number which is used in drivers on other operating systems
> (obtained from protocol analysis).
No.
As long as I tested with a debug option to firewire-ohci module, it
sends write transaction with '01000000'. This value includes invalid
node ID.
ConfigRom::getNodeId() returns the invalid value. I think there's
something wrong coding, such like forgetting initialization or update of
the instance.
>> I think it better that FFADO developers fixes the bug as long as they doesn't
>> support MIDI functionality.
>
> As above, this is not exactly a bug because other systems set that register
> to the value which FFADO uses. In the interests of interoperability I'm
> willing to remove manipulation of this register from FFADO, but I suggest
> that in time the ALSA driver should consider setting this register as is
> done under other systems or else we could introduce subtle behavioural
> differences down the track - at least until such time as we understand what
> the high part of that register does.
Regards
Takashi Sakamoto
next prev parent reply other threads:[~2015-12-07 1:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 13:23 [RFC][PATCH 0/3] ALSA: fireface: new driver for RME Fireface series (MIDI only) Takashi Sakamoto
2015-12-06 13:23 ` [PATCH 1/3] fireface: add skeleton for RME Fireface series Takashi Sakamoto
2015-12-06 22:13 ` [FFADO-devel] " Jonathan Woithe
2015-12-07 1:32 ` Takashi Sakamoto
2015-12-07 2:05 ` Jonathan Woithe
2015-12-06 13:23 ` [PATCH 2/3] fireface: add transaction support Takashi Sakamoto
2015-12-08 10:22 ` Clemens Ladisch
2015-12-08 11:25 ` Takashi Sakamoto
2015-12-08 11:29 ` Clemens Ladisch
2015-12-08 12:20 ` Takashi Sakamoto
2015-12-08 12:36 ` Clemens Ladisch
2015-12-10 11:31 ` Takashi Sakamoto
2015-12-06 13:23 ` [PATCH 3/3] fireface: add support for MIDI functionality Takashi Sakamoto
2015-12-06 14:29 ` [FFADO-devel] [RFC][PATCH 0/3] ALSA: fireface: new driver for RME Fireface series (MIDI only) Илья
2015-12-06 21:57 ` Jonathan Woithe
2015-12-07 1:27 ` Takashi Sakamoto [this message]
2015-12-07 1:37 ` Jonathan Woithe
2015-12-07 1:52 ` Takashi Sakamoto
2015-12-07 2:05 ` Takashi Sakamoto
2015-12-07 2:21 ` Jonathan Woithe
2015-12-07 2:42 ` Takashi Sakamoto
2015-12-07 3:01 ` Jonathan Woithe
2015-12-07 7:37 ` Clemens Ladisch
2015-12-07 8:41 ` Jonathan Woithe
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=5664E06C.9080705@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=ffado-devel@lists.sf.net \
--cc=jwoithe@just42.net \
--cc=tiwai@suse.de \
/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.