Dear All,
What is the most effective/optimal/recommended way to wait for
DRM_MODE_CONNECTED status?
This is to make sure when disply manager (uses drm apis) starts and if it
do not get the DRM_MODE_CONNECTED status as some dependent driver is still
loading and setting up (e.g. serializer driver)
Hi Nasser,
No, problem was not solved and I left it as priorities of my work changed.
Best Regards,
Vikash
On Mon, May 27, 2019 at 3:08 AM nasser afshin
wrote:
> Hi Vikash,
>
> As it's been quite a while, I want to know if the problem is solved
> successfully
> If so, could you please shed som
On Thu, Jul 13, 2017 at 7:20 PM, Daniel Vetter wrote:
> On Thu, Jul 13, 2017 at 3:33 PM, Vikas Patil wrote:
>> Dear All,
>>
>> I am looking for an solution to have early smooth splashscreen on the
>> Linux system with Weston and drm-backend.
>>
>> I trie
Dear All,
I am looking for an solution to have early smooth splashscreen on the
Linux system with Weston and drm-backend.
I tried showing splashscreen using Linux logo and fbcon Linux features
but it is not smooth as when system boots logo gets displayed via
kernel and as the Weston starts
I see
On Mon, Sep 26, 2016 at 6:11 PM, Tomi Valkeinen
wrote:
> On 26/09/16 15:34, Vikas Patil wrote:
>
>> Will check once I get display working, for time being I think it shows
>> connected with the hack I mentioned. I was taking about supporting
>> "interlace" via
On Mon, Sep 26, 2016 at 6:00 PM, Tomi Valkeinen
wrote:
>
>
> On 26/09/16 15:25, Vikas Patil wrote:
>> On Fri, Sep 23, 2016 at 4:30 PM, Tomi Valkeinen
>> wrote:
>>> On 22/09/16 16:22, Vikas Patil wrote:
>>>
>>>> Could you help me to understand
On Fri, Sep 23, 2016 at 4:30 PM, Tomi Valkeinen
wrote:
> On 22/09/16 16:22, Vikas Patil wrote:
>
>> Could you help me to understand if I could use âinterlace=falseâ?
>> ADV7393 seems to be supporting non-interlaced mode. From datasheet:
>> âThe ADV7390/ADV7391/ADV73
On Fri, Sep 23, 2016 at 4:32 PM, Tomi Valkeinen
wrote:
> On 23/09/16 13:08, Vikas Patil wrote:
>> Hi Tomi,
>>
>> I added the missing check for "OMAP_DISPLAY_TYPE_VENC" in function
>> omap_connector_detect @ gpu/drm/omapdrm/omap_connector.c and now
>> m
display. I think I need to understand about what display
timing I could use as interlace doesn't seems to be supported as I
mentioned above.
Could you please comment on this?
Thanks & Regards,
Vikash
On Thu, Sep 22, 2016 at 6:52 PM, Vikas Patil wrote:
> Hi Tomi,
>
>
> Now with
23 PM, Tomi Valkeinen
wrote:
>
>
> On 15/09/16 12:44, Vikas Patil wrote:
>> On Wed, Sep 14, 2016 at 3:04 PM, Tomi Valkeinen
>> wrote:
>>>
>>>
>>> On 13/09/16 16:13, Vikas Patil wrote:
>>>> Thanks Tomi for quick comment.
>>>>
>
On Thu, Sep 15, 2016 at 3:23 PM, Tomi Valkeinen
wrote:
>
>
> On 15/09/16 12:44, Vikas Patil wrote:
>> On Wed, Sep 14, 2016 at 3:04 PM, Tomi Valkeinen
>> wrote:
>>>
>>>
>>> On 13/09/16 16:13, Vikas Patil wrote:
>>>> Thanks Tomi for q
On Wed, Sep 14, 2016 at 3:04 PM, Tomi Valkeinen
wrote:
>
>
> On 13/09/16 16:13, Vikas Patil wrote:
>> Thanks Tomi for quick comment.
>>
>> I am thinking to base adv7393 driver on
>> "drivers\gpu\drm\omapdrm\displays\encoder-tc358768.c" as I don&#x
ng to open device 'rockchip'...failed
trying to open device 'atmel-hlcdc'...failed
trying to open device 'fsl-dcu-drm'...failed
trying to open device 'vc4'...failed
no device found
root at dra7xx-evm:~# kmscube
trying to load module omapdrm...failed.
trying to
with adv7393 driver?
Thanks & Regards,
Vikash
On Mon, Sep 12, 2016 at 5:59 PM, Vikas Patil wrote:
> Dear All,
>
> I am trying to understand difference between "DRM Encoder slave
> driver" and "DRM bridge driver" as I need to write one for ADV7393
> Video
Dear All,
I am trying to understand difference between "DRM Encoder slave
driver" and "DRM bridge driver" as I need to write one for ADV7393
Video Encoder Chip for the custom target
based on DRA74x having following display connection.
VOUT1 --> ADV7393 --> CVBS Out(ADV7393 is on I2C)
Could a
gem_put_paddr(buf);
} else {
if (bPhysContig) {
omap_gem_put_paddr(buf);
} else {
omap_gem_put_pages(buf);
}
}
}
#endif /* SUPPORT_DRI_DRM_EXTERNAL */
return err;
}
Thanks & Regards,
Vikash
On Mon, Dec 1, 2
Hi,
I am running camera capture application (based on omap iss, v4l2,
videobuf2-dma-contig, x11, gles2) on customized OMAP5 board with 3.8 kernel
and rootfs based on GLSDK 6.04.00.02. However within 12 to 30 minutes it
crashes with following trace.
I have reverted Link 1 patch from omap_gem.c and
.-rc5 linux)
Regards,
Vikash
On Fri, May 16, 2014 at 2:23 PM, Tomi Valkeinen wrote:
> On 13/05/14 09:26, Vikas Patil wrote:
> > Hi Tomi,
> >
> >>That driver cannot be used with omapdrm, which uses omapdss. There's no
> > TDF19988 driver for omapdss (at least i
cture and effort to backport some of the things, write new driver
> fro TDF19988 and make DPI interface working for our platform for someone
> like me who has just started working on DSS/Display.
>
> Regards,
> Vikash
>
> On Mon, May 12, 2014 at 5:28 PM, Tomi Valkeinen t
on DSS/Display.
Regards,
Vikash
On Mon, May 12, 2014 at 5:28 PM, Tomi Valkeinen wrote:
> On 12/05/14 14:33, Vikas Patil wrote:
> > Hi,
> >
> > Re-posting as previous posting was rejected due to length.
> >
> > Forgot to mention, DPI pins are connected to TDF1
driver itself? Could you please give
some inputs, how should I proceed further to adding support for TDF19988
for which the input is coming from DPI interface?
Thanks & Regards,
Vikash
On Mon, May 12, 2014 at 2:11 PM, Vikas Patil wrote:
> Hi Tomi,
>
> How could I confirm for OMAP
kernel\arch\arm\mach-omap2?
Regards,
Vikash
On Fri, May 9, 2014 at 4:49 PM, Tomi Valkeinen wrote:
> On 08/05/14 13:07, Vikas Patil wrote:
> > Hi,
> >
> > I am working on to enable the second display output for customized OMAP5
> > based platform and linux 3.4.25. Fir
bug fixes in the DRM driver.
>
>
>
> I believe Wayland 1.4.0 should work as-is with this release on J6.
>
>
>
> Regards,
>
> Anand Balagopalakrishnan
>
> Systems Architect
>
> Automotive Infotainment
>
> Texas Instruments
> -----
Hi,
HDMI display is not showing anything (i.e. shows black ) while running
Wayland/Weston 1.4.0 with drm-backend.so on linux 3.8.13 which is
customized for Jacinto 6 based platform.
- Although weston seem to be running
- I am able to run the kmscube and it is showing cube on display.
- I am able
ark wrote:
> On Wed, Apr 2, 2014 at 8:23 AM, Vikas Patil wrote:
> > Hi,
> > I am seeing following kernel backtrace on J6 with linux 3.8.13 when
> trying
> > to start IVI LM service. Before starting this I started the X11 and run
> some
> > GLES2/X11 based tests su
Hi,
I am seeing following kernel backtrace on J6 with linux 3.8.13 when trying
to start IVI LM service. Before starting this I started the X11 and run
some GLES2/X11 based tests successfully.
The same binaries and my graphics driver are working fine on OMAP5 and
linux 3.4.25. Is this some known BU
Hi All,
While running one of the map application I am seeing following crash in
omapdrm_pvr. Is this known issue? or any clues to debug this would be very
much helpful to me.
[ 51.095336] Unable to handle kernel paging request at virtual address
f297d000
[ 51.102996] pgd = e7ac4000
[ 51.1
Hi All,
I am running the webkit on custom linux based on 3.4.25 kernel on omap5.
However it is failing to map some memory using drm_gem_mmap() at following
code.
if (map->size < vma->vm_end - vma->vm_start) {
ret = -EINVAL;
g
Hi All,
Please excuse me if this is not the right place to ask this question. If
not please point me where should I ask?
Is it possible to render to framebuffer memory or some allocated memory
with graphics stack which uses DRI/DRM and Xserver and platform without any
display port or monitor atta
29 matches
Mail list logo
