From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Luy9U-0002QK-5c for mharc-grub-devel@gnu.org; Fri, 17 Apr 2009 20:11:24 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Luy9S-0002Pj-4M for grub-devel@gnu.org; Fri, 17 Apr 2009 20:11:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Luy9N-0002PL-Fb for grub-devel@gnu.org; Fri, 17 Apr 2009 20:11:21 -0400 Received: from [199.232.76.173] (port=36373 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Luy9N-0002PI-Cb for grub-devel@gnu.org; Fri, 17 Apr 2009 20:11:17 -0400 Received: from smtp103.vzn.mail.re1.yahoo.com ([69.147.103.190]:41263) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1Luy9N-0004Uw-4A for grub-devel@gnu.org; Fri, 17 Apr 2009 20:11:17 -0400 Received: (qmail 83828 invoked from network); 18 Apr 2009 00:01:39 -0000 Received: from unknown (HELO ?192.168.2.5?) (jpsinthemix@151.200.143.223 with plain) by smtp103.vzn.mail.re1.yahoo.com with SMTP; 18 Apr 2009 00:01:39 -0000 X-Yahoo-Newman-Property: ymail-3 Message-ID: <49E91862.9090103@verizon.net> Date: Fri, 17 Apr 2009 20:01:38 -0400 From: John Stanley User-Agent: Thunderbird 2.0.0.21 (X11/20090302) 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> <49E5AA2F.1060305@gmail.com> <1240003243.6449.7.camel@localhost> <49E90CCD.90207@verizon.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-detected-operating-system: by monty-python.gnu.org: FreeBSD 6.x (1) 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: Sat, 18 Apr 2009 00:11:22 -0000 Ok, that sounds good... I feel better about it then. I didn't mean directly modifying bios data, but through doc'd bios ints of course. It been a long, long time since I've looked at (or dealt with) bios code, so I was was simply wondering if boot device naming could be modified in a documented way nowadays-- after all, the functionality has been available in the bios setup in pcs for at least 10 years or so. Vladimir Serbinenko wrote: > > > On Sat, Apr 18, 2009 at 1:12 AM, John Stanley > wrote: > > Hi Javier and all, > I could probably have a version of the drivemap completed this > weekend as well, but since I've basically simply adapted your > drivempa.patch.8 to r2106, with little change, I'd be more > comfortable going with your new patch since you know the code much > better. > > In addition, in the last several days, have started leaning away > from it altogether -- because of the use of an int13 intercept > TSR. When I started looking at the drivemap patch about a week > ago, I assumed it simply did some sort of bios (internal) table > swapping only. I'm not really comfort able with the int13 handler > redirect. I worry about (possibly rare) problems downstream while > running Windows. On the other hand, I know it "does work," as I > and many others have been using map with grub-legasy for several > years now. Nevertheless, I'm now a bit apprehensive. > > Modifying internal bios tables isn't practicable because they may be > anywhere and in any format. Windows follows the memory map supplied by > int12/int15/bda which says that the ranges used by hook are unusable. > Also even if windows overwrites int13 handle it doesn't matter at all > because windows switches to its own disk drivers after initial start > > > For me, for the time-being, as my laptops are all Thinkpads, which > have bios supplied "boot device table" functionality (via f12 on > poweron), I can live without drivemap for those occasions when I > need to come down from the hilltop to work on Windows. > > What I'd like to do with drivemap, is to do boot device swapping > by changing in the bios which device is to be treated as the > "first" boot device, which is the second, etc. I know this is > doable in principle, but it may not be practical, or wise-- I'm > not sure. > > There is no public API to do so. So you need to reverse engineer BIOS > which is impractical to do for every possible mobo. > > It would also have to be done in a way which does not "pull the > rug out on grub" insofar as boot device enumeration is concerned. > > > Javier Martín wrote: > > Hello there. I am the original author of the drivemap command. > I was > told by a friend that it was being discussed again on the GRUB > list, so > I came back and examined the two new enabling functionalities, > preboot > hooks and mmap. I've adapted drivemap to use them both, and I'm > polishing some rough edges. I might send a new version of the > patch this > weekend. Should people, however, prefer John's version, I'd be > glad to > assist. > > El mié, 15-04-2009 a las 11:34 +0200, phcoder escribió: > > > 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 > > > The preboot hooks patch works beautifully. However, mmap > causes some > sort of glitch that makes FreeDOS (one of my three drivemap tests, > together with ReactOS and XP) triple-fault. I've been trying > to debug it > with GDB-over-QEMU, but it is a real PITA. I haven't found any > sort of > bug in the mmap code, so I'm quite dumbfounded right now. > Nevertheless, > I'm proceeding to the XP test, which would likely be the most > common use > case for drivemap. > > ------------------------------------------------------------------------ > > > > _______________________________________________ > 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 >