From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HFEtU-0000x6-QK
	for mharc-grub-devel@gnu.org; Thu, 08 Feb 2007 14:25:20 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HFEtS-0000vT-Se
	for grub-devel@gnu.org; Thu, 08 Feb 2007 14:25:18 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HFEtR-0000tb-QA
	for grub-devel@gnu.org; Thu, 08 Feb 2007 14:25:18 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HFEtR-0000tS-Gm
	for grub-devel@gnu.org; Thu, 08 Feb 2007 14:25:17 -0500
Received: from nf-out-0910.google.com ([64.233.182.188])
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1HFEtR-0000K9-31
	for grub-devel@gnu.org; Thu, 08 Feb 2007 14:25:17 -0500
Received: by nf-out-0910.google.com with SMTP id h2so935014nfe
	for <grub-devel@gnu.org>; Thu, 08 Feb 2007 11:25:16 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=LHAEeGPz2IphopQXT3Q5/pWwKIG+zS8WV5R2/xPzsGTz3vAgSAK36GAYOHIrFi2gj5vpaTWeqKh7DGBWvCkS4biiF6a0zo9IpRH9P0IUNAENmqrIV48shccch/7akbRVWMPm04+NdnmvjKRXQLzTbuoFCMDD/4pg5lPPalLE2MQ=
Received: by 10.82.152.16 with SMTP id z16mr2433743bud.1170962715865;
	Thu, 08 Feb 2007 11:25:15 -0800 (PST)
Received: by 10.82.160.20 with HTTP; Thu, 8 Feb 2007 11:25:15 -0800 (PST)
Message-ID: <ef4cc8c10702081125g72b0a681k347e1f2a2d33186a@mail.gmail.com>
Date: Thu, 8 Feb 2007 11:25:15 -0800
From: "Patrick Connolly" <pjc999@gmail.com>
To: grub-devel@gnu.org
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_33900_11385140.1170962715828"
X-detected-kernel: Linux 2.4-2.6 (Google crawlbot)
Subject: Adapting GRUB to boot directly from RAM in protected mode
X-BeenThere: grub-devel@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: The development of GRUB 2 <grub-devel@gnu.org>
List-Id: The development of GRUB 2 <grub-devel.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/grub-devel>,
	<mailto:grub-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/grub-devel>
List-Post: <mailto:grub-devel@gnu.org>
List-Help: <mailto:grub-devel-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/grub-devel>,
	<mailto:grub-devel-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Feb 2007 19:25:19 -0000

------=_Part_33900_11385140.1170962715828
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Can anyone think of a straightforward way to modify GRUB to boot a linux
kernel directly from RAM in protected mode?

We have an embedded system with a special BIOS that places a file (any file)
at a fixed location in RAM and executes it (in protected mode) starting at
that same fixed location.  We'd like the file to be a linux kernel (with
boot code) and we're wondering if GRUB could be adapted to do this.  We
realize that some assembly-level modifications would be needed but we aren't
sure how extensive those modifications might be expected to be.

Patrick

------=_Part_33900_11385140.1170962715828
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<p>Can anyone think of a straightforward way to modify GRUB to boot a linux kernel directly from RAM in protected mode?</p>
<p>We have an embedded system with a special BIOS that places a file (any file) at a fixed location in RAM and executes it (in protected mode) starting at that same fixed location.&nbsp; We&#39;d like the file to be a linux kernel (with boot code) and we&#39;re wondering if GRUB could be adapted to do this.&nbsp; We realize that some assembly-level modifications would be needed but we aren&#39;t sure how extensive those modifications might be expected to be.&nbsp; 
</p>
<p>Patrick&nbsp; </p>

------=_Part_33900_11385140.1170962715828--