On Fri, May 20, 2016 at 3:51 AM, Andrei Gherzan wrote:
> On Fri, May 20, 2016 at 12:47:40PM +0200, Herve Jourdain wrote:
>> Hi Andrei, Khem,
>>
>> That's what I implemented in the upcoming v2 - except for the python
>> checking function part.
>> One thing, shall I call the variable CMA_SIZE, or VC
On Fri, May 20, 2016 at 12:47:40PM +0200, Herve Jourdain wrote:
> Hi Andrei, Khem,
>
> That's what I implemented in the upcoming v2 - except for the python
> checking function part.
> One thing, shall I call the variable CMA_SIZE, or VC4_CMA_SIZE?
> I know CMA is kind of common, but we're using thi
Hi Andrei, Khem,
That's what I implemented in the upcoming v2 - except for the python
checking function part.
One thing, shall I call the variable CMA_SIZE, or VC4_CMA_SIZE?
I know CMA is kind of common, but we're using this only to trigger a
parameter to the v4c overlay.
Any opinion? (in the curr
