From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Zoz Subject: Re: DSDT in initrd? Date: Tue, 6 May 2003 08:42:22 +0200 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <20030506064222.GV1817@suse.de> References: <20030504215051.GA488@elf.ucw.cz> <200305060007.49847.bob@diamond.demon.co.uk> 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 Tue, May 06, Markus Gaugusch wrote: > On May 6, Bob Lees wrote: > > Why use initrd? Why not allow a file name to be passed to the kernel at > > boot a la acpi=off, acpi=mydst.hex or whatever? Put the file in the > > /boot directory? > I think that this is not possible. The filesystem would have to be > accessible which is not the case at the early stage where ACPI loads > (there could even be the case, that no interrupts are assigned yet, to use > the scsi controller where the partition with the file is stored). Not to > mention, that harddisk and scsi drivers are loaded much later anyway. > The initrd is the only sane way to do this. I could also change my patch > to accept a plain DSDT file, without my 'magic' signature, if no other > initrd data is present. Grub should be able to handle the file access at this stage. -- 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