Hi Stefano,
On 02/11/2015 02:07 AM, Stefano Babic wrote:
> Hi Eric,
>
> On 10/02/2015 18:19, Eric Nelson wrote:
>> Hi Stefano,
>>
>> On 02/05/2015 11:49 AM, Stefano Babic wrote:
>>> Hi Eric,
>>>
>>> On 05/02/2015 19:22, Eric Nelson wrote:
>>>
Certainly, but it seems wrong to make a deci
Hi Eric,
On 10/02/2015 18:19, Eric Nelson wrote:
> Hi Stefano,
>
> On 02/05/2015 11:49 AM, Stefano Babic wrote:
>> Hi Eric,
>>
>> On 05/02/2015 19:22, Eric Nelson wrote:
>>
>>>
>>> Certainly, but it seems wrong to make a decision about where and how
>>> this might get passed to an O/S in code.
>
On 10 Feb 2015, eric.nel...@boundarydevices.com wrote:
> I posted a couple of additional options and received no comment
> from you.
> Neither of them works as-is because of the ordering of events
> (print_cpuinfo() is called before restoring the environment),
> so your suggestion would require
Hi Stefano,
On 02/05/2015 11:49 AM, Stefano Babic wrote:
> Hi Eric,
>
> On 05/02/2015 19:22, Eric Nelson wrote:
>
>>
>> Certainly, but it seems wrong to make a decision about where and how
>> this might get passed to an O/S in code.
>>
>> If we want to generalize it, I'd be inclined to add comma
On 2/5/2015 4:01 PM, Eric Nelson wrote:
> Hi Stefano,
>
> On 02/05/2015 11:49 AM, Stefano Babic wrote:
>> Hi Eric,
>>
>> On 05/02/2015 19:22, Eric Nelson wrote:
>>
>>>
>>> Certainly, but it seems wrong to make a decision about where and how
>>> this might get passed to an O/S in code.
>>>
>>> If w
Hi Stefano,
On 02/05/2015 11:49 AM, Stefano Babic wrote:
> Hi Eric,
>
> On 05/02/2015 19:22, Eric Nelson wrote:
>
>>
>> Certainly, but it seems wrong to make a decision about where and how
>> this might get passed to an O/S in code.
>>
>> If we want to generalize it, I'd be inclined to add comma
Hi Eric,
On 05/02/2015 19:22, Eric Nelson wrote:
>
> Certainly, but it seems wrong to make a decision about where and how
> this might get passed to an O/S in code.
>
> If we want to generalize it, I'd be inclined to add commands to
> query (into a variable) and clear the reset cause.
>
> That
Hi Stefano,
On 02/05/2015 10:52 AM, Stefano Babic wrote:
> Hi Eric,
>
> On 05/02/2015 18:22, Eric Nelson wrote:
>
There is very similar code in 'arch/arm/cpu/armv7/vf610/generic.c'. The
write is for a hard power on case where these reason registers are full
of weird bogus values
Hi Eric,
On 05/02/2015 18:22, Eric Nelson wrote:
>>> There is very similar code in 'arch/arm/cpu/armv7/vf610/generic.c'. The
>>> write is for a hard power on case where these reason registers are full
>>> of weird bogus values (at least on Vybrid; I suspect on iMx). In the
>>> case of a non-POR
Hi Stefano,
On 02/05/2015 10:19 AM, Stefano Babic wrote:
> Hi Bill,
>
> On 05/02/2015 17:28, Bill Pringlemeir wrote:
>> On 4 Feb 2015, eric.nel...@boundarydevices.com wrote:
>>
>>> The cause of a reset is generally useful, and shouldn't be
>>> blindly cleared in the process of displaying it as a
Hi Bill,
On 05/02/2015 17:28, Bill Pringlemeir wrote:
> On 4 Feb 2015, eric.nel...@boundarydevices.com wrote:
>
>> The cause of a reset is generally useful, and shouldn't be
>> blindly cleared in the process of displaying it as a part
>> of the boot announcement.
>>
>> If a particular system wan
Hi Bill,
On 02/05/2015 09:28 AM, Bill Pringlemeir wrote:
> On 4 Feb 2015, eric.nel...@boundarydevices.com wrote:
>
>> The cause of a reset is generally useful, and shouldn't be
>> blindly cleared in the process of displaying it as a part
>> of the boot announcement.
>>
>> If a particular system
On 4 Feb 2015, eric.nel...@boundarydevices.com wrote:
> The cause of a reset is generally useful, and shouldn't be
> blindly cleared in the process of displaying it as a part
> of the boot announcement.
>
> If a particular system wants to clear it out, this should
> be done later after there's an
On 04/02/2015 22:51, Eric Nelson wrote:
> The cause of a reset is generally useful, and shouldn't be
> blindly cleared in the process of displaying it as a part
> of the boot announcement.
>
> If a particular system wants to clear it out, this should
> be done later after there's an opportunity fo
The cause of a reset is generally useful, and shouldn't be
blindly cleared in the process of displaying it as a part
of the boot announcement.
If a particular system wants to clear it out, this should
be done later after there's an opportunity for code or
boot commands to read the value.
Signed-o
15 matches
Mail list logo
