[Dev] Tizen bring-up - DRM

Shahul Ahamed Shaik shahulahamed.shaik at incubesol.com
Thu Dec 17 09:50:52 GMT 2015

Hi Inki Dae,

1. Our SoC is MIPS based. Do the limitations still exist with Linux framebuffer?

2. Can you be a little more specific about bypassing the DRM and use Linux framebuffer directly? Native window system is X and it uses DRM at the backend.

sk shahul

Message: 2
Date: Wed, 16 Dec 2015 20:46:16 +0900
From: Inki Dae <inki.dae at samsung.com>
To: dev at lists.tizen.org
Subject: Re: [Dev] Tizen bring-up - DRM
Message-ID: <56714F08.1070609 at samsung.com>
Content-Type: text/plain; charset=UTF-8

Hello Shahul,

2015? 12? 16? 18:33? Shahul Ahamed Shaik ?(?) ? ?:
> Dear All,
>     We are trying to bring-up Tizen on our platform. Android is running on our platform and we are using FrameBuffer for rendering. 
>     Is the use of DRM compulsory for Tizen bring-up and graphics rendering?

It's not compulsory but we recommend to use DRM instead of Linux framebuffer because Linux framebuffer not only has many limitations for advanced ARM SoC but also doesn't support the integrated buffer manager.

> If not, what is the way to bypass DRM and use FrameBuffer directly to achieve Rendering, and what are the advantages/disadvantages associated with the same? 
>     Please let me know.

It would be dependent on what backend - Linux framebuffer or DRM - is used by native window system such as X or Wayland server.
The advantages with DRM is that Tizen platform is DRM-friendly so it is easy to port Tizen platform to your kernel, including easy-to-manage DMA buffer and many hardware features available.

Inki Dae

> Thanks in Advance.
> Skshahul.
> _______________________________________________
> Dev mailing list
> Dev at lists.tizen.org
> https://lists.tizen.org/listinfo/dev

More information about the Dev mailing list