Re: DSDT in initrd?

[Alexander Hoogerhuis <alexh-rpjHciJLgqZBDgjK7y7TUQ@public.gmane.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Markus Gaugusch <markus-z+rTbpWsRgbk7+2FdBfRIA@public.gmane.org> writes:

> On May 6, Bob Lees <bob-l+PWtdWbHAsG2Il/BtU0GPXRex20P6io@public.gmane.org> 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.
> 

Or make the acpi=file.hex boot argument refer to a file within the
initrd image. Then its just a case of getting mkinitrd patched to look
for /boot/dsdt.hex by default, and letting the user specificy an
alternate DSDT by parameter and generating initrd's would be a simple.

mvh,
A
- -- 
Alexander Hoogerhuis                               | alexh-rpjHciJLgqZBDgjK7y7TUQ@public.gmane.org
CCNP - CCDP - MCNE - CCSE                          | +47 908 21 485
"You have zero privacy anyway. Get over it."  --Scott McNealy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQE+t20FCQ1pa+gRoggRAqGvAKCZ1Vj+UcYKaRc/mvjwPkO7SKNqgACfSc7H
O0FXhxPs9k0paJ0i2jUSZgA=
=c/nm
-----END PGP SIGNATURE-----


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf