On Fri, Mar 27, 2015 at 02:19:44PM +, Jan Beulich wrote:
> >>> On 27.03.15 at 15:09, wrote:
> > On Fri, Mar 27, 2015 at 02:04:22PM +, Jan Beulich wrote:
> >> >>> On 27.03.15 at 14:53, wrote:
> >> > On 27/03/15 13:43, Jan Beulich wrote:
> >> > On 27.03.15 at 14:32, wrote:
> >> >>> On
>>> On 27.03.15 at 15:09, wrote:
> On Fri, Mar 27, 2015 at 02:04:22PM +, Jan Beulich wrote:
>> >>> On 27.03.15 at 14:53, wrote:
>> > On 27/03/15 13:43, Jan Beulich wrote:
>> > On 27.03.15 at 14:32, wrote:
>> >>> On Fri, Feb 20, 2015 at 04:17:35PM +, Jan Beulich wrote:
>> >>> On 3
On Fri, Mar 27, 2015 at 02:04:22PM +, Jan Beulich wrote:
> >>> On 27.03.15 at 14:53, wrote:
> > On 27/03/15 13:43, Jan Beulich wrote:
> > On 27.03.15 at 14:32, wrote:
> >>> On Fri, Feb 20, 2015 at 04:17:35PM +, Jan Beulich wrote:
> >>> On 30.01.15 at 18:54, wrote:
> > We need
>>> On 27.03.15 at 14:53, wrote:
> On 27/03/15 13:43, Jan Beulich wrote:
> On 27.03.15 at 14:32, wrote:
>>> On Fri, Feb 20, 2015 at 04:17:35PM +, Jan Beulich wrote:
>>> On 30.01.15 at 18:54, wrote:
> We need more fine grained knowledge about EFI environment and check
> for EF
On 27/03/15 13:43, Jan Beulich wrote:
On 27.03.15 at 14:32, wrote:
On Fri, Feb 20, 2015 at 04:17:35PM +, Jan Beulich wrote:
On 30.01.15 at 18:54, wrote:
We need more fine grained knowledge about EFI environment and check
for EFI platform and EFI loader separately to properly support
mult
>>> On 27.03.15 at 14:32, wrote:
> On Fri, Feb 20, 2015 at 04:17:35PM +, Jan Beulich wrote:
>> >>> On 30.01.15 at 18:54, wrote:
>> > We need more fine grained knowledge about EFI environment and check
>> > for EFI platform and EFI loader separately to properly support
>> > multiboot2 protocol
On Fri, Feb 20, 2015 at 04:17:35PM +, Jan Beulich wrote:
> >>> On 30.01.15 at 18:54, wrote:
> > We need more fine grained knowledge about EFI environment and check
> > for EFI platform and EFI loader separately to properly support
> > multiboot2 protocol.
>
> ... because of ... (i.e. I can't s
>>> On 03.03.15 at 00:40, wrote:
> Reviewing the #ifndef CONFIG_ARM in EFI code, and the efi_enabled
> usage elsewhere,
> the remaining EFI tasks on ARM look like:
> * Support for SetVirtualAddressMap
> * Runtime service support - looks like just time function used by x86
> in get_cmos_time()
* P
On Mon, Mar 2, 2015 at 10:43 AM, Roy Franz wrote:
> On Mon, Mar 2, 2015 at 9:21 AM, Stefano Stabellini
> wrote:
>> On Fri, 30 Jan 2015, Daniel Kiper wrote:
>>> We need more fine grained knowledge about EFI environment and check
>>> for EFI platform and EFI loader separately to properly support
>>
On Mon, Mar 2, 2015 at 9:21 AM, Stefano Stabellini
wrote:
> On Fri, 30 Jan 2015, Daniel Kiper wrote:
>> We need more fine grained knowledge about EFI environment and check
>> for EFI platform and EFI loader separately to properly support
>> multiboot2 protocol. In general Xen loaded by this protoc
On Fri, 30 Jan 2015, Daniel Kiper wrote:
> We need more fine grained knowledge about EFI environment and check
> for EFI platform and EFI loader separately to properly support
> multiboot2 protocol. In general Xen loaded by this protocol uses
> memory mappings and loaded modules in simliar way to X
>>> On 30.01.15 at 18:54, wrote:
> We need more fine grained knowledge about EFI environment and check
> for EFI platform and EFI loader separately to properly support
> multiboot2 protocol.
... because of ... (i.e. I can't see from the description what the
separation is good for). Looking at the
We need more fine grained knowledge about EFI environment and check
for EFI platform and EFI loader separately to properly support
multiboot2 protocol. In general Xen loaded by this protocol uses
memory mappings and loaded modules in simliar way to Xen loaded
by multiboot (v1) protocol. Hence, spli
13 matches
Mail list logo
