From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Zoz Subject: Re: DSDT in initrd? Date: Tue, 6 May 2003 06:05:32 +0200 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <20030506040532.GS1817@suse.de> References: <20030504215051.GA488@elf.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org On Mon, May 05, Markus Gaugusch wrote: > > > Has anybody thought about putting the dsdt into the initial ramdisk? > > > This would make changing/updating it much easier. > > I guess initrd is too late to override it... > If I would mount it, probably yes. But I rather thought about the way that > bootsplash uses: Scan the initrd for a magic signature and read it 'raw'. > The dsdt would not be in the filesystem of the initrd, but just appended > to the compressed initrd. I think that something that is early enough for > bootsplash should be early enough for the dsdt as well. And this would make patching dsdt much easier for the unexperienced user. Just download a file and call 'mkinitrd'. If bootsplash is early enough, then lets do that. -- ciao, christian -------------------------------------------------------------------- Verglichen mit jedem x-beliebigen Redmonder Betriebssystem-Clone ist Linux geradezu eine leuchtende Perle der Datensicherheit. ------ Frank Rennemann (http://www.linux-knowledge-portal.org) ----- ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf