Re: [Dev] Tizen source for odroid ux

2015-12-09 Thread Inki Dae
Hi Shahul,

2015년 12월 09일 21:13에 Shahul Ahamed Shaik 이(가) 쓴 글:
> 
> 
> Hi All,
> 
> I am planning to bring up tizen 2.3 wearable profile on our platform. I took 
> ODROID-XU as reference platform .
> 
> Can anyone please let me know kernel source/configuration for ODROID-XU. Also 
> would there any tizen code changes between ODROID-U3 and ODROID-XU.

You can refer to below kernel repository,
https://git.tizen.org/cgit/platform/kernel/linux-exynos.git/
branch name : tizen

And there is no any change between ODROID-U3 and XU3 even XU4 so you can use 
odroidxu3_defconfig file for all of them.

Thanks,
Inki Dae

> 
> Thanks in Advance 
> 
> Regards,
> Sk shahul.
> ___
> Dev mailing list
> Dev@lists.tizen.org
> https://lists.tizen.org/listinfo/dev
> 
> 
___
Dev mailing list
Dev@lists.tizen.org
https://lists.tizen.org/listinfo/dev


Re: [Dev] Tizen source for odroid ux

2015-12-09 Thread Inki Dae
Hi Shahul,

Below is additional comment,


2015년 12월 10일 15:03에 Inki Dae 이(가) 쓴 글:
> Hi Shahul,
> 
> 2015년 12월 09일 21:13에 Shahul Ahamed Shaik 이(가) 쓴 글:
>>
>>
>> Hi All,
>>
>> I am planning to bring up tizen 2.3 wearable profile on our platform. I took 
>> ODROID-XU as reference platform .
>>
>> Can anyone please let me know kernel source/configuration for ODROID-XU. 
>> Also would there any tizen code changes between ODROID-U3 and ODROID-XU.

ODROID-XU board is much different with U3, XU3 and XU4, especially 3D GPU so 
below kernel wouldn't support the ODROID-XU board.
If you want to use our kernel for ODROID-XU board, you would need to port board 
specific part and some portion of Exynos5410 SoC maybe.
So how about using one of other boards, ODROID-U3/XU3/XU4 which are supported 
by our kernel?

Thanks,
Inki Dae

> 
> You can refer to below kernel repository,
> https://git.tizen.org/cgit/platform/kernel/linux-exynos.git/
> branch name : tizen
> 
> And there is no any change between ODROID-U3 and XU3 even XU4 so you can use 
> odroidxu3_defconfig file for all of them.
> 
> Thanks,
> Inki Dae
> 
>>
>> Thanks in Advance 
>>
>> Regards,
>> Sk shahul.
>> ___
>> Dev mailing list
>> Dev@lists.tizen.org
>> https://lists.tizen.org/listinfo/dev
>>
>>
___
Dev mailing list
Dev@lists.tizen.org
https://lists.tizen.org/listinfo/dev


Re: [Dev] Tizen BUilding for Odroid u3

2015-12-10 Thread Inki Dae
CCing Mr. Dug-In Lyu

Hi Shahul,

I think Mr. Lyu can give you some guide for it.

To Mr. Lyu,
Could you please give him some guide about how to compile Tizen 2.3 werable 
profile?

Thanks,
Inki Dae

2015년 12월 10일 22:04에 Shahul Ahamed Shaik 이(가) 쓴 글:
> 
> 
> Hi  Inki Dae,
> 
> I downloaded tizen 2.3 wearable profile source. Please let me know how to 
> compile it for odroid u3 platform.
> 
> Thanks In Advance.
> 
> Regards,
> Sk shahul.
> 
> - Original Message -
> From: "Shahul Ahamed Shaik" 
> To: "inki dae" 
> Cc: dev@lists.tizen.org
> Sent: Thursday, December 10, 2015 5:41:56 PM
> Subject: Re: Dev Digest, Vol 28, Issue 10
> 
> Hi  Inki Dae,
> 
> Thanks for reply.
> 
> We are ordering odroid u3 platform.
> 
> 
> 
> Regards,
> Sk shahul.
> 
> - Original Message -
> From: dev-requ...@lists.tizen.org
> To: dev@lists.tizen.org
> Sent: Thursday, December 10, 2015 5:30:01 PM
> Subject: Dev Digest, Vol 28, Issue 10
> 
> Send Dev mailing list submissions to
>   dev@lists.tizen.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>   https://lists.tizen.org/listinfo/dev
> or, via email, send a message with subject or body 'help' to
>   dev-requ...@lists.tizen.org
> 
> You can reach the person managing the list at
>   dev-ow...@lists.tizen.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Dev digest..."
> 
> 
> Today's Topics:
> 
>1.  Tizen source for odroid ux (Shahul Ahamed Shaik)
>2. Re:  Tizen source for odroid ux (Inki Dae)
>3. Re:  Tizen source for odroid ux (Inki Dae)
> 
> 
> --
> 
> Message: 1
> Date: Wed, 9 Dec 2015 17:43:13 +0530 (IST)
> From: Shahul Ahamed Shaik 
> To: dev@lists.tizen.org
> Subject: [Dev] Tizen source for odroid ux
> Message-ID: <14510881.92.1449662897550.JavaMail.ashahul@skshahul>
> Content-Type: text/plain; charset=utf-8
> 
> 
> 
> Hi All,
> 
> I am planning to bring up tizen 2.3 wearable profile on our platform. I took 
> ODROID-XU as reference platform .
> 
> Can anyone please let me know kernel source/configuration for ODROID-XU. Also 
> would there any tizen code changes between ODROID-U3 and ODROID-XU.
> 
> Thanks in Advance 
> 
> Regards,
> Sk shahul.
> 
> 
> --
> 
> Message: 2
> Date: Thu, 10 Dec 2015 15:03:40 +0900
> From: Inki Dae 
> To: dev@lists.tizen.org
> Subject: Re: [Dev] Tizen source for odroid ux
> Message-ID: <566915bc.6060...@samsung.com>
> Content-Type: text/plain; charset=UTF-8
> 
> Hi Shahul,
> 
> 2015? 12? 09? 21:13? Shahul Ahamed Shaik ?(?) ? ?:
>>
>>
>> Hi All,
>>
>> I am planning to bring up tizen 2.3 wearable profile on our platform. I took 
>> ODROID-XU as reference platform .
>>
>> Can anyone please let me know kernel source/configuration for ODROID-XU. 
>> Also would there any tizen code changes between ODROID-U3 and ODROID-XU.
> 
> You can refer to below kernel repository,
> https://git.tizen.org/cgit/platform/kernel/linux-exynos.git/
> branch name : tizen
> 
> And there is no any change between ODROID-U3 and XU3 even XU4 so you can use 
> odroidxu3_defconfig file for all of them.
> 
> Thanks,
> Inki Dae
> 
>>
>> Thanks in Advance 
>>
>> Regards,
>> Sk shahul.
>> _______
>> Dev mailing list
>> Dev@lists.tizen.org
>> https://lists.tizen.org/listinfo/dev
>>
>>
> 
> 
> --
> 
> Message: 3
> Date: Thu, 10 Dec 2015 15:22:06 +0900
> From: Inki Dae 
> To: dev@lists.tizen.org
> Subject: Re: [Dev] Tizen source for odroid ux
> Message-ID: <56691a0e.6080...@samsung.com>
> Content-Type: text/plain; charset=utf-8
> 
> Hi Shahul,
> 
> Below is additional comment,
> 
> 
> 2015? 12? 10? 15:03? Inki Dae ?(?) ? ?:
>> Hi Shahul,
>>
>> 2015? 12? 09? 21:13? Shahul Ahamed Shaik ?(?) ? ?:
>>>
>>>
>>> Hi All,
>>>
>>> I am planning to bring up tizen 2.3 wearable profile on our platform. I 
>>> took ODROID-XU as reference platform .
>>>
>>> Can anyone please let me know kernel source/configuration for ODROID-XU. 
>>> Also would there any tizen code changes between ODROID-U3 and ODROID-XU.
> 
> ODROID-XU board is much different with U3, XU3 and XU4, especially 3D GPU so 
> below kernel wouldn't support the ODROID-XU board.
> If you want to use 

Re: [Dev] Tizen bring-up - DRM

2015-12-16 Thread Inki Dae
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.

Thanks,
Inki Dae

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


Re: [Dev] Tizen bring-up - DRM

2015-12-17 Thread Inki Dae
Hi Shahul,

2015년 12월 17일 18:50에 Shahul Ahamed Shaik 이(가) 쓴 글:
> 
> Hi Inki Dae,
> 
> 1. Our SoC is MIPS based. Do the limitations still exist with Linux 
> framebuffer?

Linux framebuffer has the limitations not MIPS. Linux mainline had already 
stopped new feature update for Linux framebuffer, which means Linux mainline 
will move to DRM gradually.
Actually, most ARM SoC started to move to DRM already.

> 
> 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.

Before that, Could I ask you about why you want to bypass the DRM although you 
already has the native window system which provides the DRM backend?

AFAIK, you can use X server with FB backend by building it with proper 
configuration - please, check X server build document.
However, the problem is that you have to implement a buffer manager as a TBM 
(Tizen Buffer Manager) backend[1] because all X clients allocate DMA buffer 
through TBM[2] interfaces.
If you use DRM, then DRM could be the backend. If not so - you use FB, then 
other buffer manager would be required for it such as ION[3] or other vendor 
specific one.

[1] 
https://review.tizen.org/git/?p=platform/adaptation/samsung_exynos/libtbm-exynos4412.git;a=shortlog;h=refs/heads/tizen
[2] 
https://review.tizen.org/git/?p=platform/core/uifw/libtbm.git;a=shortlog;h=refs/heads/tizen
[3] https://lwn.net/Articles/480055/

Thanks,
Inki Dae

> 
> 
> 
> Thanks,
> sk shahul
> 
> 
> Message: 2
> Date: Wed, 16 Dec 2015 20:46:16 +0900
> From: Inki Dae 
> To: dev@lists.tizen.org
> Subject: Re: [Dev] Tizen bring-up - DRM
> Message-ID: <56714f08.1070...@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.
> 
> Thanks,
> Inki Dae
> 
>>
>> Thanks in Advance.
>> Skshahul.
>> ___
>> Dev mailing list
>> Dev@lists.tizen.org
>> https://lists.tizen.org/listinfo/dev
>>
>>
> 
> 
___
Dev mailing list
Dev@lists.tizen.org
https://lists.tizen.org/listinfo/dev


Re: [Dev] Tizen common profile porting on new h/w

2016-03-09 Thread Inki Dae
Hi,

2016년 03월 10일 12:31에 PINTU KUMAR 이(가) 쓴 글:
> Hi,
> 
> I wanted to port Tizen platform in one of the ARM based open hardware such as 
> BeagleBone, Raspberry Pi.
> So, I thought, I will start with the Tizen 3.0 common profile and create my 
> own custom profile.
> 
> But, when I see, in http://download.tizen.org/ there are so many Tizen images 
> available.
> I am really confused which one to choose. There is no clear documentation 
> which explains about it.
> 
> So, I tried one of the images from:
> http://download.tizen.org/snapshots/tizen/common/ 
> http://download.tizen.org/snapshots/tizen/common/latest/images/arm-wayland/
> http://download.tizen.org/snapshots/tizen/common/latest/images/arm-wayland/common-wayland-3parts-armv7l-odroidu3/
>  (tizen-common_20160309.1_common-wayland-3parts-armv7l-odroidu3.tar.gz)
> 
> Because, I just need the rootfs.img, system-data.img, user.img  (only the 
> Tizen platform).
> I already have my own boot loader and Linux Kernel  (Raspberry Pi).
> 
> Now, my questions are as follows:
> 
> 1) Am I using the correct image to create a new profile? Will it work for me?
> 
> 2) When I try to boot the image on Raspberry Pi, I am not able to get the 
> Login prompt on my virtual terminal (tty1).
> Please let me know what changes are required to get the login prompt?
> 
> Note: I have made the required changes in Kernel (as per Tizen) but disabled 
> DRM (as I am not interested in Display).
> Like, I have already enabled SMACK in kernel.
> 
> 3) If I am not using the correct image, please point me to the right image, 
> to start with.
> 

I believe below link could provide what you need for Tizen porting,
https://wiki.tizen.org/wiki/RaspberryPi

Thanks,
Inki Dae

> 
> 
> 
> Regards,
> Pintu
> ___
> Dev mailing list
> Dev@lists.tizen.org
> https://lists.tizen.org/listinfo/dev
> 
> 
___
Dev mailing list
Dev@lists.tizen.org
https://lists.tizen.org/listinfo/dev


Re: [Dev] Tizen common profile porting on new h/w

2016-03-09 Thread Inki Dae
Dear PINTU,

2016년 03월 10일 14:09에 PINTU KUMAR 이(가) 쓴 글:
> Dear Mr. Inki-Dae,
> 
> Thank you very much for your reply.
> 
> Yes, I am already aware about Tizen Yocto image for raspberry pi. I have 
> already 
> tried it and I can boot successfully till the desktop/display screen.
> 
> Due to the firewall restrictions (and PC space limits), I cannot build the 
> Yocto 
> image.
> 
> So, I tried with the pre-build images, but, I am not getting any output on 
> the 
> virtual terminal by connecting an HDMI to my computer monitor (tty1).
> 
> Unfortunately, I don't have a serial UART cable right now (for raspberry pi), 
> so 
> I haven't tried it yet using UART.

Really bad news.

I think there must be no problem to enter console using one of them below 
images,
http://download.tizen.org/snapshots/tizen/common/
http://download.tizen.org/snapshots/tizen/common/latest/images/arm-wayland/
http://download.tizen.org/snapshots/tizen/common/latest/images/arm-wayland/common-wayland-3parts-armv7l-odroidu3/
 

Could you share the kernel log with us after you are ready for UART?
With the log, we could know what happens in there and give you some help.

Thanks,
Inki Dae

> 
> Also, at this moment, I don't want the graphical display (for my use case), 
> so I 
> just want to drop it to console and execute some commands.
> 
> Moreover, I wanted to start things from scratch using the existing Tizen 
> images 
> either from common profile or others.
> 
> Please let me know which image to choose.
> 
> Also, let me know, how to enable virtual console on Tizen (using systemd?)
> 
> Thank You!
> With Regards,
> Pintu Kumar
> 
> --- *Original Message* ---
> 
> *Sender* : In-Ki Dae S5/Senior Engineer/Tizen Platform 
> Lab./Samsung Electronics
> 
> *Date* : Mar 10, 2016 09:47 (GMT+05:30)
> 
> *Title* : Re: [Dev] Tizen common profile porting on new h/w
> 
> Hi,
> 
> 2016년 03월 10일 12:31에 PINTU KUMAR 이(가) 쓴 글:
>  > Hi,
>  >
>  > I wanted to port Tizen platform in one of the ARM based open hardware such 
> as 
> BeagleBone, Raspberry Pi.
>  > So, I thought, I will start with the Tizen 3.0 common profile and create 
> my 
> own custom profile.
>  >
>  > But, when I see, in http://download.tizen.org/ there are so many Tizen 
> images 
> available.
>  > I am really confused which one to choose. There is no clear documentation 
> which explains about it.
>  >
>  > So, I tried one of the images from:
>  > http://download.tizen.org/snapshots/tizen/common/
>  > http://download.tizen.org/snapshots/tizen/common/latest/images/arm-wayland/
>  > 
> http://download.tizen.org/snapshots/tizen/common/latest/images/arm-wayland/common-wayland-3parts-armv7l-odroidu3/
>  
> (tizen-common_20160309.1_common-wayland-3parts-armv7l-odroidu3.tar.gz)
>  >
>  > Because, I just need the rootfs.img, system-data.img, user.img  (only the 
> Tizen platform).
>  > I already have my own boot loader and Linux Kernel  (Raspberry Pi).
>  >
>  > Now, my questions are as follows:
>  >
>  > 1) Am I using the correct image to create a new profile? Will it work for 
> me?
>  >
>  > 2) When I try to boot the image on Raspberry Pi, I am not able to get the 
> Login prompt on my virtual terminal (tty1).
>  > Please let me know what changes are required to get the login prompt?
>  >
>  > Note: I have made the required changes in Kernel (as per Tizen) but 
> disabled 
> DRM (as I am not interested in Display).
>  > Like, I have already enabled SMACK in kernel.
>  >
>  > 3) If I am not using the correct image, please point me to the right 
> image, 
> to start with.
>  >
> 
> I believe below link could provide what you need for Tizen porting,
> https://wiki.tizen.org/wiki/RaspberryPi
> 
> Thanks,
> Inki Dae
> 
>  >
>  >
>  >
>  > Regards,
>  > Pintu
>  > ___
>  > Dev mailing list
>  > Dev@lists.tizen.org
>  > https://lists.tizen.org/listinfo/dev
>  >
>  >
> 
___
Dev mailing list
Dev@lists.tizen.org
https://lists.tizen.org/listinfo/dev


Re: [Dev] Build errors of TM1 Kernel and its patch.

2016-10-14 Thread Inki Dae
address.c
> 
> index fafedd8..f6aa84d 100644
> 
> --- a/arch/arm/kernel/return_address.c
> 
> +++ b/arch/arm/kernel/return_address.c
> 
> @@ -63,11 +63,6 @@ void *return_address(unsigned int level)
> 
> #warning "TODO: return_address should use unwind tables"
> 
> #endif
> 
>  
> 
> -void *return_address(unsigned int level)
> 
> -{
> 
> -   return NULL;
> 
> -}
> 
> -
> 
> #endif /* if defined(CONFIG_FRAME_POINTER) && !defined(CONFIG_ARM_UNWIND) /
> else */
> 
>  
> 
> EXPORT_SYMBOL_GPL(return_address);
> 
> diff --git a/drivers/cpufreq/cpufreq_sprdemand.c
> b/drivers/cpufreq/cpufreq_sprdemand.c
> 
> index 23f9f09..4a4bc77 100644
> 
> --- a/drivers/cpufreq/cpufreq_sprdemand.c
> 
> +++ b/drivers/cpufreq/cpufreq_sprdemand.c
> 
> @@ -98,12 +98,14 @@ struct work_struct unplug_all_work;
> 
> static int cpu_num_limit_temp;
> 
> static void sprd_thm_unplug_cpu(struct work_struct *work);
> 
>  
> 
> +#if 0
> 
> static DEFINE_PER_CPU(struct unplug_work_info, uwi);
> 
>  
> 
> static DEFINE_SPINLOCK(g_lock);
> 
> static unsigned int percpu_total_load[CONFIG_NR_CPUS] = {0};
> 
> static unsigned int percpu_check_count[CONFIG_NR_CPUS] = {0};
> 
> static int cpu_score = 0;
> 
> +#endif

Also will check it but this way, using #if 0, is not good.

Thanks for report,
Inki Dae

> 
>  
> 
> /* FIXME. default touch boost is enabled */
> 
> #define CONFIG_TOUCH_BOOST
> 
> 
> 
> 
> ___
> Dev mailing list
> Dev@lists.tizen.org
> https://lists.tizen.org/listinfo/dev
> 
___
Dev mailing list
Dev@lists.tizen.org
https://lists.tizen.org/listinfo/dev


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

2017-12-17 Thread Inki Dae
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://wiki.tizen.org/Tizen_3.0_Porting_Guide

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.
http://download.tizen.org/releases/milestone/tizen/4.0.m1/tizen-unified_20170529.1/repos/standard/packages/armv7l/

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@lists.tizen.org
https://lists.tizen.org/listinfo/dev