Once spi-nor flash write issue fixed in driver, ability to select FW_B
works, as Aaron indicated it should.
Cheers,
T.mike
On 2017-02-15 15:01, ttu...@codeaurora.org wrote:
On 2017-02-15 13:34, Aaron Durbin wrote:
On Wed, Feb 15, 2017 at 3:20 PM, wrote:
On
On 2017-02-15 13:34, Aaron Durbin wrote:
On Wed, Feb 15, 2017 at 3:20 PM, wrote:
On 2017-02-15 09:45, Aaron Durbin via coreboot wrote:
On Wed, Feb 15, 2017 at 11:38 AM, wrote:
On 2017-02-15 07:46, Aaron Durbin via coreboot wrote:
On Tue,
On Wed, Feb 15, 2017 at 3:20 PM, wrote:
> On 2017-02-15 09:45, Aaron Durbin via coreboot wrote:
>>
>> On Wed, Feb 15, 2017 at 11:38 AM, wrote:
>>>
>>> On 2017-02-15 07:46, Aaron Durbin via coreboot wrote:
On Tue, Feb 14, 2017 at 8:26
On 2017-02-15 09:45, Aaron Durbin via coreboot wrote:
On Wed, Feb 15, 2017 at 11:38 AM, wrote:
On 2017-02-15 07:46, Aaron Durbin via coreboot wrote:
On Tue, Feb 14, 2017 at 8:26 PM, wrote:
Folks,
I'm working on coreboot on ARMv8
On Wed, Feb 15, 2017 at 11:38 AM, wrote:
> On 2017-02-15 07:46, Aaron Durbin via coreboot wrote:
>>
>> On Tue, Feb 14, 2017 at 8:26 PM, wrote:
>>>
>>>
>>> Folks,
>>> I'm working on coreboot on ARMv8 architecture and recently attempted to
>>> verify
On 2017-02-15 07:46, Aaron Durbin via coreboot wrote:
On Tue, Feb 14, 2017 at 8:26 PM, wrote:
Folks,
I'm working on coreboot on ARMv8 architecture and recently attempted
to
verify FW_B can be selected if FW_A is corrupted.
In reviewing the code-path through coreboot
On Tue, Feb 14, 2017 at 8:26 PM, wrote:
>
> Folks,
> I'm working on coreboot on ARMv8 architecture and recently attempted to
> verify FW_B can be selected if FW_A is corrupted.
>
> In reviewing the code-path through coreboot vboot wrapper and
> vboot_reference library I'm
Folks,
I'm working on coreboot on ARMv8 architecture and recently attempted to
verify FW_B can be selected if FW_A is corrupted.
In reviewing the code-path through coreboot vboot wrapper and
vboot_reference library I'm not understanding the logic.
The logic appears to be that
8 matches
Mail list logo