From mboxrd@z Thu Jan 1 00:00:00 1970 From: presotto@plan9.bell-labs.com To: 9fans@cse.psu.edu Subject: Re: [9fans] change to bitsy/devsac.c to use the new bootldr MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-pcwsxgpijnyctvsiaphcxfxima" Message-Id: <20010617153749.7C807199F6@mail.cse.psu.edu> Date: Sun, 17 Jun 2001 11:37:47 -0400 Topicbox-Message-UUID: bbb36aa4-eac9-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-pcwsxgpijnyctvsiaphcxfxima Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit I already did this. We look in both spots. I needed to do that to make william work. He's using the latest and greatest bootldr. --upas-pcwsxgpijnyctvsiaphcxfxima Content-Type: message/rfc822 Content-Disposition: inline Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Fri Jun 15 07:35:08 EDT 2001 Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Fri Jun 15 07:35:06 EDT 2001 Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.30.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id A93DE199F3; Fri, 15 Jun 2001 03:33:12 -0400 (EDT) Received: from nautilus.dat.escet.urjc.es (nautilus.dat.escet.urjc.es [212.128.1.37]) by mail.cse.psu.edu (CSE Mail Server) with SMTP id 09C19199E9 for <9fans@cse.psu.edu>; Fri, 15 Jun 2001 03:32:16 -0400 (EDT) To: 9fans@cse.psu.edu From: F.J.Ballesteros MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Message-Id: <20010615073217.09C19199E9@mail.cse.psu.edu> Subject: [9fans] change to bitsy/devsac.c to use the new bootldr Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.1 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Fri, 15 Jun 2001 09:28:11 +0200 Hi, To load and use a ramdisk on the bitsy with the new boot loaders you need to change devsac.c: where it said p = (uchar*)Flash_tar+4; it should say now p = (uchar*)Flash_tar; This seems to be due to a change in the bootldr that now has a partition table. So the tar file created in ramdisk now gets placed exactly at 0x100000, not at 0x100004. Beware that this change can make devsac.c fail with previous verions of the bootldr, but you are likely to upgrade it anyway... BTW, you also need to create a ramdisk partition in the bootldr. I'll post in a minute an updated howto file (i.e. Booting101) for the new bootldr. --upas-pcwsxgpijnyctvsiaphcxfxima--