On Mon, Jun 5, 2017 at 9:03 AM, Ard Biesheuvel
wrote:
> On 5 June 2017 at 15:40, Ingo Molnar wrote:
>>
>> * Ard Biesheuvel wrote:
>>
>>> From: Andy Lutomirski
>>>
>>> efi_call_phys_prolog() used to return a "pgd_t *" that meant one of
>>> three different things depending on kernel and system co
* Ard Biesheuvel wrote:
> >> +config EFI_CAPSULE_QUIRK_QUARK_CSH
> >> + boolean "Add support for Quark capsules with non-standard headers"
> >> + depends on X86 && !64BIT
> >> + select EFI_CAPSULE_LOADER
> >> + default y
> >> + help
> >> + Add support for processing Qua
On 5 June 2017 at 15:40, Ingo Molnar wrote:
>
> * Ard Biesheuvel wrote:
>
>> From: Andy Lutomirski
>>
>> efi_call_phys_prolog() used to return a "pgd_t *" that meant one of
>> three different things depending on kernel and system configuration.
>> Clean it up so it uses a union and is more expli
On 5 June 2017 at 15:50, Ingo Molnar wrote:
>
> * Ard Biesheuvel wrote:
>
>> From: Jan Kiszka
>>
>> The firmware for Quark X102x prepends a security header to the capsule
>> which is needed to support the mandatory secure boot on this processor.
>> The header can be detected by checking for the
* Ard Biesheuvel wrote:
> > It would be nice to fix your SOB flow: the maintainer who queues up a patch
> > should
> > add the SOB, and add an Acked-by of the co-maintainer if the co-maintainer
> > agrees
> > with the patch as well. The tree should typically not be rebased after that
> > poin
* Ard Biesheuvel wrote:
> From: Jan Kiszka
>
> The firmware for Quark X102x prepends a security header to the capsule
> which is needed to support the mandatory secure boot on this processor.
> The header can be detected by checking for the "_CSH" signature and -
> to avoid any GUID conflict -
* Ard Biesheuvel wrote:
> From: Andy Lutomirski
>
> efi_call_phys_prolog() used to return a "pgd_t *" that meant one of
> three different things depending on kernel and system configuration.
> Clean it up so it uses a union and is more explicit about what's
> going on.
>
> Signed-off-by: Andy
On 5 June 2017 at 09:07, Ingo Molnar wrote:
>
> * Ard Biesheuvel wrote:
>
>> (trim cc)
>>
>> On 2 June 2017 at 13:51, Ard Biesheuvel wrote:
>> > The following changes since commit
>> > 5ed02dbb497422bf225783f46e6eadd237d23d6b:
>> >
>> > Linux 4.12-rc3 (2017-05-28 17:20:53 -0700)
>> >
>> > are
On Mon, Jun 05, 2017 at 08:04:35AM +, Ard Biesheuvel wrote:
> On ARM, regions of memory that are described by UEFI as having special
> significance to the firmware itself are omitted from the linear mapping.
> This is necessary since we cannot guarantee that alternate mappings of
> the same phy
* Ard Biesheuvel wrote:
> (trim cc)
>
> On 2 June 2017 at 13:51, Ard Biesheuvel wrote:
> > The following changes since commit 5ed02dbb497422bf225783f46e6eadd237d23d6b:
> >
> > Linux 4.12-rc3 (2017-05-28 17:20:53 -0700)
> >
> > are available in the git repository at:
> >
> > git://git.kerne
(trim cc)
On 2 June 2017 at 13:51, Ard Biesheuvel wrote:
> The following changes since commit 5ed02dbb497422bf225783f46e6eadd237d23d6b:
>
> Linux 4.12-rc3 (2017-05-28 17:20:53 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags
On ARM, regions of memory that are described by UEFI as having special
significance to the firmware itself are omitted from the linear mapping.
This is necessary since we cannot guarantee that alternate mappings of
the same physical region will use attributes that are compatible with
the ones we us
12 matches
Mail list logo
