public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "M. Warner Losh" <imp-uzTCJ5RojNnQT0dZR+AlfA@public.gmane.org>
To: marks-h3GR0owD+wQ@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: Re: DSDT in initrd
Date: Fri, 23 May 2003 22:51:09 -0600 (MDT)	[thread overview]
Message-ID: <20030523.225109.32721389.imp@bsdimp.com> (raw)
In-Reply-To: <20030522080420.GA634-ScjxTogt4I4lGuH5DXb43w@public.gmane.org>

In message: <20030522080420.GA634-ScjxTogt4I4lGuH5DXb43w@public.gmane.org>
            Mark Santcroos <marks-h3GR0owD+wQ@public.gmane.org> writes:
: Linux people might want to look at how FreeBSD does this.
: However, as Andy states, this is not ACPI specific, it means an overhaul
: for the whole Linux booting process.

Basically, for those unfamiliar, FreeBSD has a three stage boot.
First stage know just enough to load the second stage.  Second stage
knows enough about file systems to load a third stage.  Third stage
can load kernels, modules and pass information to the kernels.  Very
handy for thoese sorts of situations.  While the first two stages very
from arch to arch, the third stage is basically the same on all
architectures (although there is a md component to is that handles
processor specific relocation goo, etc).

Loading DSDT tables in FreeBSD is just another thing that the loader
can load before transferring control to the kernel.

Warner


-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

  parent reply	other threads:[~2003-05-24  4:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22  7:48 Re: Re: DSDT in initrd Grover, Andrew
     [not found] ` <F760B14C9561B941B89469F59BA3A84725A2B3-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-05-22  8:04   ` Mark Santcroos
     [not found]     ` <20030522080420.GA634-ScjxTogt4I4lGuH5DXb43w@public.gmane.org>
2003-05-24  4:51       ` M. Warner Losh [this message]
2003-05-22 11:40   ` Alan Cox
     [not found]     ` <1053603651.2541.10.camel-2MMpYkNvuYAXoXS6vNje7nviChZXdy279dF7HbQ/qKg@public.gmane.org>
2003-05-22 13:31       ` Ducrot Bruno
     [not found]         ` <20030522133132.GJ346-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-05-22 16:07           ` Russell Coker
2003-05-24  7:32   ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2003-05-28 18:31 Grover, Andrew
     [not found] ` <F760B14C9561B941B89469F59BA3A847E96EE6-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-05-28 19:01   ` Pavel Machek
2003-05-28 20:27 Grover, Andrew
     [not found] ` <F760B14C9561B941B89469F59BA3A84725A2C3-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-05-28 20:36   ` Pavel Machek
2003-05-28 21:46   ` Matthew Wilcox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030523.225109.32721389.imp@bsdimp.com \
    --to=imp-uztcj5rojnnqt0dzr+alfa@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=marks-h3GR0owD+wQ@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox