RE: DSDT in initrd

On May 15, Brown, Len [off-list ref] wrote:

It makes me uneasy to append the DSDT to the initrd image.  This encumbers
the initrd booting scheme with ACPI BIOS workarounds.  What happens when
somebody changes how initrd works?

It's like everything in the kernel: If something changes and breaks
something else, the other things will be fixed as well, or the change will
be reverted. (or in the worst case, the other things will be removed).

If appending a DSDT image to initrd is okay, why not append other things
such as the ACPI black-list, for the same reasons?

The DSDT is one of the most dynamic things for ACPI hackers. If there is
the need to put other things into the initrd: no problem. The existing
patch should cooperate with bootsplash and should do so as well with other
'magic attachments'.

I think I'd be happier with the DSDT being _in_ the initrd as a named
file/module -- just like the other boot-time modules, rather than being
magically appended to the image.

I'll try to find out if it is possible in any way. I think that filesystem
drivers are not available at this stage of booting (why should they? they
are not needed and it would probably be a big and ugly hack to load them
in such an early stage.)

Of course this would require you to run mkinitrd for each platform;
unless multiple named tables were included in the initrd.

That's the least problem.

Markus
-- 
__________________    /"\
Markus Gaugusch       \ /    ASCII Ribbon Campaign
markus-z+rTbpWsRgbk7+2FdBfRIA@public.gmane.org     X     Against HTML Mail
                      / \


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com