From owner-freebsd-hackers@FreeBSD.ORG Fri May 18 08:33:56 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79636106564A for ; Fri, 18 May 2012 08:33:56 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from mail-new.kirov.so-ups.ru (mail-new.kirov.so-ups.ru [178.74.170.12]) by mx1.freebsd.org (Postfix) with ESMTP id 2206F8FC12 for ; Fri, 18 May 2012 08:33:56 +0000 (UTC) Received: from kirov.so-ups.ru (unknown [172.21.81.1]) by mail-new.kirov.so-ups.ru (Postfix) with ESMTP id 38669A1E27; Fri, 18 May 2012 12:25:00 +0400 (MSK) Received: by ns.kirov.so-ups.ru (Postfix, from userid 1010) id 86807B9FC0; Fri, 18 May 2012 12:24:42 +0400 (MSK) Received: from [127.0.0.1] (unknown [10.118.3.52]) by ns.kirov.so-ups.ru (Postfix) with ESMTP id 50EBAB9FB0; Fri, 18 May 2012 12:24:42 +0400 (MSK) Message-ID: <4FB6074A.3000802@FreeBSD.org> Date: Fri, 18 May 2012 12:24:42 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: Eric McCorkle References: <4FA95960.7090908@shadowsun.net> <4FB17B85.9080701@shadowsun.net> <201205151144.38123.jhb@freebsd.org> <4FB33BD9.3030501@FreeBSD.org> <4FB4FCE2.7060509@shadowsun.net> In-Reply-To: <4FB4FCE2.7060509@shadowsun.net> X-Enigmail-Version: 1.4.1 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: GSoC Project: EFI on amd64/i386 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2012 08:33:56 -0000 On 17.05.2012 17:28, Eric McCorkle wrote: >> As i see we already have sys/boot/efi/libefi/efipart.c that uses >> EFI BLOCK_IO_PROTOCOL to make "part" devsw. EFI BLOCK_IO_PROTOCOL >> provides access to each disk and partition. AFAIK it supports only >> GPT and MBR+EBR, so there might be some problems with ZFS support, >> because we can use ZFS atop of BSD partition. > > > I'd need to take a look, but if the efi loaders are not directly > calling the EFI_BLOCK_IO_PROTOCOL functions, then it should be easy to > implement a layer that understands BSDlabels. IA64 might have a solution. > > Then again, is a BSDlabel really necessary on a GPT disk? It might be necessary for the ZFS case. ZFS can use several devices/partitions and they should be accessible while booting. -- WBR, Andrey V. Elsukov