> ; l...@nuviainc.com
> Subject: Re: [PATCH v2 1/1] efi_loader: architecture specific UEFI setup
>
> On Thu, Feb 13, 2020 at 2:11 PM Ard Biesheuvel
> wrote:
> >
> > On Thu, 13 Feb 2020 at 19:59, Atish Patra wrote:
> > >
> > > On Tue, Feb 11, 2020 at 11:28 PM A
t;; Atish Patra ;
> l...@nuviainc.com
> Subject: Re: [PATCH v2 1/1] efi_loader: architecture specific UEFI setup
>
> On Fri, 14 Feb 2020 at 13:04, Chang, Abner (HPS SW/FW Technologist)
> wrote:
> >
> >
> >
> > > -Original Message-
> > > Fr
viainc.com
> Subject: Re: [PATCH v2 1/1] efi_loader: architecture specific UEFI setup
>
>
>
> > Am 14.02.2020 um 05:21 schrieb Chang, Abner (HPS SW/FW Technologist)
> :
> >
> >
> >
> >> -Original Message-
> >> From: Atish Patra [m
t;; Atish Patra ;
> l...@nuviainc.com
> Subject: Re: [PATCH v2 1/1] efi_loader: architecture specific UEFI setup
>
> On Fri, 14 Feb 2020 at 12:27, Chang, Abner (HPS SW/FW Technologist)
> wrote:
> >
> >
> >
> > > -Original Message-
> > > Fr
)
> > Cc: Alexander Graf ; Atish Patra ;
> > Heinrich Schuchardt ; U-Boot Mailing List > b...@lists.denx.de>; Atish Patra ;
> > l...@nuviainc.com
> > Subject: Re: [PATCH v2 1/1] efi_loader: architecture specific UEFI setup
> >
> > On
; > Cc: Atish Patra ; Ard Biesheuvel
> > ; Heinrich Schuchardt ;
> > U-Boot Mailing List ; Atish Patra
> > ; l...@nuviainc.com
> > Subject: Re: [PATCH v2 1/1] efi_loader: architecture specific UEFI setup
> >
> >
> >
> > > Am 14.02.2020 um 05:21 schrieb
Abner (HPS SW/FW Technologist) ;
>> Heinrich Schuchardt ; Alexander Graf
>> ; U-Boot Mailing List ; Atish Patra
>> ; l...@nuviainc.com
>> Subject: Re: [PATCH v2 1/1] efi_loader: architecture specific UEFI setup
>>
>>> On Thu, Feb 13, 2020 at 2:11 PM
t; > To: Chang, Abner (HPS SW/FW Technologist) ;
> > > > > Atish Patra ; Ard Biesheuvel
> > > > >
> > > > > Cc: Alexander Graf ; U-Boot Mailing List > > > > b...@lists.denx.de>; Atish Patra
gt; > > Cc: Alexander Graf ; U-Boot Mailing List > > > b...@lists.denx.de>; Atish Patra ;
> > > > l...@nuviainc.com
> > > > Subject: Re: [PATCH v2 1/1] efi_loader: architecture specific UEFI setup
> > > >
> > > > On 2/7/20 4:13 AM,
; > > Sent: Wednesday, February 12, 2020 2:26 AM
> > > To: Chang, Abner (HPS SW/FW Technologist) ;
> > > Atish Patra ; Ard Biesheuvel
> > >
> > > Cc: Alexander Graf ; U-Boot Mailing List > > b...@lists.denx.de>; Atish Patra ;
> > > l...@nuviain
e>; Atish Patra ;
> l...@nuviainc.com
> Subject: Re: [PATCH v2 1/1] efi_loader: architecture specific UEFI setup
>
> On 2/7/20 4:13 AM, Chang, Abner (HPS SW/FW Technologist) wrote:
> >
> >
> >> -Original Message-
> >> From: Atish Patra [mailto:
> > Atish Patra ; Ard Biesheuvel
> >
> > Cc: Alexander Graf ; U-Boot Mailing List > b...@lists.denx.de>; Atish Patra ;
> > l...@nuviainc.com
> > Subject: Re: [PATCH v2 1/1] efi_loader: architecture specific UEFI setup
> >
> > On 2/7/20 4:13 AM, Chan
Mailing List ; Atish
Patra ; l...@nuviainc.com
Subject: Re: [PATCH v2 1/1] efi_loader: architecture specific UEFI setup
On Thu, Feb 6, 2020 at 2:07 PM Ard Biesheuvel
wrote:
On Thu, 6 Feb 2020 at 21:06, Atish Patra wrote:
On Thu, Feb 6, 2020 at 12:10 PM Alexander Graf wrote:
On 06.02.20 19:28
On Wed, Feb 05, 2020 at 12:37:03PM +0100, Heinrich Schuchardt wrote:
> Hello Daniel, hello Leif,
>
> what is the GRUB view on this discussion?
Alex, could you chime in on this as a GRUB RISC-V maintainer?
Daniel
> Best regards
>
> Heinrich
>
> On 2/5/20 12:32 PM, Heinrich Schuchardt wrote:
> > O
atra ; l...@nuviainc.com
> Subject: Re: [PATCH v2 1/1] efi_loader: architecture specific UEFI setup
>
> On Thu, Feb 6, 2020 at 2:07 PM Ard Biesheuvel
> wrote:
> >
> > On Thu, 6 Feb 2020 at 21:06, Atish Patra wrote:
> > >
> > > On Thu, Feb 6, 2020 at 12:10 PM Alexa
On Thu, Feb 6, 2020 at 2:07 PM Ard Biesheuvel wrote:
>
> On Thu, 6 Feb 2020 at 21:06, Atish Patra wrote:
> >
> > On Thu, Feb 6, 2020 at 12:10 PM Alexander Graf wrote:
> > >
> > >
> > > On 06.02.20 19:28, Atish Patra wrote:
> > > > On Tue, Feb 4, 2020 at 11:43 PM Ard Biesheuvel
> > > > wrote:
>
On Thu, 6 Feb 2020 at 21:06, Atish Patra wrote:
>
> On Thu, Feb 6, 2020 at 12:10 PM Alexander Graf wrote:
> >
> >
> > On 06.02.20 19:28, Atish Patra wrote:
> > > On Tue, Feb 4, 2020 at 11:43 PM Ard Biesheuvel
> > > wrote:
> > >> On Wed, 5 Feb 2020 at 05:53, Heinrich Schuchardt
> > >> wrote:
>
> Am 06.02.2020 um 22:06 schrieb Atish Patra :
>
> On Thu, Feb 6, 2020 at 12:10 PM Alexander Graf wrote:
>>
>>
>>> On 06.02.20 19:28, Atish Patra wrote:
>>> On Tue, Feb 4, 2020 at 11:43 PM Ard Biesheuvel
>>> wrote:
On Wed, 5 Feb 2020 at 05:53, Heinrich Schuchardt
wrote:
> R
On Thu, Feb 6, 2020 at 12:10 PM Alexander Graf wrote:
>
>
> On 06.02.20 19:28, Atish Patra wrote:
> > On Tue, Feb 4, 2020 at 11:43 PM Ard Biesheuvel
> > wrote:
> >> On Wed, 5 Feb 2020 at 05:53, Heinrich Schuchardt
> >> wrote:
> >>> RISC-V booting currently is based on a per boot stage lottery t
On 06.02.20 19:28, Atish Patra wrote:
On Tue, Feb 4, 2020 at 11:43 PM Ard Biesheuvel
wrote:
On Wed, 5 Feb 2020 at 05:53, Heinrich Schuchardt wrote:
RISC-V booting currently is based on a per boot stage lottery to determine
the active CPU. The Hart State Management (HSM) SBI extension replac
On Tue, Feb 4, 2020 at 11:43 PM Ard Biesheuvel
wrote:
>
> On Wed, 5 Feb 2020 at 05:53, Heinrich Schuchardt wrote:
> >
> > RISC-V booting currently is based on a per boot stage lottery to determine
> > the active CPU. The Hart State Management (HSM) SBI extension replaces
> > this lottery by using
Hello Daniel, hello Leif,
what is the GRUB view on this discussion?
Best regards
Heinrich
On 2/5/20 12:32 PM, Heinrich Schuchardt wrote:
On 2/5/20 8:43 AM, Ard Biesheuvel wrote:
On Wed, 5 Feb 2020 at 05:53, Heinrich Schuchardt
wrote:
RISC-V booting currently is based on a per boot stage l
On 2/5/20 8:43 AM, Ard Biesheuvel wrote:
On Wed, 5 Feb 2020 at 05:53, Heinrich Schuchardt wrote:
RISC-V booting currently is based on a per boot stage lottery to determine
the active CPU. The Hart State Management (HSM) SBI extension replaces
this lottery by using a dedicated primary CPU.
Cf.
On Wed, 5 Feb 2020 at 05:53, Heinrich Schuchardt wrote:
>
> RISC-V booting currently is based on a per boot stage lottery to determine
> the active CPU. The Hart State Management (HSM) SBI extension replaces
> this lottery by using a dedicated primary CPU.
>
> Cf. Hart State Management Extension,
RISC-V booting currently is based on a per boot stage lottery to determine
the active CPU. The Hart State Management (HSM) SBI extension replaces
this lottery by using a dedicated primary CPU.
Cf. Hart State Management Extension, Extension ID: 0x48534D (HSM)
https://github.com/riscv/riscv-sbi-doc/
25 matches
Mail list logo
