From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1J3vyr-0003Kb-Bq for mharc-grub-devel@gnu.org; Sun, 16 Dec 2007 11:04:41 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J3vyo-0003KB-MM for grub-devel@gnu.org; Sun, 16 Dec 2007 11:04:38 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J3vyn-0003Jp-2Z for grub-devel@gnu.org; Sun, 16 Dec 2007 11:04:38 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J3vym-0003Jm-T1 for grub-devel@gnu.org; Sun, 16 Dec 2007 11:04:36 -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 1J3vym-0004eX-FH for grub-devel@gnu.org; Sun, 16 Dec 2007 11:04:36 -0500 Received: from [127.0.0.1] (88.193.32.97) by pne-smtpout3-sn1.fre.skanova.net (7.3.129) id 474FCCB0000CDBF6 for grub-devel@gnu.org; Sun, 16 Dec 2007 17:03:54 +0100 Message-ID: <47654D12.1040300@nic.fi> Date: Sun, 16 Dec 2007 18:06:42 +0200 From: =?ISO-8859-1?Q?Vesa_J=E4=E4skel=E4inen?= User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: The development of GRUB 2 References: <20071216153046.GA11912@thorin> In-Reply-To: <20071216153046.GA11912@thorin> 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: moving ata initialisation to a 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: Sun, 16 Dec 2007 16:04:39 -0000 Robert Millan wrote: > I'd like to move ata.mod initialisation away from its _init routine and into > a separate command. This way it isn't a nuissance when it gets included in > monolithic builds (such as the ones made by grub-mkrescue) and disables biosdisk > completely. > > Does that sound fine? > While you are there why not add optional IO-base argument so one could use more than one controller lurking in other IO-bases (second/third PCI ?). Of course there needs to be some kind of auto detect for easier usage for normal users.