From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Iqvve-0005Xg-V8 for mharc-grub-devel@gnu.org; Sat, 10 Nov 2007 14:23:38 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Iqvvd-0005XP-LL for grub-devel@gnu.org; Sat, 10 Nov 2007 14:23:37 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Iqvvb-0005Wd-J1 for grub-devel@gnu.org; Sat, 10 Nov 2007 14:23:36 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Iqvvb-0005Wa-Et for grub-devel@gnu.org; Sat, 10 Nov 2007 14:23:35 -0500 Received: from pne-smtpout3-sn1.fre.skanova.net ([81.228.11.120]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Iqvvb-0004pY-6a for grub-devel@gnu.org; Sat, 10 Nov 2007 14:23:35 -0500 Received: from [127.0.0.1] (88.193.32.97) by pne-smtpout3-sn1.fre.skanova.net (7.3.129) id 4717E5DD00138B48 for grub-devel@gnu.org; Sat, 10 Nov 2007 20:23:16 +0100 Message-ID: <473604C2.6020307@nic.fi> Date: Sat, 10 Nov 2007 21:21:38 +0200 From: =?ISO-8859-1?Q?Vesa_J=E4=E4skel=E4inen?= User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: The development of GRUB 2 References: <87d4uic70x.fsf@xs4all.nl> In-Reply-To: <87d4uic70x.fsf@xs4all.nl> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-detected-kernel: by monty-python.gnu.org: Solaris 10 (beta) Subject: Re: Status of ATA support 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, 10 Nov 2007 19:23:38 -0000 Marco Gerards wrote: > First of all, this is mainly for i386-linuxbios. On i386-pc we have > to disable biosdisk support because ata.mod and biosdisk.mod do not > like eachother :-). Perhaps disk access via the BIOS will not be > possible/safe anymore after loading ata.mod. We have to make sure we are not using BIOS for accessing disk after that point. And ATA controller should be at stable state after resuming normal operations OR we install custom int13h handler. Actually you could try to determine what devices are handled by biosdisk and what are not. EDD supports some queries that report on what controller disk comes from.