From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001654]: Support for Midiman (M-audio) Biport 2x4s
Date: Fri, 4 Aug 2006 01:03:52 +0200 [thread overview]
Message-ID: <c1ca661cbedeadc72bf0e7b575ac9cf4@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1654>
======================================================================
Reported By: pumpkin
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1654
Category: GENERIC - serialmidi
Reproducibility: always
Severity: major
Priority: normal
Status: closed
Distribution: slackware 10.2
Kernel Version:
Resolution: unable to duplicate
Fixed in Version:
======================================================================
Date Submitted: 12-15-2005 23:21 CET
Last Modified: 08-04-2006 01:03 CEST
======================================================================
Summary: Support for Midiman (M-audio) Biport 2x4s
Description:
I have a Midiman Biport 2x4s (a midi-interface that connects to the
serial-port) that I cant get to work in Linux. I have seen that there is
support for many other midi-interfaces by Midiman (M-audio) in ALSA but I
havent seen support for my model. I have searched the internet and asked
around for drivers and stuff to get it to work but with no luck so far.
Is there support for my model that I havent found yet? and if not, will
there be any support for my model soon?
unfortunately I am pretty new to linux so I cant make my own driver so I
am happy for all the help I can get.
======================================================================
----------------------------------------------------------------------
Clemens Ladisch - 12-16-05 09:12
----------------------------------------------------------------------
Most serial MIDI interfaces use a Sound Canvas compatible protocol.
Does it work with the following commands?
setserial /dev/ttyS0 uart none
modprobe snd-serial-u16550 port=0x3f8 irq=4 outs=4 ins=2 adaptor=0
Issue History
Date Modified Username Field Change
======================================================================
12-15-05 23:21 pumpkin New Issue
12-15-05 23:21 pumpkin Distribution => slackware 10.2
12-15-05 23:22 pumpkin Issue Monitored: pumpkin
12-16-05 09:12 Clemens LadischNote Added: 0007057
08-04-06 01:03 Adrian Bunk Status new => closed
08-04-06 01:03 Adrian Bunk Resolution open => unable to
duplicate
======================================================================
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next reply other threads:[~2006-08-03 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 23:03 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-16 8:12 [ALSA - driver 0001654]: Support for Midiman (M-audio) Biport 2x4s bugtrack
2005-12-15 22:21 bugtrack
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=c1ca661cbedeadc72bf0e7b575ac9cf4@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.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