Re: etnaviv: PHYS_OFFSET usage

Hi Lucas, On Wed, 2017-11-15 at 18:56 +0100, Lucas Stach wrote: > Am Mittwoch, den 15.11.2017, 17:36 + schrieb Alexey Brodkin: [snip] > I'm not keen on having a private memory region for the GPU. Normally we > just use the shared system CMA memory region (and we will point the > linear memor

Re: etnaviv: PHYS_OFFSET usage

Hi Lucas, On Wed, 2017-11-15 at 17:44 +0100, Lucas Stach wrote: > Hi Alexey, > > Am Mittwoch, den 15.11.2017, 16:24 + schrieb Alexey Brodkin: > > > > Hi Lucas, > > > > As we discussed on ELCE last month in Prague we have Vivante GPU > > built-in our new ARC HSDK development board. > > > >

etnaviv: PHYS_OFFSET usage

Hi Lucas, As we discussed on ELCE last month in Prague we have Vivante GPU built-in our new ARC HSDK development board. And even though [thanks to your suggestions] I got Etnaviv driver working perfectly fine on our board I faced one quite a tricky situation [which I dirty worked-around for now].

Re: etnaviv: PHYS_OFFSET usage

Am Mittwoch, den 15.11.2017, 17:36 + schrieb Alexey Brodkin: > Hi Lucas, > > On Wed, 2017-11-15 at 17:44 +0100, Lucas Stach wrote: > > Hi Alexey, > > > > Am Mittwoch, den 15.11.2017, 16:24 + schrieb Alexey Brodkin: > > > > > > Hi Lucas, > > > > > > As we discussed on ELCE last month in

Re: etnaviv: PHYS_OFFSET usage

Hi Alexey, Am Mittwoch, den 15.11.2017, 16:24 + schrieb Alexey Brodkin: > Hi Lucas, > > As we discussed on ELCE last month in Prague we have Vivante GPU > built-in our new ARC HSDK development board. > > And even though [thanks to your suggestions] I got Etnaviv driver > working perfectly fi