From: Takashi Iwai <tiwai@suse.de>
To: James@superbug.co.uk
Cc: Lee Revell <rlrevell@joe-job.com>,
alsa-devel <alsa-devel@lists.sourceforge.net>,
perex@suse.cz
Subject: Re: Re: [PATCH] emu10k1: minor send routing cleanup
Date: Mon, 22 Nov 2004 12:36:32 +0100 [thread overview]
Message-ID: <s5hk6sedsjj.wl@alsa2.suse.de> (raw)
In-Reply-To: <200411210121.25291.James@superbug.co.uk>
At Sun, 21 Nov 2004 01:21:25 +0000,
James@superbug.co.uk wrote:
>
> [1 <text/plain; iso-8859-1 (quoted-printable)>]
> Lee Revell wrote:
> > On Wed, 2004-11-17 at 14:38 +0100, Takashi Iwai wrote:
> >
> >>>Use snd_emu10k1_compose_audigy_fxrt* macro where appropriate. Also add
> >>>a few comments to explain send routing structure.
> >>>
> >>>Signed-Off-By: Lee Revell <rlrevell@joe-job.com>
> >>
> >>Thanks, applied to CVS.
> >>
> >
> >
> > Sorry, please revert this one. It disables the right channel. The
> > macro must not be correct.
> >
> > Lee
> >
>
> Use the attached patch to fix this problem.
Could you give the summary and signed-off-by lines, please?
thanks,
Takashi
> [2 emu10k1.h.diff <text/x-diff; iso-8859-1 (7bit)>]
> --- emu10k1.h.org 2004-11-21 01:04:06.875103895 +0000
> +++ emu10k1.h 2004-11-21 01:04:10.252609912 +0000
> @@ -840,10 +840,10 @@
> ((route[0] | (route[1] << 4) | (route[2] << 8) | (route[3] << 12)) << 16)
>
> #define snd_emu10k1_compose_audigy_fxrt1(route) \
> -(((unsigned int)route[0] | ((unsigned int)route[1] << 8) | ((unsigned int)route[2] << 16) | ((unsigned int)route[3] << 12)) << 24)
> +((unsigned int)route[0] | ((unsigned int)route[1] << 8) | ((unsigned int)route[2] << 16) | ((unsigned int)route[3] << 24))
>
> #define snd_emu10k1_compose_audigy_fxrt2(route) \
> -(((unsigned int)route[4] | ((unsigned int)route[5] << 8) | ((unsigned int)route[6] << 16) | ((unsigned int)route[7] << 12)) << 24)
> +((unsigned int)route[4] | ((unsigned int)route[5] << 8) | ((unsigned int)route[6] << 16) | ((unsigned int)route[7] << 24))
>
> typedef struct snd_emu10k1_memblk {
> snd_util_memblk_t mem;
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-11-22 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-21 1:21 Re: [PATCH] emu10k1: minor send routing cleanup James
2004-11-22 11:36 ` Takashi Iwai [this message]
2004-11-22 18:30 ` James Courtier-Dutton
2004-11-22 18:42 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2004-11-16 22:55 Lee Revell
2004-11-17 13:38 ` Takashi Iwai
2004-11-20 23:29 ` Lee Revell
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=s5hk6sedsjj.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=James@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
--cc=rlrevell@joe-job.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