Hi Kever,
Ahh, yup! You're totally right! I didn't see Heiko's patch earlier.
My mistake.
Cheers,
Alex
On 18 May 2017 12:38 PM, "Kever Yang" wrote:
> Hi Alex,
>
>
> Thanks for your patch, but this patch is just the same with the one from
> Heiko[0], right?
>
>
>
Hi Alex,
Thanks for your patch, but this patch is just the same with the one from
Heiko[0], right?
Thanks,
- Kever
[0] https://patchwork.ozlabs.org/patch/758272/
On 05/15/2017 08:01 PM, Alex Hixon wrote:
The config name enabling the rk3399-pinctrl driver is spelled wrong, so
it does
On 15 May 2017 at 06:30, Tom Rini wrote:
> On Mon, May 15, 2017 at 10:01:32PM +1000, Alex Hixon wrote:
>
>> The config name enabling the rk3399-pinctrl driver is spelled wrong, so
>> it does not get built. This causes SPL to fail during board init.
>>
>> Make rk3399-firefly
> From: Alex Hixon
> Date: Mon, 15 May 2017 22:01:32 +1000
>
> The config name enabling the rk3399-pinctrl driver is spelled wrong, so
> it does not get built. This causes SPL to fail during board init.
>
> Make rk3399-firefly boot by enabling the pinctrl driver via the
On Mon, May 15, 2017 at 10:01:32PM +1000, Alex Hixon wrote:
> The config name enabling the rk3399-pinctrl driver is spelled wrong, so
> it does not get built. This causes SPL to fail during board init.
>
> Make rk3399-firefly boot by enabling the pinctrl driver via the correct
> config name.
>
The config name enabling the rk3399-pinctrl driver is spelled wrong, so
it does not get built. This causes SPL to fail during board init.
Make rk3399-firefly boot by enabling the pinctrl driver via the correct
config name.
Signed-off-by: Alex Hixon
---
6 matches
Mail list logo