[Dev] [Tizen Product-dev] Tizen on MIPS arch
N S S R Murthy
nssr.murthy at inedasystems.com
Mon Oct 6 06:21:19 GMT 2014
This is a priority question. We are more focused on Tizen wear.
If we go ahead with Tizen 3.0 common and 3.14 Kernel, we can get the base work required for bringing up Tizen wear.
But there seems to be no Tizen wear profile on Tizen 3.0 till now.
Any time lines for it? By when we can see Tizen wearable profile on Tizen 3.0.
----- Original Message -----
From: "N S S R Murthy" <nssr.murthy at inedasystems.com>
To: "Philippe Coval" <philippe.coval at open.eurogiciel.org>
Cc: dev at lists.tizen.org
Sent: Saturday, October 4, 2014 11:02:36 PM
Subject: Re: [Dev] [Tizen Product-dev] Tizen on MIPS arch
We are using 3.10.5 Kernel which we have already used to bring up Android on our platform.
We have disabled the Android specific configurations and rebuilt it with TIzen_defconfig. We'll check the feasibility of using 3.14 kernel with SMACK enabled. We have DRM enabled but still need to integrate the PowerVR driver to it.
Our goal as of today is bring up Tizen 2.2 Mobile. We see that in repos, it is using 3.0 kernel.
We surely plan to contribute to the community. But it can take sometime as we still have to bring up our platform.
I cannot say on whether we maintain our platform specific patches ourselves or make them available through mainstream. That's management decision still pending.
On your suggestion, I have create a request on JIRA here: https://bugs.tizen.org/jira/browse/TC-1690.
I have tried to some local Tizen builds with Tizen 2.2 for armv7l and I am stuck with errors. I have posted that in a different thread: https://lists.tizen.org/pipermail/dev/2014-October/004390.html.
Please suggest on that as well.
----- Original Message -----
From: "Philippe Coval" <philippe.coval at open.eurogiciel.org>
To: "N S S R Murthy" <nssr.murthy at inedasystems.com>
Cc: product-dev at lists.tizen.org, dev at lists.tizen.org
Sent: Friday, October 3, 2014 3:09:56 PM
Subject: Re: [Tizen Product-dev] Tizen on MIPS arch
On Thu, Oct 2, 2014 at 5:29 AM, N S S R Murthy
<nssr.murthy at inedasystems.com> wrote:
> Hi All,
> (Probably I should be referring this mail to Qiang Zhang)
> We are trying to bring up Tizen on MIPS platform. For that we need to update
> the gbs to support MIPS architecture and toolchains.
This is something I care because I am trying to make Tizen:Common
supporting many different hardware
to make sure the system is not arch oriented and can be a solid base
for generic development...
Let me reference your project on this page I am drafting to ease cross
profile kernel packaging
> As of now in build system, I figured gbs/gitbuildsys/cmd_build.py file needs
> to be changed to add MIPS support.
> We have kernel built Tizen configuration and bootloader for the MIPS
> platform we are using.
Which version is it ? do you plan to share the source as community contrib ?
what about the targeted machine
Let me remind Tizen:Common requirements to be supported :
* need to have SMACK enabled
* need to be based on linux lts 3.14.+ (next ltsi?)
* need hw graphics (drm , egl...)
> We have MIPS toolchain binaries, which need to be
> packed into RPMs and put into pre-built/toolchain-mips folder.
Yea I think this is the 1st thing to achieve,
do you indent to use obs/gbs or yocto ?
1st one is current tizen build system .
> Can you please guide me what else needs to be done and how the changes can
> be tested comprehensively before we use this MIPS supported gbs to compile
I dont see any easier way that bootstraping your own OBS server (using qemu)
or deploy it to a MIPS farm
> And please point us to any related documentation on extending Tizen and gbs
> for other architectures.
I dont know any yet . but I know who can help you ,
So I invite you to report a "wish" tizen tracker and try to attract
ps: let's move the conversation to dev list ...
mailto:philippe.coval at eurogiciel.fr -- gpg:0x467094BC
xmpp:philippe.coval.pro at gmail.com
Dev mailing list
Dev at lists.tizen.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Dev