On 2017-02-16 09:38, Arend Van Spriel wrote:
On 16-2-2017 8:26, Rafał Miłecki wrote:
From: Rafał Miłecki
Failing to load NVRAM file isn't critical if we manage to get platform
one in the fallback path. It means warnings like:
[ 10.801506] brcmfmac :01:00.0: Direct
On 16-2-2017 10:32, Rafał Miłecki wrote:
> On 2017-02-16 10:18, Arend Van Spriel wrote:
>> On 16-2-2017 10:04, Rafał Miłecki wrote:
>>> On 2017-02-16 09:38, Arend Van Spriel wrote:
On 16-2-2017 8:26, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> Failing to load
On 2017-02-16 10:18, Arend Van Spriel wrote:
On 16-2-2017 10:04, Rafał Miłecki wrote:
On 2017-02-16 09:38, Arend Van Spriel wrote:
On 16-2-2017 8:26, Rafał Miłecki wrote:
From: Rafał Miłecki
Failing to load NVRAM file isn't critical if we manage to get
platform
one in
On 16-2-2017 10:04, Rafał Miłecki wrote:
> On 2017-02-16 09:38, Arend Van Spriel wrote:
>> On 16-2-2017 8:26, Rafał Miłecki wrote:
>>> From: Rafał Miłecki
>>>
>>> Failing to load NVRAM file isn't critical if we manage to get platform
>>> one in the fallback path. It means
On 16-2-2017 8:26, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> Failing to load NVRAM file isn't critical if we manage to get platform
> one in the fallback path. It means warnings like:
> [ 10.801506] brcmfmac :01:00.0: Direct firmware load for
>