Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Guenther Sohler <guenther.sohler@newlogic.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: problems and questions with creative audixy
Date: Thu, 07 Feb 2002 18:15:23 +0100	[thread overview]
Message-ID: <s5hd6zhz00k.wl@alsa2.suse.de> (raw)
In-Reply-To: <s5heljxz17r.wl@alsa2.suse.de>

At Thu, 07 Feb 2002 17:49:28 +0100, I wrote:
> 
> > With my audixy all the 4 wavetable ports are fine but the midi ports do not work
> > If I try to access them, there is following error message issued:
> > alsa ../../alsa-kernel/pci/emu10k1/emumpu401.c:126 cmd 0xff failed at
> > 0xd400(status=0xff, data=0xff)
> > 
> > the same command is repeated with 0x3f isntead of 0xff after 126
>  
> Aggh, I find one here.  Will be fixed soon.  Thanks.

ok, now committed to cvs.  hopefully it works now..

BTW, there are two MIDI ports on audigy, the first one
/dev/snd/midiC0D0 is for the gameport and the second one midiC0D1 is
for the connector on external drive.


Takashi

_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

  reply	other threads:[~2002-02-07 17:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-07 16:35 problems and questions with creative audixy Guenther Sohler
2002-02-07 16:49 ` Takashi Iwai
2002-02-07 17:15   ` Takashi Iwai [this message]
     [not found]     ` <XFMail.020207182710.guenther.sohler@newlogic.com>
2002-02-07 17:39       ` Takashi Iwai
2002-02-08  6:24         ` stupid question about pcm devices Guenther Sohler
2002-02-08  7:42           ` Jaroslav Kysela
2002-02-08 14:48           ` Paul Davis
2002-02-08 11:39         ` emu10k1 specification Guenther Sohler
2002-02-08 11:54           ` Jaroslav Kysela

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=s5hd6zhz00k.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=guenther.sohler@newlogic.com \
    /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