Re: [LAD] exciting news about the realtime kernel tree

An interesting/important question though is how many of these 50+
modules actually contains hw specific adaptions. As an example, for
audio apps you typically rely on a number of sound ("snd-*") related
modules of which a fair amount is hardware independent. It is only the
modules that implement hardware specific adaptions that needs to go
through the "tedious" identification process.

I guess that the BIOS will leave most hardware components in a state
where they do not generate "interrupts" unless some kernel or userland
code explicitly turns this on. If this is true you should probably be
able to have a working system with a minimum set of modules. Anyone
that have some experience in creating a system with a minimum set of
hardware adaption modules? If so, what are the minimum set of hardware
adaption modules required?

/Lars

2009/2/27 Jens M Andreasen <jens.andreasen@email-addr-hidden>:
> Allrighty then, by hand is the way to go. With 50+ modules loaded on the
> running machine, that should take no more than a week to identify what
> they are, what they do (if anything?) and correct possible mistakes ...
>
> Or just leave it the way it is and do the laundry, take a nap, visit
> friends and watch some television :-D
>
> /j
>
>
> On Fri, 2009-02-27 at 08:32 +0100, MarcO'Chapeau wrote:
>> On Thu, 26 Feb 2009 18:46:32 +0100, Luis Garrido
>> <luisgarrido@email-addr-hidden> wrote:
>> >> Run 'make oldconfig'. That will stop when it encounters a new option
>> that
>> >
>> > Certainly, but that assumes that you have already done the job of
>> > pruning the kernel tree to the needs of your machine, so you don't
>> > have to build the whole behemoth.
>> >
>> > I think Jens was hinting at automating that step too, making use of
>> > the module detection facilities of a running stock kernel.
>>
>> I do not know about automating it, but doing it by hand is certainly good
>> for one's culture, and you only have to do it once since you can migrate
>> you .config file from one tree to a new one.
>>
>> I've been using the same config file for years. Eventually, I sometimes
>> have to take a look at new options/drivers to add (or remove).
>>
>> -- Marc-Olivier Barre --
>>  --- MarcO'Chapeau ----
>> - www.marcochapeau.org -
>> _______________________________________________
>> Linux-audio-dev mailing list
>> Linux-audio-dev@email-addr-hidden
>> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
>
> _______________________________________________
> Linux-audio-dev mailing list
> Linux-audio-dev@email-addr-hidden
> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
>
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Received on Fri Feb 27 16:15:02 2009