On Tue, May 08, 2018 at 11:57:38AM +0100, Daniel Thompson wrote:
> > > > No sure how other OSes like Windows or ubuntu make this happen. But
> > > > they do call SetVariable during runtime such as to set OsIndications
> > > > or BootNext to reboot to BIOS system utility.
> > >
> > > Sorry, just no
gt; > To: Chang, Abner (HPS SW/FW Technologist)
> > Cc: Architecture Mailman List ;
> > arm.ebbr-
> > disc...@arm.com
> > Subject: Re: [Arm.ebbr-discuss] ebbr: boot behaviour without persistent
> > variables
> >
> > On Mon, Apr 30, 2018 at 02:26:22PM +,
> disc...@arm.com
> Subject: Re: [Arm.ebbr-discuss] ebbr: boot behaviour without persistent
> variables
>
> On Mon, Apr 30, 2018 at 02:26:22PM +, Chang, Abner (HPS SW/FW
> Technologist) wrote:
> > > > I guess it would be possible to implement this in code. The
> > &
On Mon, Apr 30, 2018 at 02:26:22PM +, Chang, Abner (HPS SW/FW Technologist)
wrote:
> > > I guess it would be possible to implement this in code. The problem is
> > > that the UEFI spec does not cover any of this, and so there is no way
> > > for the OS to find out whether it can call SetVariab
> -Original Message-
> From: Udit Kumar [mailto:udit.ku...@nxp.com]
> Sent: Wednesday, May 02, 2018 12:31 PM
> To: Chang, Abner (HPS SW/FW Technologist) ; Ard
> Biesheuvel
> Cc: Architecture Mailman List ; arm.ebbr-
> disc...@arm.com
> Subject: RE: [Arm.
> > Also, eMMC controllers (which are more widely used on mobile platforms
> > as the only available storage controller) use DMA under the OS, which
> > complicates things even further when attempting to share such a
> > controller between the OS and the firmware.
> Agree with this. May need other
On 04/30/2018 10:26 AM, Chang, Abner (HPS SW/FW Technologist) wrote:
>> On 30 April 2018 at 16:00, Ard Biesheuvel wrote:
>>> On 30 April 2018 at 15:57, Chang, Abner (HPS SW/FW Technologist)
>> Also, eMMC controllers (which are more widely used on mobile platforms as
>> the only available storage
.ebbr-disc...@arm.com
> Subject: Re: [Arm.ebbr-discuss] ebbr: boot behaviour without persistent
> variables
>
> On 30 April 2018 at 16:00, Ard Biesheuvel wrote:
> > On 30 April 2018 at 15:57, Chang, Abner (HPS SW/FW Technologist)
> > wrote:
> >> Hi Ard,
> >&
April 29, 2018 12:21 AM
>>> To: Chang, Abner (HPS SW/FW Technologist)
>>> Cc: Daniel Thompson ; Grant Likely
>>> ; Architecture Mailman List >> architect...@lists.linaro.org>; l...@cam-list1.cambridge.arm.com;
>>> b...@cam-list1.cambridge.arm.com;
; Cc: Daniel Thompson ; Grant Likely
>> ; Architecture Mailman List > architect...@lists.linaro.org>; l...@cam-list1.cambridge.arm.com;
>> b...@cam-list1.cambridge.arm.com; arm.ebbr-disc...@arm.com
>> Subject: Re: [Arm.ebbr-discuss] ebbr: boot behaviour without persistent
>
g>; l...@cam-list1.cambridge.arm.com;
> b...@cam-list1.cambridge.arm.com; arm.ebbr-disc...@arm.com
> Subject: Re: [Arm.ebbr-discuss] ebbr: boot behaviour without persistent
> variables
>
> On 28 April 2018 at 15:46, Chang, Abner (HPS SW/FW Technologist)
> wrote:
> >
On 28 April 2018 at 15:46, Chang, Abner (HPS SW/FW Technologist)
wrote:
> I am behind this topic and not familiar with embedded system with U-boot.
> Some dumb questions below.
> Why there is no persistent storage on platform? I thought at least EEPROM is
> on platform. Can't EEPROM be the varst
iday, April 27, 2018 10:41 PM
To: Grant Likely
Cc: Architecture Mailman List ;
b...@cam-list1.cambridge.arm.com; arm.ebbr-disc...@arm.com;
l...@cam-list1.cambridge.arm.com
Subject: Re: [Arm.ebbr-discuss] ebbr: boot behaviour without persistent
variables
On Fri, Apr 27, 2018 at 11:22:27AM +0100
On Fri, Apr 27, 2018 at 11:22:27AM +0100, Grant Likely wrote:
> On 26/04/2018 17:52, William Mills wrote:
> >
> >
> > On 04/26/2018 08:43 AM, Alexander Graf wrote:
> > > On 04/26/2018 10:51 AM, Grant Likely wrote:
> > > > On 25/04/2018 19:34, Alexander Graf wrote:
> > > > >
> > > > >
> > > > >
On Fri, Apr 27, 2018 at 09:58:07AM +0100, Leif Lindholm wrote:
> > This is the "priority" statement I think it problematic as discussed on
> > todays call. I think Boot### should be followed if present but boot
> > firmware writers should be cautioned not to hard code stupid stuff into
> > them.
On 26/04/2018 17:52, William Mills wrote:
On 04/26/2018 08:43 AM, Alexander Graf wrote:
On 04/26/2018 10:51 AM, Grant Likely wrote:
On 25/04/2018 19:34, Alexander Graf wrote:
On 25.04.18 19:54, Leif Lindholm wrote:
I took an action last week to provide a block of text for how
platforms wi
On 26.04.18 18:52, William Mills wrote:
>
>
> On 04/26/2018 08:43 AM, Alexander Graf wrote:
>> On 04/26/2018 10:51 AM, Grant Likely wrote:
>>> On 25/04/2018 19:34, Alexander Graf wrote:
On 25.04.18 19:54, Leif Lindholm wrote:
> I took an action last week to provide a block of
On Thu, Apr 26, 2018 at 12:52:04PM -0400, William Mills wrote:
> Driver and Boot### global variable entries. If present, these
> entries will be processed in the order specified by corresponding
> statically defined SysPrepOrder, DriverOrder and BootOrder global
> variables.
On 04/26/2018 08:43 AM, Alexander Graf wrote:
> On 04/26/2018 10:51 AM, Grant Likely wrote:
>> On 25/04/2018 19:34, Alexander Graf wrote:
>>>
>>>
>>> On 25.04.18 19:54, Leif Lindholm wrote:
I took an action last week to provide a block of text for how
platforms without persistent variab
On 04/26/2018 10:51 AM, Grant Likely wrote:
On 25/04/2018 19:34, Alexander Graf wrote:
On 25.04.18 19:54, Leif Lindholm wrote:
I took an action last week to provide a block of text for how
platforms without persistent variable storage should behave. Here's my
opening play:
Thanks a lot for
On 25/04/2018 19:34, Alexander Graf wrote:
On 25.04.18 19:54, Leif Lindholm wrote:
I took an action last week to provide a block of text for how
platforms without persistent variable storage should behave. Here's my
opening play:
Thanks a lot for getting this started!
Boot manager behavio
On 25.04.18 19:54, Leif Lindholm wrote:
> I took an action last week to provide a block of text for how
> platforms without persistent variable storage should behave. Here's my
> opening play:
Thanks a lot for getting this started!
>
> Boot manager behaviour without persistent variable store
>
22 matches
Mail list logo
