From: Takashi Iwai <tiwai@suse.de>
To: Andrew de Quincey <adq_dvb@lidskialf.net>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Patch to enable IR on Audigy 2 Drive
Date: Tue, 11 Mar 2003 17:43:05 +0100 [thread overview]
Message-ID: <s5h7kb53ld2.wl@alsa2.suse.de> (raw)
In-Reply-To: <200303102231.31227.adq_dvb@lidskialf.net>
At Mon, 10 Mar 2003 22:31:31 +0000,
Andrew de Quincey wrote:
>
>
> Hi, I've been having a frustrating couple of days getting IR to work on my
> brand new Audigy2 drive... Lots of people seem to have it working, but for
> me, it refused. Enabling it under windows showed that the IR _did_ work, and
> if I rebooted immediately into linux, IR worked there too (although not after
> a power cycle).
>
> It turns out the Audigy2 (and maybe the Audigy as well? I don't know) has a
> different port (A_IOCFG instead of A_HCFG) for accessing the GPIO
> registers... This is actually in the OSS driver, but hadn't made it across to
> ALSA. I assume the people who had this working were all using the OSS driver.
>
> I'd like to point out that I've only done this for the IR.. it might be an
> idea to check the ALSA emu101k source for other occurences of this for the
> Audigy2..
>
> Here's a patch against CVS to the IR enabling code.
thanks, applied to cvs now.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
prev parent reply other threads:[~2003-03-11 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 22:31 Patch to enable IR on Audigy 2 Drive Andrew de Quincey
2003-03-10 23:22 ` Andrew de Quincey
2003-03-11 16:43 ` Takashi Iwai [this message]
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=s5h7kb53ld2.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=adq_dvb@lidskialf.net \
--cc=alsa-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