From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262346AbVHAI6k (ORCPT ); Mon, 1 Aug 2005 04:58:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262424AbVHAI6k (ORCPT ); Mon, 1 Aug 2005 04:58:40 -0400 Received: from cantor.suse.de ([195.135.220.2]:13480 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S262421AbVHAI6D (ORCPT ); Mon, 1 Aug 2005 04:58:03 -0400 Date: Mon, 01 Aug 2005 10:58:02 +0200 Message-ID: From: Takashi Iwai To: Daniel Egger Cc: Jaroslav Kysela , Andrew Morton , Mailing List Kernel linux-kernel Subject: Re: [ALSA PATCH] 1.0.9b+ In-Reply-To: <3442015A-4821-45DA-ACD4-16AAD9DC3268@axiros.com> References: <20050728102525.234e6511.akpm@osdl.org> <3442015A-4821-45DA-ACD4-16AAD9DC3268@axiros.com> User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 MULE XEmacs/21.5 (beta18) (chestnut) (+CVS-20041021) (i386-suse-linux) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org At Sat, 30 Jul 2005 15:42:33 +0200, Daniel Egger wrote: > > On 29.07.2005, at 09:39, Jaroslav Kysela wrote: > > > Note that most of lines are from new Sparc and ARM drivers. Other > > changes > > are mostly small bugfixes, cleanups and new hardware ID additions. > > The all > > changes goes through all ALSA developers (our CVS server sends us > > whole > > diffs back), so all of them review/verify new code and can fix it > > ASAP. It > > works quite well. > > FWIW the current ALSA patch against 2.6.12 works much better than > the original version for my Asus W3V with Intel HDA ALC880 in the sense > that there's a possibility to prevent crashing the kernel when loading > the module. However apart from the ID fixes this involves disabling the > autodetection code and hardcoding the correct type in the realtek code. > > As it stands the code seems to be really buggy and I'd love to test the > driver after someone wiser than me in this area reviewed and fixed the > code. The oops was fixed by this update... Takashi