[Dev] References images that contains libtbm-dumb and libtdm-drm

Boram Park boram1288.park at samsung.com
Mon Dec 18 07:08:27 UTC 2017

It seems libtbm-dumb and libtdm-drm should work fine as you said.
But, sometimes we face the unexpected problem when testing new target 
Could you check if any TBM or TDM error logs are in your board? you can 
check them with "dlogutil TBM" and "dlogutil TDM".

On 2017년 12월 18일 13:06, Hee-cheol Yang wrote:
> Hello, thank you very much for your mail.
> I am using beaglebone black singleboard computer, which is based on 
> TI's AM335x SOC.
> This board supports Linux mainline kernel wirh board-specific patches 
> and my kernel version is mainline 4.4
> When I read your wiki section, I thought that I don't need to port the 
> backends because the libtbm-dumb and libtdm-drm are for the modules to 
> support the platforms which provieds standard drm interfaces like my 
> board.
> Anyway, thanks a lot your help and I will check whether ENABLE_PP is 
> set or not in my kernel.
> Best regards.
> Heecheol Yang
> 삼성 갤럭시 스마트폰에서 보냈습니다.
> -------- 원본 이메일 --------
> 보낸 사람: Inki Dae <inki.dae at samsung.com>
> 날짜: 17/12/18 오전 10:08 (GMT+09:00)
> 받은 사람: myungjoo.ham at samsung.com, Hee-cheol Yang 
> <heecheol.yang at outlook.com>, dev at lists.tizen.org
> 제목: Re: [Dev]  References images that contains libtbm-dumb and 
> libtdm-drm
> Hi Hee-cheol,
> 2017년 12월 18일 09:35에 MyungJoo Ham 이(가) 쓴 글:
> >> Hello,first of all, thank you for all your kind advices.
> >>
> >> I disabled suspend feature first, and my board doesn't get freeze. 
> I will find what make it get freeze later.
> >>
> >> Anyway, now I am struggling to enable the Tizen UI on my HDMI 
> Monitor. It seems that I need to port libtbm and libtdm backends 
> because my reference image is built  with exynos backends.
> >>
> >> As my CPU supports DRM, I am trying to replace them with 
> libtbm-dumb and libtdm-drm. But it is hard to find reference images 
> because most images in download.tizen.org uses its own backends  for 
> the SOC that they are running upon.
> >>
> >> So could you tell me if is there any reference board or sample 
> image that runs upon drm?
> TBM and TDM backend are Tizen HAL modules dependent on Hardware and 
> its kernel. So you would need to implement these HALs - TBM and TDM 
> backends. You can refer to below porting guide.
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.tizen.org%2FTizen_3.0_Porting_Guide&data=02%7C01%7C%7Ce93a83180cee4b804b2208d545b3dc0c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636491561144249374&sdata=Qms2ux91lq%2FbIs4YYQ3Pev4F%2FIyN5%2BY4yaEYmypSh4A%3D&reserved=0
> If your board uses mainline kernel which never include in-house code 
> then you could use libtbm-dump and even libtdm-drm(by disabling 
> ENABLE_PP config) packages below by installing them on your target.
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdownload.tizen.org%2Freleases%2Fmilestone%2Ftizen%2F4.0.m1%2Ftizen-unified_20170529.1%2Frepos%2Fstandard%2Fpackages%2Farmv7l%2F&data=02%7C01%7C%7Ce93a83180cee4b804b2208d545b3dc0c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636491561144249374&sdata=P%2F5eu6jc5SdyiuFRKp9YwD0Fui4DV4s%2FsT3hTDWE6TQ%3D&reserved=0
> What hardware and Linux kernels are you using? If you give me more 
> details about your env. then I may give you more advices.
> Thanks,
> Inki Dae
> >>
> >> Best regards
> >> Heecheol Yang
> >
> > I guess that any Exynos-based and x86/x64-based references would be 
> using DRM. There would be Non-Exynos ARM boards that use DRM as well, 
> but I cannot be sure which supports DRM.
> >
> > CC: Inki Dae: could you please give him some hints on this matter? 
> I'm not that well-aware of display-related technologies or recent 
> Tizen changes.
> >
> >
> > Cheers,
> > MyungJoo
> >
> >
> _______________________________________________
> Dev mailing list
> Dev at lists.tizen.org
> https://lists.tizen.org/listinfo/dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.tizen.org/pipermail/dev/attachments/20171218/390bd48d/attachment-0001.html>

More information about the Dev mailing list