Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Sean M. Pappalardo - D.J. Pegasus" <spappalardo@mixxx.org>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org, linux1394-devel@lists.sourceforge.net
Subject: Re: Help requested: new HSS1394 MIDI back-end
Date: Sun, 27 May 2012 22:59:25 +0200	[thread overview]
Message-ID: <4FC295AD.1030901@mixxx.org> (raw)
In-Reply-To: <4FC23123.8000702@ladisch.de>


[-- Attachment #1.1: Type: text/plain, Size: 2232 bytes --]

Hello again.

On 05/27/2012 03:50 PM, Clemens Ladisch wrote:
> See the document "Writing an ALSA Driver", and look at the source code
> of other MIDI drivers, such as, for example, sound/usb/midi.c or the
> (untested) patch below.

Holy crap!! Thank you so much for that patch, Clemens! I just updated my 
kernel and tried it with the SCS.1m but unfortunately it reports an error:

firewire_ohci: isochronous cycle inconsistent
firewire_core: created device fw1: GUID 0012600000000000, S400
firewire_core: phy config: card 0, new root=ffc0, gap_count=5
snd_scs1x fw1.0: transaction failed: type error
snd_scs1x: probe of fw1.0 failed with error -5

Turning on the SCS.1d then yields:
firewire_core: phy config: card 0, new root=ffc2, gap_count=7
firewire_core: phy config: card 0, new root=ffc2, gap_count=7
firewire_core: created device fw2: GUID 0012600100000000, S400


I'm guessing the type error is around line 254 in scs1x.c, but where 
does tcode come from? (I'm totally green with systems and Firewire 
programming.) I glanced at the MIDI section of that "writing a driver" 
PDF before I wrote to this list. I guess I'll go actually read it now. :)

FYI, I'm now on kernel 3.2.18-rt23 #2 SMP PREEMPT x86_64.

> BTW: What is the output of "lsfirewire -v" for these devices?

device fw1:
   vendor ID: 0x001260
   model ID: 0x001000
   vendor: Stanton DJ
   model: SCS.1m
   guid: 0x0012600000000000
   units: 0x00a02d:0x010001
   unit fw1.0:
     model ID: 0x001000
     model: SCS.1m
     specifier ID: 0x00a02d
     version: 0x010001
device fw2:
   vendor ID: 0x001260
   model ID: 0x002000
   vendor: Stanton DJ
   model: SCS.1d
   guid: 0x0012600100000000
   units: 0x00a02d:0x010001
   unit fw2.0:
     model ID: 0x002000
     model: SCS.1d
     specifier ID: 0x00a02d
     version: 0x010001


bus 0, node 0: 080028:424296  Texas Instruments TSB41AB1/2
bus 0, node 1: 080028:424296  Texas Instruments TSB41AB1/2

I tried poking around with firewire-request read but didn't find 
anything interesting. (Then again, I don't really know what I'm looking 
at or for.)

Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"
Mixxx Developer - Controller Specialist


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4545 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2012-05-27 20: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 [this message]
2012-05-28 14:58     ` Clemens Ladisch
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=4FC295AD.1030901@mixxx.org \
    --to=spappalardo@mixxx.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=linux1394-devel@lists.sourceforge.net \
    /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