On 31.10.22 г. 12:13 ч., Tony Lindgren wrote:
* Ivaylo Dimitrov [221031 06:55]:
On 31.10.22 г. 0:08 ч., H. Nikolaus Schaller wrote:
[ 39.419846] WARNING: CPU: 0 PID: 3673 at drivers/bus/omap_l3_noc.c:139
l3_interrupt_handler+0x23c/0x330
[ 39.429914] 4400.l3-noc:L3 Custom Error: MAS
On 31.10.22 г. 12:13 ч., Tony Lindgren wrote:
* Ivaylo Dimitrov [221031 06:55]:
On 31.10.22 г. 0:08 ч., H. Nikolaus Schaller wrote:
[ 39.419846] WARNING: CPU: 0 PID: 3673 at drivers/bus/omap_l3_noc.c:139
l3_interrupt_handler+0x23c/0x330
[ 39.429914] 4400.l3-noc:L3 Custom Error: MAS
* Ivaylo Dimitrov [221031 06:55]:
> On 31.10.22 г. 0:08 ч., H. Nikolaus Schaller wrote:
> > [ 39.419846] WARNING: CPU: 0 PID: 3673 at drivers/bus/omap_l3_noc.c:139
> > l3_interrupt_handler+0x23c/0x330
> > [ 39.429914] 4400.l3-noc:L3 Custom Error: MASTER MPU TARGET GPMC
> > (Idle): Data A
Hi Ivaylo,
> Am 31.10.2022 um 10:58 schrieb Ivaylo Dimitrov :
>
>
>
> On 31.10.22 г. 9:57 ч., H. Nikolaus Schaller wrote:
>>> Am 31.10.2022 um 08:44 schrieb H. Nikolaus Schaller :
>>>
>>> Hi Ivaylo,
>>>
Am 31.10.2022 um 08:05 schrieb Ivaylo Dimitrov
:
HI Nikolaus,
On 31.10.22 г. 9:57 ч., H. Nikolaus Schaller wrote:
Am 31.10.2022 um 08:44 schrieb H. Nikolaus Schaller :
Hi Ivaylo,
Am 31.10.2022 um 08:05 schrieb Ivaylo Dimitrov :
HI Nikolaus,
On 31.10.22 г. 0:08 ч., H. Nikolaus Schaller wrote:
Hi Ivaylo,
it took a while until I found time to test
> Am 31.10.2022 um 08:44 schrieb H. Nikolaus Schaller :
>
> Hi Ivaylo,
>
>> Am 31.10.2022 um 08:05 schrieb Ivaylo Dimitrov :
>>
>> HI Nikolaus,
>>
>> On 31.10.22 г. 0:08 ч., H. Nikolaus Schaller wrote:
>>> Hi Ivaylo,
>>> it took a while until I found time to test newer kernels (mainline + Le
Hi Ivaylo,
> Am 31.10.2022 um 08:05 schrieb Ivaylo Dimitrov :
>
> HI Nikolaus,
>
> On 31.10.22 г. 0:08 ч., H. Nikolaus Schaller wrote:
>> Hi Ivaylo,
>> it took a while until I found time to test newer kernels (mainline + Letux
>> additions)
>> on the OMAP5 Pyra but unfortunately I did not get s
HI Nikolaus,
On 31.10.22 г. 0:08 ч., H. Nikolaus Schaller wrote:
Hi Ivaylo,
it took a while until I found time to test newer kernels (mainline + Letux
additions)
on the OMAP5 Pyra but unfortunately I did not get screen display for v6.1. Even
worse,
the console was flooded by
Could you elabo
Hi Ivaylo,
it took a while until I found time to test newer kernels (mainline + Letux
additions)
on the OMAP5 Pyra but unfortunately I did not get screen display for v6.1. Even
worse,
the console was flooded by
[ 39.419846] WARNING: CPU: 0 PID: 3673 at drivers/bus/omap_l3_noc.c:139
l3_interr
On 30.08.22 г. 21:23 ч., Tomi Valkeinen wrote:
On 30/08/2022 21:08, Ivaylo Dimitrov wrote:
flags &= ~OMAP_BO_TILED_MASK;
flags |= 0x0008;
flags |= OMAP_BO_WC;
bo = omap_bo_new(dev, size, flags);
As you can see we use 0x0008 (OMAP_BO_MEM_CONTIG) u
On 30/08/2022 21:08, Ivaylo Dimitrov wrote:
flags &= ~OMAP_BO_TILED_MASK;
flags |= 0x0008;
flags |= OMAP_BO_WC;
bo = omap_bo_new(dev, size, flags);
As you can see we use 0x0008 (OMAP_BO_MEM_CONTIG) unconditionally.
This was a hack added since even no
Hi,
On 30.08.22 г. 18:08 ч., Yongqin Liu wrote:
HI, Andrew
Thanks a lot for the information! And great to have you here!
Hi, Ivaylo
With the code provided by Andrew, could you please help give suggestions
on how to modify it in the gralloc lib side?
to add the OMAP_BO_SCANOUT flag unconditio
HI, Andrew
Thanks a lot for the information! And great to have you here!
Hi, Ivaylo
With the code provided by Andrew, could you please help give suggestions
on how to modify it in the gralloc lib side?
to add the OMAP_BO_SCANOUT flag unconditionally as OMAP_BO_MEM_CONTIG?
Thanks,
Yongqin Liu
Hi,
On 29.08.22 г. 5:51 ч., Yongqin Liu wrote:
Hi, Ivaylo
Sorry for the late response, and Thanks very much for the detailed explanations!
On Thu, 18 Aug 2022 at 18:23, Ivaylo Dimitrov
wrote:
Hi,
On 17.08.22 г. 7:52 ч., Yongqin Liu wrote:
Hi, Ivaylo
On Mon, 15 Aug 2022 at 14:23, Ivaylo
Hi, Ivaylo
Sorry for the late response, and Thanks very much for the detailed explanations!
On Thu, 18 Aug 2022 at 18:23, Ivaylo Dimitrov
wrote:
>
> Hi,
>
> On 17.08.22 г. 7:52 ч., Yongqin Liu wrote:
> > Hi, Ivaylo
> >
> > On Mon, 15 Aug 2022 at 14:23, Ivaylo Dimitrov
> > wrote:
> >>
> >> Hi Li
Hi,
On 17.08.22 г. 7:52 ч., Yongqin Liu wrote:
Hi, Ivaylo
On Mon, 15 Aug 2022 at 14:23, Ivaylo Dimitrov
wrote:
Hi Liu,
On 14.08.22 г. 17:27 ч., Yongqin Liu wrote:
Hi, IvayIo
Thanks very much for the reply!
On Sat, 13 Aug 2022 at 14:58, Ivaylo Dimitrov
wrote:
Hi Liu,
On 12.08.22 г. 7:
Hi, Ivaylo
On Mon, 15 Aug 2022 at 14:23, Ivaylo Dimitrov
wrote:
>
> Hi Liu,
>
> On 14.08.22 г. 17:27 ч., Yongqin Liu wrote:
> > Hi, IvayIo
> >
> > Thanks very much for the reply!
> >
> > On Sat, 13 Aug 2022 at 14:58, Ivaylo Dimitrov
> > wrote:
> >>
> >> Hi Liu,
> >>
> >> On 12.08.22 г. 7:35 ч.,
Hi Liu,
On 14.08.22 г. 17:27 ч., Yongqin Liu wrote:
Hi, IvayIo
Thanks very much for the reply!
On Sat, 13 Aug 2022 at 14:58, Ivaylo Dimitrov
wrote:
Hi Liu,
On 12.08.22 г. 7:35 ч., Yongqin Liu wrote:
Hi, Ivaylo, Tomi
We have one X15 Android AOSP master build, it could not have the home
sc
Hi, IvayIo
Thanks very much for the reply!
On Sat, 13 Aug 2022 at 14:58, Ivaylo Dimitrov
wrote:
>
> Hi Liu,
>
> On 12.08.22 г. 7:35 ч., Yongqin Liu wrote:
> > Hi, Ivaylo, Tomi
> >
> > We have one X15 Android AOSP master build, it could not have the home
> > screen displayed
> > on the hdmi monit
Hi Liu,
On 12.08.22 г. 7:35 ч., Yongqin Liu wrote:
Hi, Ivaylo, Tomi
We have one X15 Android AOSP master build, it could not have the home
screen displayed
on the hdmi monitor connected with this change, with the following
message printed on the serial console
[ 607.404205] omapdrm omapdrm
Hi, Ivaylo, Tomi
We have one X15 Android AOSP master build, it could not have the home
screen displayed
on the hdmi monitor connected with this change, with the following
message printed on the serial console
[ 607.404205] omapdrm omapdrm.0: Failed to setup plane plane-0
[ 607.410522] om
On 17.02.22 г. 14:46 ч., Tomi Valkeinen wrote:
Hi,
On 19/01/2022 12:23, Ivaylo Dimitrov wrote:
On devices with DMM, all allocations are done through either DMM or
TILER.
DMM/TILER being a limited resource means that such allocations will start
to fail before actual free memory is exhausted.
Hi,
On 19/01/2022 12:23, Ivaylo Dimitrov wrote:
On devices with DMM, all allocations are done through either DMM or TILER.
DMM/TILER being a limited resource means that such allocations will start
to fail before actual free memory is exhausted. What is even worse is that
with time DMM/TILER spac
On devices with DMM, all allocations are done through either DMM or TILER.
DMM/TILER being a limited resource means that such allocations will start
to fail before actual free memory is exhausted. What is even worse is that
with time DMM/TILER space gets fragmented to the point that even if we have
24 matches
Mail list logo
