Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932083AbVLTUgA (ORCPT ); Tue, 20 Dec 2005 15:36:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932084AbVLTUf7 (ORCPT ); Tue, 20 Dec 2005 15:35:59 -0500 Received: from anchor-post-35.mail.demon.net ([194.217.242.85]:20486 "EHLO anchor-post-35.mail.demon.net") by vger.kernel.org with ESMTP id S932083AbVLTUf7 (ORCPT ); Tue, 20 Dec 2005 15:35:59 -0500 Message-ID: <43A86B20.1090104@superbug.co.uk> Date: Tue, 20 Dec 2005 20:35:44 +0000 From: James Courtier-Dutton User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051218) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Linus Torvalds CC: Adrian Bunk , Sergey Vlasov , Ricardo Cerqueira , mchehab@brturbo.com.br, Linux Kernel Mailing List , video4linux-list@redhat.com, perex@suse.cz, alsa-devel@alsa-project.org Subject: Re: [Alsa-devel] 2.6.15-rc6: boot failure in saa7134-alsa.c References: <20051220131810.GB6789@stusta.de> <20051220155216.GA19797@master.mivlgu.local> <20051220191412.GA4578@stusta.de> In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1594 Lines: 46 Linus Torvalds wrote: > > On Tue, 20 Dec 2005, Adrian Bunk wrote: > >>>Adrian, does it work if you change the "module_init()" in >>>sound/sound_core.c into a "fs_initcall()"? >> >>No, this didn't work. >> >>What did work was to leave sound/sound_core.c alone > > > Can you do try the other way again, with sound/core/sound.c fixed too? > > A regular driver really _should_ use the regular "module_init()" sequence > (it is indeed just a compatibility define for "driver_init()"). > > The "late_init()" stuff is meant for stuff that literally runs after > everything else is up and running, it might want all drivers functional > (now, nobody really cares about a sound driver, so in that sense it would > be ok..) > > Thanks, > > Linus > This is an interesting problem actually. alsa consists of a number of different modules. They all load in the correct order if they are modules. The problem comes when one compiles them into the kernel. They then load in the wrong order and bad things happen, resulting in the recommendation that alsa should always be modules. In this basis, we should not have to change the code in alsa at all, but instead change the kernel to understand the load order, even if compiled into the kernel and not as modules. I have no idea how to get the kernel to do this though. Any pointers? James - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/