From: Takashi Iwai Subject: Re: question about bluez using alsa and patches Date: Tue, 19 Jun 2007 12:45:23 +0200 Message-ID: References: <200706141945.25383.wshekrota@optonline.net> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.suse.de (ns1.suse.de [195.135.220.2]) by alsa0.perex.cz (Postfix) with ESMTP id 1DDCA2438F for ; Tue, 19 Jun 2007 12:45:24 +0200 (CEST) In-Reply-To: <200706141945.25383.wshekrota@optonline.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Walt Shekrota Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org At Thu, 14 Jun 2007 19:45:25 -0400, Walt Shekrota wrote: > > I was told that when using the btsco(bluez) and/or plugs bluetooth headset > software a patch is always required. > In the Gentoo community and perhaps everywhere it is suggested to use alsa > compiled into your kernel. > As I go to new kernels frequently these folks (sco headset) seem to have no > such forward support ie they have not worked on the patches yet for the newer > kernels. > Am I wrong or at some point in time should this app not be weaned from using > patches? Is it the fact they use sco that they have to patch? Is there not an > alsa library they can program to instead. > I guess I don't understand the overall design so I can't see why this goes on > forever. > I'm somewhat apprehensive about trusting others to continually modify my > kernel. > > Am I out in left field here? Can anyone explain why they must choose this > path? Because no one posted a patch to merge to the upstream... Takashi