On Tue, Jul 11, 2017 at 2:38 PM, Simon Horman
wrote:
> Add fallback compatibility string for R-Car Gen 1, 2 and 3.
>
> In the case of Renesas R-Car hardware we know that there are generations of
> SoCs, f.e. Gen 1 and 2. But beyond that its not clear what the
Hi Simon,
CC DT
On Wed, Jul 12, 2017 at 7:49 AM, Simon Horman wrote:
> On Tue, Jul 11, 2017 at 07:59:31PM +0200, Geert Uytterhoeven wrote:
>> On Tue, Jul 11, 2017 at 2:38 PM, Simon Horman
>> wrote:
>> > Add fallback compatibility string for R-Car
On Tue, Jul 11, 2017 at 07:59:31PM +0200, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Tue, Jul 11, 2017 at 2:38 PM, Simon Horman
> wrote:
> > Add fallback compatibility string for R-Car Gen 1, 2 and 3.
> >
> > In the case of Renesas R-Car hardware we know that there
Hi Simon,
On Tue, Jul 11, 2017 at 2:38 PM, Simon Horman
wrote:
> Add fallback compatibility string for R-Car Gen 1, 2 and 3.
>
> In the case of Renesas R-Car hardware we know that there are generations of
> SoCs, f.e. Gen 1 and 2. But beyond that its not clear what
Add fallback compatibility string for R-Car Gen 1, 2 and 3.
In the case of Renesas R-Car hardware we know that there are generations of
SoCs, f.e. Gen 1 and 2. But beyond that its not clear what the relationship
between IP blocks might be. For example, I believe that r8a7790 is older
than r8a7791