From: holger@dehnhardt.org
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: MOTU Midi Express XT
Date: Mon, 31 Oct 2016 20:10:39 +0000 [thread overview]
Message-ID: <dfc508c06ed983cc3b712adea386d873@owncloud.dehnhardt.org> (raw)
In-Reply-To: <0ee7780b-d697-ace0-99bb-07ac36b710e1@ladisch.de>
Thanks for answering, Clemens. Comments are inline.
> In theory, this indicates that the driver has been initialized correctly.
> But it doesn't actually check if the device is there.
>
> A PCI device needs to be enabled before it can be used, and this driver
> does not know about PCI.
It looks like the driver does not care about that.
>
> The partport-serial driver gets loaded, doesn't it?
It can be loaded but is not loaded by default as mtpav does not work if any other parport driver is
loaded.
>> I added a print statement to to __init function (see the code and arrow -> below).
>> It initialises without error.
>>
>> static int __init alsa_card_mtpav_init(void)
>
> The actual device initialization is in snd_mptav_probe().
Ok, this is where the default message: "Motu MidiTimePiece on parallel port irq: %d ioport: 0x%lx\n" is written from. So there is no error too.
BTW: lsmod |grep snd_mtpav shows, that it is using snd_rawmidi...
snd_mtpav 16384 0
snd_rawmidi 32768 2 snd_mtpav,snd_seq_midi
snd 81920 5 snd_mtpav,snd_timer,snd_seq,snd_rawmidi,snd_seq_device
Was there a recent api change? More and more it looks like there is a problem with registering the driver / the port to the ALSA system.
Holger
next prev parent reply other threads:[~2016-10-31 20:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 6:16 MOTU Midi Express XT holger
2016-10-27 6:40 ` Clemens Ladisch
2016-10-27 7:03 ` holger
2016-10-27 16:22 ` holger
2016-10-27 19:11 ` holger
2016-10-27 20:28 ` holger
2016-10-29 15:52 ` holger
2016-10-29 16:33 ` Clemens Ladisch
2016-10-29 19:25 ` holger
2016-10-30 20:12 ` holger
2016-10-31 15:01 ` Clemens Ladisch
2016-10-31 20:10 ` holger [this message]
2025-11-06 4:53 ` [alsa-devel] " tynsareatger
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=dfc508c06ed983cc3b712adea386d873@owncloud.dehnhardt.org \
--to=holger@dehnhardt.org \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).