Date: Fri, 18 May 2012 12:24:42 +0400 From: "Andrey V. Elsukov" <ae@FreeBSD.org> To: Eric McCorkle <eric@shadowsun.net> Cc: freebsd-hackers@freebsd.org Subject: Re: GSoC Project: EFI on amd64/i386 Message-ID: <4FB6074A.3000802@FreeBSD.org> In-Reply-To: <4FB4FCE2.7060509@shadowsun.net> References: <4FA95960.7090908@shadowsun.net> <BA85B7AA-FEA5-40B0-A15A-B4E000206C59@xcllnt.net> <4FB17B85.9080701@shadowsun.net> <201205151144.38123.jhb@freebsd.org> <4FB33BD9.3030501@FreeBSD.org> <4FB4FCE2.7060509@shadowsun.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FB6074A.3000802>