3169 2012-09-25 13:38:44 +0000 Implement Shuku proposal 2017-12-06 16:46:26 +0000 1 1 6 Yocto Project Subprojects Sato sato 1.3 All Multiple RESOLVED FIXED Medium+ enhancement 2.2 M1 35 2415 4659 8606 9664 1 ross.burton jku alex.kanavin alexandru.c.georgescu alexandru.damian david.c.stewart jessica.zhang jose.perez.carranza richard.purdie song.liu terence.chiang --- --- Don't know oldest_to_newest 25692 0 ross.burton 2012-09-25 13:38:44 +0000 The Shuku proposal was basically turning Sato into a test runner and validation UI instead of a bad PIM. 25848 1 alexandru.damian 2012-09-27 12:50:00 +0000 Do we have any kind of specs ? I assume this is a 1.4 task ? 25849 2 ross.burton 2012-09-27 13:05:15 +0000 1.4, yes. No hard specification but my proposal was on oe-core. 27721 3 terence.chiang 2012-11-27 11:56:04 +0000 I think integrating “Phoronix Test Suite” in the YP layer is a good approach as the first step. I aslo get some feedback from the board manufactures that what tools are used for platform validation. most of them are tools in DOS. But I don't know whether there are some similar tools in Linux that could be used. here is the list: CPU test : chkcpu.exe (DOS6.22) com port test: BEAR UART Card (DOS6.22) LAN port test: novell link test (DOS6.22), Lanconf (DOS), iperf (Linux) USB port test: bear usb-t02 card (DOS6.22), USBHSET (Windows) SATA HDD test: copy&compare (DOS6.22) SATA test : RU473/ADU461 (DOS) DRAM test : read dram size (DOS6.22), Memtest86(Windows/Linux) PCI-E Test : bear pci-e card (DOS6.22) Fan Test : cmos check (Dos6.22) buzzer test : speaker.com (DOS6.22) Gfx test : 3DMark (Windows/Linux), OpenArena (Windows/Linux), glxgears, render_bench, VLC Burn-in for All : Passmark (Windows) for running 72 hours Burn-in for Com Port: PCCOM2000 (Windows) for running 72 hours Burn-in for Storage : Winthrax.exe (Windows) 27722 4 ross.burton 2012-11-27 12:01:31 +0000 I'm not entirely convinced phoronix is the best idea as it has a massive range of dependencies (postgres, apache, ...). My initial goal isn't to focus on raw performance but functional testing: - does the touchscreen work correctly - 2D acceleration - GL support - VAAPI support - sound input/output through each output And so on. 31629 5 david.c.stewart 2013-04-05 23:10:48 +0000 Promoting this to HIGH for 1.5 33405 6 richard.purdie 2013-05-30 15:06:02 +0000 Ross is clearly doing this ;-) 34282 7 ross.burton 2013-07-02 15:05:12 +0000 In progress but not ready for merging. 50730 8 alexandru.c.georgescu 2015-05-04 11:09:55 +0000 (In reply to comment #7) > In progress but not ready for merging. Hi Ross, Any updates on this? 55103 9 ross.burton 2015-10-09 10:37:16 +0000 To make this bug clear as all the discussion happened on the mailing lists - the Shuku proposal is to take Sato, port to GTK+3 (this is mostly done, needs bug fixing), and drop the pretence that it's a reference UI for a PDA, swapping stuff like "Music Player" for "GStreamer test harness" (this in particular has happened). 55360 10 alex.kanavin 2015-10-15 15:11:49 +0000 *** Bug 8470 has been marked as a duplicate of this bug. *** 55516 11 ross.burton 2015-10-20 14:27:09 +0000 Reassigning to Alex as he expressed interest in actually doing this for 2.1. 58813 12 jku 2016-02-10 09:01:41 +0000 Not sure if it's too late for 2.1 but I finally have something to show so I'm moving to M3 and sending some patches ... 59966 13 jku 2016-03-15 08:57:17 +0000 I've sent a RFC patchset to list: IMO it's too late for 2.1 release, I propose moving to 2.2 M1. 61901 14 jku 2016-05-03 16:11:41 +0000 Status update: * All of the "upstream" patchsets have been sent (mostly to yocto ML) * There's a WIP poky branch that contains these to-be-upstreamed patches and everything else I intend to send: http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=jku/matchbox-wip Possible issues: * Some recipes still depend on GTK+2 (see list below). These are all development tools though: nothing that should be used on actual target images * GTK+3 still currently requires opengl (via libepoxy) * I've had to replace some software: e.g. adding l3afpad to oe-core (as a replacement for leafpad) might still require discussion List of GTK+2 reverse dependencies in oe-core world build after my patches: * gnome-themes-standard - Gtk+2 theme that matches the current Gtk+3 theme * alsa-tools - some tools depend on Gtk+2 sysprof - latest version requires gtk3 & polkit, but can compile without GUI latencytop kernelshark fstests oprofileui libglade - used by by oprofileui and (current) sysprof 61924 15 alex.kanavin 2016-05-04 11:24:45 +0000 It would be good to tag new versions, and make the recipes refer to those versions, instead of just updating the commit ids, e.g. here: http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=jku/matchbox-wip&id=9315cad3da18127925ac0c10e2f208bd2b61c40b So that the recipe reporting system can correctly report those recipes as 'up to date' instead of 'unknown'. 63148 16 jku 2016-06-20 12:47:05 +0000 Not sure how close we got to the original "Shuku proposal" (from Yocto 1.3 !) but I'm calling it done: matchbox components (and the rest of oe-core) now use Gtk+3. Tweaks and improvements to the UI should be filed as new bugs.