From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Lu1WC-0002rm-UG for mharc-grub-devel@gnu.org; Wed, 15 Apr 2009 05:34:56 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lu1WB-0002r9-4i for grub-devel@gnu.org; Wed, 15 Apr 2009 05:34:55 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lu1W6-0002qP-03 for grub-devel@gnu.org; Wed, 15 Apr 2009 05:34:54 -0400 Received: from [199.232.76.173] (port=43443 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lu1W5-0002qJ-Lh for grub-devel@gnu.org; Wed, 15 Apr 2009 05:34:49 -0400 Received: from fg-out-1718.google.com ([72.14.220.154]:25226) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Lu1W4-0004qK-Fv for grub-devel@gnu.org; Wed, 15 Apr 2009 05:34:49 -0400 Received: by fg-out-1718.google.com with SMTP id 19so847737fgg.7 for ; Wed, 15 Apr 2009 02:34:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=MPELVQAj5TlZ7azMpOEn4SMLtZQt2DXd+7DYl0yQKPY=; b=kfwMdBWdX9y3kCUwzEMD9J5/7IIGt+WYA7tUzAM3DcoEUcYd09MbzKQvmPiLunbKhY uo7kNCgTTMCCosCMBnejzRuPNJEJoQ18Nfm8UBccxuut8dfUo6UjLQGgVk7AEoOS9HaM ogNREOysxNx4/YIYFp8sc13SvdoHP/1/ugJoU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=la+OvIVmkdQWHwBxaJAF91dXYVYSy0ndMhmtRfjSPQgO33Ja4WfRiixTSRW61xQyk/ DzjioQ9dMvPbpzr5qQTNyDj2QjzzpSqDSqsfJrZz7+AOUBlmVjAmmiplm5oE5uvbFVjd Tw+B3MfLmfXYEDeDLY3pc7jlsfMmk4CI4S6vk= Received: by 10.86.66.16 with SMTP id o16mr17898fga.18.1239788087336; Wed, 15 Apr 2009 02:34:47 -0700 (PDT) Received: from ?192.168.1.100? (121.88.202.62.cust.bluewin.ch [62.202.88.121]) by mx.google.com with ESMTPS id e20sm10650838fga.14.2009.04.15.02.34.44 (version=SSLv3 cipher=RC4-MD5); Wed, 15 Apr 2009 02:34:46 -0700 (PDT) Message-ID: <49E5AA2F.1060305@gmail.com> Date: Wed, 15 Apr 2009 11:34:39 +0200 From: phcoder User-Agent: Thunderbird 2.0.0.21 (X11/20090409) MIME-Version: 1.0 To: The development of GRUB 2 References: <49E3E0FB.1070907@verizon.net> <1239694395.3718.5.camel@fz.local> <49E455B7.5040402@verizon.net> <49E4518D.1090301@gmail.com> <49E5A102.40701@verizon.net> <49E5A394.8050108@gmail.com> <49E5A91C.3000109@verizon.net> In-Reply-To: <49E5A91C.3000109@verizon.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: Re: status grub2 port of grub-legasy map command X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2009 09:34:55 -0000 Yes it is. Also it's better to use grub_mmap_iterate instead of basing the location on 0x413 value. How to do it look at mmap/i386/pc/mmap.c John Stanley wrote: > I'd be happy to sign a copywrite statement, no problem -- how do I go > about it ? > > Is this what you're referring to: > > /* BDA offset 0x13 contains the top of conventional memory, in > kiB. */ > grub_uint16_t *bpa_freekb = (grub_uint16_t*)0x00000413; > . > . > *bpa_freekb -= payload_sizekb; > > where payload_sizekb is the size of the drivemap int13 handler + its > mapped drive table ? > > > phcoder wrote: >> If you want your code to be incorporated you need to sign the >> copyright assignment. >> John Stanley wrote: >>> I have also incorporated your mmap services patch as well (again >>> with minor mods to build in r2106). My question at this point, is >>> how best to incorporate mmap services into drivemap. I see that in >>> mmap/i386/pc/mmap.c there is some sort of support for int12 and int15 >>> services. Should I incorporate the drivemap int13 handler here ? >>> Looks relatively straightforward -- just insert the asm handler into >>> mmap/i386/pc/mmap_helper.S and update mmap/i386/pc/mmap.c -- (except >>> for how I place the mapped drives table), or, should I use the mmap.c >>> code as a template for the drivemap int13 handler plus mapped drives >>> table ? >> Don't do it that way. It merges 2 unrelated modules. At some point >> drivermap does following >> *bpaMemInKb -= ...; >> But this isn't correct because mmap interrupts still list the memory >> used by drivemap as available. Use grub_mmap_register instead of it. >>> >>> thanks for any help/suggestions, >>> John >>> >>> phcoder wrote: >>>> I haven't yet looked in depth in drivemap patch but it has some >>>> problems. It uses preboot hook interface for which I proposed an >>>> update in my recent patch "preboot hooks". Also it doesn't update >>>> memorymap correctly. For this it should use my "mmap services" >>>> interface >>>> John Stanley wrote: >>>>> Thanks Felix, >>>>> >>>>> Hurm.. Well, if anyone is interested, I have just made a couple of >>>>> additional updates to the drivemap.path.8 code, >>>>> and now with r2104 the "unaligned pointer" issue is gone, and it is >>>>> working great on my systems. I can post the patch if you or anyone >>>>> else is interested. >>>>> John >>>>> >>>>> >>>>> Felix Zielcke wrote: >>>>>> Am Montag, den 13.04.2009, 21:03 -0400 schrieb John Stanley: >>>>>> >>>>>>> Hi all, >>>>>>> I was wondering what the current status of a grub2 port of the >>>>>>> grub-0.97 "map" and "rootnoverify" commands is? I have found >>>>>>> some work done to this end in the "drivemap.patch" work, but I >>>>>>> find nothing more recent than drivemap.patch.8 dated around Aug >>>>>>> 2008. >>>>>>> >>>>>> >>>>>> The current status of it are exactly what you found out. >>>>>> I don't know if that'll ever change. >>>>>> >>>>>> >>>>>> >>>>>>> Could anyone give me any pointers/direction on what might be >>>>>>> happening here? Could it be that the "norootverify"-functionality >>>>>>> of grub-legasy is lacking here? Or, perhaps, that the "--force" >>>>>>> option is not being honored ? >>>>>>> >>>>>> >>>>>> rootnoverify isn't needed anymore, because root is now just a >>>>>> variable >>>>>> and not anymore a command which tried to verify it. So basically >>>>>> rootnoverify is default now. >>>>>> chainloader --force just skips the check for 0xaa55, normally it >>>>>> shouldn't be needed with a valid windows bootsector. >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Grub-devel mailing list >>>>> Grub-devel@gnu.org >>>>> http://lists.gnu.org/mailman/listinfo/grub-devel >>>> >>>> >>> >>> >>> _______________________________________________ >>> Grub-devel mailing list >>> Grub-devel@gnu.org >>> http://lists.gnu.org/mailman/listinfo/grub-devel >> >> > > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/grub-devel -- Regards Vladimir 'phcoder' Serbinenko