Hi Matthias,
Am 17.09.19 um 20:03 schrieb Stefan Wahren:
> Hi Matthias,
>
> Am 17.09.19 um 11:04 schrieb Matthias Brugger:
>> On 16/09/2019 21:19, Stefan Wahren wrote:
>>> Hi Matthias,
>>>
>>> [drop uninvolved receiver]
>>>
>>> Am 13.09.19 um 12:39 schrieb Matthias Brugger:
>>>
>>> So my
Hi Matthias,
Am 17.09.19 um 11:04 schrieb Matthias Brugger:
>
> On 16/09/2019 21:19, Stefan Wahren wrote:
>> Hi Matthias,
>>
>> [drop uninvolved receiver]
>>
>> Am 13.09.19 um 12:39 schrieb Matthias Brugger:
>>> If you talk about the
>>> downstream kernel, I suppose you mean we should
On 16/09/2019 21:19, Stefan Wahren wrote:
> Hi Matthias,
>
> [drop uninvolved receiver]
>
> Am 13.09.19 um 12:39 schrieb Matthias Brugger:
>>
>> If you talk about the
>> downstream kernel, I suppose you mean we should change this in the FW DT
>> blob
>> and in the downstream
Hi Matthias,
[drop uninvolved receiver]
Am 13.09.19 um 12:39 schrieb Matthias Brugger:
>
> If you talk about the
> downstream kernel, I suppose you mean we should change this in the FW DT
> blob
> and in the downstream kernel. That would work for me.
>
> Did I
On 13/09/2019 12:08, Stefan Wahren wrote:
> Am 13.09.19 um 11:25 schrieb Matthias Brugger:
>>
>> On 13/09/2019 10:50, Stefan Wahren wrote:
>>> Am 13.09.19 um 10:09 schrieb Matthias Brugger:
On 12/09/2019 21:32, Stefan Wahren wrote:
> Am 12.09.19 um 19:18 schrieb Matthias Brugger:
Am 13.09.19 um 11:25 schrieb Matthias Brugger:
>
> On 13/09/2019 10:50, Stefan Wahren wrote:
>> Am 13.09.19 um 10:09 schrieb Matthias Brugger:
>>> On 12/09/2019 21:32, Stefan Wahren wrote:
Am 12.09.19 um 19:18 schrieb Matthias Brugger:
> On 10/09/2019 11:27, Matthias Brugger wrote:
>>
On 13/09/2019 10:50, Stefan Wahren wrote:
> Am 13.09.19 um 10:09 schrieb Matthias Brugger:
>>
>> On 12/09/2019 21:32, Stefan Wahren wrote:
>>> Am 12.09.19 um 19:18 schrieb Matthias Brugger:
On 10/09/2019 11:27, Matthias Brugger wrote:
> On 09/09/2019 21:33, Stefan Wahren wrote:
>>
Am 13.09.19 um 10:09 schrieb Matthias Brugger:
>
> On 12/09/2019 21:32, Stefan Wahren wrote:
>> Am 12.09.19 um 19:18 schrieb Matthias Brugger:
>>> On 10/09/2019 11:27, Matthias Brugger wrote:
On 09/09/2019 21:33, Stefan Wahren wrote:
> Hi Nicolas,
>
> Am 09.09.19 um 11:58 schrieb
On 12/09/2019 21:32, Stefan Wahren wrote:
>
> Am 12.09.19 um 19:18 schrieb Matthias Brugger:
>>
>> On 10/09/2019 11:27, Matthias Brugger wrote:
>>>
>>> On 09/09/2019 21:33, Stefan Wahren wrote:
Hi Nicolas,
Am 09.09.19 um 11:58 schrieb Nicolas Saenz Julienne:
> Hi all,
>
On 12/09/2019 21:32, Stefan Wahren wrote:
>
> Am 12.09.19 um 19:18 schrieb Matthias Brugger:
>>
>> On 10/09/2019 11:27, Matthias Brugger wrote:
>>>
>>> On 09/09/2019 21:33, Stefan Wahren wrote:
Hi Nicolas,
Am 09.09.19 um 11:58 schrieb Nicolas Saenz Julienne:
> Hi all,
>
Am 12.09.19 um 19:18 schrieb Matthias Brugger:
>
> On 10/09/2019 11:27, Matthias Brugger wrote:
>>
>> On 09/09/2019 21:33, Stefan Wahren wrote:
>>> Hi Nicolas,
>>>
>>> Am 09.09.19 um 11:58 schrieb Nicolas Saenz Julienne:
Hi all,
this series attempts to address some issues we found
On 9/12/19 10:18 AM, Matthias Brugger wrote:
>
>
> On 10/09/2019 11:27, Matthias Brugger wrote:
>>
>>
>> On 09/09/2019 21:33, Stefan Wahren wrote:
>>> Hi Nicolas,
>>>
>>> Am 09.09.19 um 11:58 schrieb Nicolas Saenz Julienne:
Hi all,
this series attempts to address some issues we found
On 10/09/2019 11:27, Matthias Brugger wrote:
>
>
> On 09/09/2019 21:33, Stefan Wahren wrote:
>> Hi Nicolas,
>>
>> Am 09.09.19 um 11:58 schrieb Nicolas Saenz Julienne:
>>> Hi all,
>>> this series attempts to address some issues we found while bringing up
>>> the new Raspberry Pi 4 in arm64 and
On 09/09/2019 21:33, Stefan Wahren wrote:
> Hi Nicolas,
>
> Am 09.09.19 um 11:58 schrieb Nicolas Saenz Julienne:
>> Hi all,
>> this series attempts to address some issues we found while bringing up
>> the new Raspberry Pi 4 in arm64 and it's intended to serve as a follow
>> up of these
On Mon, 2019-09-09 at 21:33 +0200, Stefan Wahren wrote:
> Hi Nicolas,
>
> Am 09.09.19 um 11:58 schrieb Nicolas Saenz Julienne:
> > Hi all,
> > this series attempts to address some issues we found while bringing up
> > the new Raspberry Pi 4 in arm64 and it's intended to serve as a follow
> > up
Hi Nicolas,
Am 09.09.19 um 11:58 schrieb Nicolas Saenz Julienne:
> Hi all,
> this series attempts to address some issues we found while bringing up
> the new Raspberry Pi 4 in arm64 and it's intended to serve as a follow
> up of these discussions:
> v4: https://lkml.org/lkml/2019/9/6/352
> v3:
Hi all,
this series attempts to address some issues we found while bringing up
the new Raspberry Pi 4 in arm64 and it's intended to serve as a follow
up of these discussions:
v4: https://lkml.org/lkml/2019/9/6/352
v3: https://lkml.org/lkml/2019/9/2/589
v2: https://lkml.org/lkml/2019/8/20/767
v1:
17 matches
Mail list logo