[lkml]   [2005]   [Dec]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Alsa-devel] 2.6.15-rc6: boot failure in saa7134-alsa.c
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?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-12-20 21:38    [W:0.104 / U:0.068 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site