From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org-S262262AbUKVSXq@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S262262AbUKVSXq (ORCPT <rfc822;willy@w.ods.org>);
	Mon, 22 Nov 2004 13:23:46 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262270AbUKVSWI
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Mon, 22 Nov 2004 13:22:08 -0500
Received: from mail-ex.suse.de ([195.135.220.2]:49549 "EHLO Cantor.suse.de")
	by vger.kernel.org with ESMTP id S262287AbUKVSTF (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 22 Nov 2004 13:19:05 -0500
Date: Mon, 22 Nov 2004 19:19:05 +0100
Message-ID: <s5hllctvjae.wl@alsa2.suse.de>
From: Takashi Iwai <tiwai@suse.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Adrian Bunk <bunk@stusta.de>, perex@suse.cz, alsa-devel@alsa-project.org,
       linux-kernel@vger.kernel.org,
       James Courtier-Dutton <James@superbug.co.uk>
Subject: Re: [Alsa-devel] Re: [2.6 patch] ALSA PCI drivers: misc cleanups
In-Reply-To: <1101147241.2873.23.camel@krustophenia.net>
References: <20041121235855.GI13254@stusta.de>
	<1101088632.5119.2.camel@krustophenia.net>
	<s5hsm71vlrc.wl@alsa2.suse.de>
	<1101145386.2873.2.camel@krustophenia.net>
	<s5hoehpvkdl.wl@alsa2.suse.de>
	<1101147241.2873.23.camel@krustophenia.net>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 15) (Security Through Obscurity) (i386-suse-linux)
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

At Mon, 22 Nov 2004 13:14:01 -0500,
Lee Revell wrote:
> 
> On Mon, 2004-11-22 at 18:55 +0100, Takashi Iwai wrote:
> > > Nope.  Any idea what this is/was for?  I poked around the OSS driver and
> > > could not find a similar function.
> > 
> > IIRC, it came from the very old version of OSS emu10k1 driver.
> > 
> 
> OK.  If this code was in the original opensource.creative.com driver
> then there is always the chance it embodies some knowledge of the
> hardware that we don't have.  For example set_loop_stop, which was also
> in the OSS driver but unused, can be used to start multiple channels in
> sync.  But as long as the CVS history is available this should not be a
> problem.

Yep.  The code is just to calculate X * ln2(Y) (or something like
that), so anyway it's not important for the hardware control.


Takashi