alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: holger@dehnhardt.org
To: alsa-devel@alsa-project.org
Subject: Re: MOTU Midi Express XT
Date: Thu, 27 Oct 2016 20:28:10 +0000	[thread overview]
Message-ID: <2e5e4e51f4f2c63ecab719a1937d695f@owncloud.dehnhardt.org> (raw)
In-Reply-To: <9d5810a657a4fb63805acea778570a49@owncloud.dehnhardt.org>

27. Oktober 2016 18:22 Uhr, holger@dehnhardt.org schrieb:

> 27. Oktober 2016 08:42 Uhr, "Clemens Ladisch" <clemens@ladisch.de> schrieb:
> 
>> holger@dehnhardt.org wrote:
>> 
>>> I own a MOTU Midi Express XT 8x8 interface which is connected through the parallel port. Recently
>>> I upgraded my system and the new motherboard does not have an ISA parallel port anymore...
>>> So I bought a PCI parallel port extension card
>> 
>> Does it happen to have a name? Is it compatible with the ISA parallel port?
>> 
>> Regards,
>> Clemens
> 
> Ok, this is the lspci output for the card:
> 
> 06:00.0 Parallel controller: MosChip Semiconductor Technology Ltd. Device 9900 (prog-if 03
> [IEEE1284])
> Subsystem: Device a000:2000
> Flags: bus master, fast devsel, latency 0, IRQ 10
> I/O ports at b010 [size=8]
> I/O ports at b000 [size=8]
> Memory at fe201000 (32-bit, non-prefetchable) [size=4K]
> Memory at fe200000 (32-bit, non-prefetchable) [size=4K]
> Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
> Capabilities: [78] Power Management version 3
> Capabilities: [80] Express Legacy Endpoint, MSI 00
> Capabilities: [100] Virtual Channel
> Capabilities: [800] Advanced Error Reporting
> 
> The card is the following:
> https://www.conrad.de/de/1-port-serielle-steckkarte-pcie-972542.html
> 
> Can such a card be compatible with an ISA-Port?
> 
> Holger

I made a new observation. When loading the driver the PC-port LED blinks. At line 339 function
snd_mtpav_portscan some bytes are send to the device. This seems to work - which means the
communication between the PC and the device seems to work.

But why is the driver loaded but not registered?

Holger

  parent reply	other threads:[~2016-10-27 20:28 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 [this message]
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
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=2e5e4e51f4f2c63ecab719a1937d695f@owncloud.dehnhardt.org \
    --to=holger@dehnhardt.org \
    --cc=alsa-devel@alsa-project.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 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).