Some stuff to report.
- on M0 the sound card seems to be broken, i reported this to the kernel
guys and they are working on it
- i managed to port XBMC on M0 with wayland/weston, this allowed me to
test video playback and I can get HD video output, it works very nice
and looks really crisp on the M0 amoled display, xbmc does not see any
touch input events so i have to remote control it over the network (the
web interface)
- also i noticed that moving weston-terminal windows around on the
screen using touch events causes weston to crash very often, i will post
a JIRA bug once i can get a stack trace of what's happening
- the latest 3.10 kernel has brightness support on M0, the exynos.sh
script inside the acid-env rpm i mention on the WIKI can use that to dim
the display to save battery (useful if you are building stuff directly
on the target, the display takes quite a lot of energy when in full
brightness)
best regards.
On 05/16/2014 10:25 AM, Dominig ar Foll (Intel OTC) wrote:
Hello,
I am pleased to announce that we have reactivated the build of Tizen3
for ARM 32 bits architecture.
The initial goal is to create a Common image for an ARM easy to
purchase hacker board. the current candidate is the Odroid-U3
I am quite convinced that he community will add support for other
boards in a second phase.
http://en.wikipedia.org/wiki/Odroid
http://www.cnx-software.com/2013/12/23/hardkernel-unveils-59-odroid-u3-board-powered-by-exynos-4412-prime-quad-core-soc/?utm_source=rss&utm_medium=rss&utm_campaign=hardkernel-unveils-59-odroid-u3-board-powered-by-exynos-4412-prime-quad-core-soc&utm_reader=feedly
Once that phase passed, we will work on the creation of a Tizen IVI
ARM target. I hope that we will get the support of an IVI vendor to
create a reference image for a device which is closer to the IVI
needs, in a similar way of what is done in IA with the VTC1010. Any
volunteer ?
You can see the progress of the build on the Tizen OBS. Note that as
we are still fixing some core building issue (the recent move to KVM
for the OBS builder is not fully transparent), it might be that we
have to force a full build a few times more. Don't panic if you see
that all packages are broken.
The status when sending this email was :
arm-wayland armv7l
succeeded: 716
failed: 7
unresolvable: 12
disabled: 3
excluded: 18
Real time status
https://build.tizen.org/project/show?project=Tizen%3ACommon
We are currently working on a reliable rebuild of glibc (hence the
risk of full rebuild).
The major building work remaining to be done, is Crosswalk and QT5.
Then will attack the image creation.
If you want it to be delivered quicker, meet us on the Tizen Dev
mailing list we will tell you how you can help.
https://lists.tizen.org/listinfo/dev
Regards
P.S. The key engineers in charge of that work will be in San Francisco
for the Tizen Developer conference. Come and share a drink with us.
--
--------------
Roman Kubiak
--------------
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
