All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: "Sean M. Pappalardo - D.J. Pegasus" <spappalardo@mixxx.org>
Cc: alsa-devel@alsa-project.org, linux1394-devel@lists.sourceforge.net
Subject: Re: Help requested: new HSS1394 MIDI back-end
Date: Mon, 28 May 2012 16:58:39 +0200	[thread overview]
Message-ID: <4FC3929F.4050304@ladisch.de> (raw)
In-Reply-To: <4FC295AD.1030901@mixxx.org>

Sean M. Pappalardo - D.J. Pegasus wrote:
> I just updated my kernel and tried it with the SCS.1m but unfortunately it reports an error:
>
> firewire_core: created device fw1: GUID 0012600000000000, S400
> snd_scs1x fw1.0: transaction failed: type error

This is from a snd_fw_transaction call, either the ping or the address
setting.

Please check if these commands work:

	firewire-request /dev/fwX read c007dedadada 4
	firewire-request /dev/fwX write c007dedadada f100123456789abc

In theory, you should be able to write MIDI commands by prefixing them
with 00, like this for a note-on:
	firewire-request /dev/fwX write c007dedadada 00912345

> Turning on the SCS.1d then yields:
> firewire_core: created device fw2: GUID 0012600100000000, S400

FFADO had only the 1m's ID, so the driver does not yet know about the 1d.


Regards,
Clemens

  reply	other threads:[~2012-05-28 14:59 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-25 19:43 Help requested: new HSS1394 MIDI back-end Sean M. Pappalardo - D.J. Pegasus
2012-05-27 13:50 ` Clemens Ladisch
2012-05-27 20:59   ` Sean M. Pappalardo - D.J. Pegasus
2012-05-28 14:58     ` Clemens Ladisch [this message]
2012-05-28 20:40       ` Sean M. Pappalardo - D.J. Pegasus
2012-05-29 17:05         ` Clemens Ladisch
2012-05-29 21:52           ` Sean M. Pappalardo - D.J. Pegasus
2012-07-24 11:44             ` Clemens Ladisch
2012-08-01 17:16               ` Sean M. Pappalardo - D.J. Pegasus
     [not found] <94aa86f3-5257-402a-a094-f58fccdeb846@email.android.com>
2012-05-30  4:51 ` Clemens Ladisch
2012-05-30  5:12   ` [alsa-devel] " Sean M. Pappalardo - D.J. Pegasus
2012-05-30  7:18     ` Clemens Ladisch
2012-05-31 20:00       ` Clemens Ladisch
2012-06-09  6:54         ` Sean M. Pappalardo - D.J. Pegasus
2012-06-09 11:07           ` Clemens Ladisch
2012-06-09 12:41             ` Sean M. Pappalardo - D.J. Pegasus
2012-06-10 13:00             ` Clemens Ladisch
2012-10-24 11:49               ` Sean M. Pappalardo - D.J. Pegasus
2012-10-25 19:23                 ` Clemens Ladisch
2012-10-25 20:26                   ` Sean M. Pappalardo - D.J. Pegasus
2012-10-26  7:48                     ` Clemens Ladisch
2012-10-31 10:00                   ` Sean M. Pappalardo - D.J. Pegasus
2012-11-09  6:41                   ` Sean M. Pappalardo - D.J. Pegasus
2012-11-12  9:45                   ` Takashi Iwai
2012-11-12 11:33                     ` Clemens Ladisch
2012-11-12 11:40                       ` Takashi Iwai
2012-06-09  8:42         ` Sean M. Pappalardo - D.J. Pegasus
2012-06-09 10:12         ` Sean M. Pappalardo - D.J. Pegasus
2012-05-31 22:04       ` Sean M. Pappalardo - D.J. Pegasus
2012-06-01  8:22         ` Clemens Ladisch
     [not found] <mailman.786.1339244201.2490.alsa-devel@alsa-project.org>
2012-06-09 12:56 ` 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=4FC3929F.4050304@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=spappalardo@mixxx.org \
    /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.