The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)

Community Workspace

From Mer Wiki
(Difference between revisions)
Jump to: navigation, search
m (Changed dead links to link to web archive pages)
 
(8 intermediate revisions by one user not shown)
Line 9: Line 9:
 
== Community Resources ==
 
== Community Resources ==
  
−
* MeeGo Porting Guide - http://wiki.meego.com/MeeGo_Porting_Guide <span style="color:red;">[DEAD LINK]</span> possibly refer instead to https://wiki.merproject.org/wiki/Nemo/Porting
+
* MeeGo Porting Guide - http://web.archive.org-main.us/web/20130620101856/http://wiki.meego.com/MeeGo_Porting_Guide <span style="color:red;">[ARCHIVE LINK]</span> possibly refer instead to [[Adaptation_Guide]] or [[Nemo/Porting]]
−
* MeeGo Image Creator Guide - http://wiki.meego.com/Image_Creation <span style="color:red;">[DEAD LINK]</span> possibly refer instead to  https://wiki.merproject.org/wiki/Image_Creation
+
* MeeGo Image Creator Guide - http://web.archive.org-main.us/web/20130929105928/http://wiki.meego.com/Image_Creation <span style="color:red;">[ARCHIVE LINK]</span> possibly refer instead to  [[Image_Creation]]
−
* MeeGo OBS (opensuse build server) - http://wiki.meego.com/OBS <span style="color:red;">[DEAD LINK]</span> possibly refer instead to https://wiki.merproject.org/wiki/Building_against_Mer_in_COBS
+
* MeeGo OBS (opensuse build server) - http://web.archive.org-main.us/web/20121017020918/http://wiki.meego.com/OBS <span style="color:red;">[ARCHIVE LINK]</span> possibly refer instead to [[Building_against_Mer_in_COBS]]
 
* [http://webchat.freenode.net/?channels=Mer IRC Chat] @ irc.freenode.net ~ #mer
 
* [http://webchat.freenode.net/?channels=Mer IRC Chat] @ irc.freenode.net ~ #mer
  
 
== Device Adaptations ==
 
== Device Adaptations ==
−
Adaptations available under obs (https://build.merproject.org/project/list_public) are typically (but not consistently) named hw:vendor:processor:sbc, e.g., hw:ti:omap4:pandaboard. (see also https://wiki.merproject.org/wiki/OBS_architecture_naming)
+
See also [[Adaptations]]
−
The items below are typically listed by a common device or sbc (single board computer) name, which is not necessarily unique; e.g., Google Nexus 7 2012 is nv:tegra3:nexus7, Google Nexus 7 2013 might rather be qualcomm:s4pro:nexus7, and would likely share very little in common with nv:tegra3:nexus7.
+
 
 +
Adaptations available under obs (https://build.merproject.org/project/list_public) are typically (but not consistently) named hw:vendor:processor:sbc, e.g., hw:ti:omap4:pandaboard. (see also [[OBS_architecture_naming]])
 +
The items below are typically listed by a common device or sbc (single board computer) name, which is not necessarily unique; e.g., Google Nexus 7 2012 is nv:tegra3:nexus7, Google Nexus 7 2013 might rather be google:msm:nexus7 or maybe it would be a child of qualcomm:s4pro.
  
 
To estimate the level of activity in an adaptation project on obs, you might look at the kernel adaptation package, and check the top line of the "changes" file, e.g., kernel-adaptation-pandaboard.changes to see the kernel version and/or date of recent patches.  Many of the adaptations listed below are outdated, one-time, "proof-of-concept" activities, rather than useful, active hardware ports.  There might also be adaptations hosted completely externally to the obs that are not documented here.
 
To estimate the level of activity in an adaptation project on obs, you might look at the kernel adaptation package, and check the top line of the "changes" file, e.g., kernel-adaptation-pandaboard.changes to see the kernel version and/or date of recent patches.  Many of the adaptations listed below are outdated, one-time, "proof-of-concept" activities, rather than useful, active hardware ports.  There might also be adaptations hosted completely externally to the obs that are not documented here.
Line 30: Line 32:
 
** New: [[N9 Kernel update project]]
 
** New: [[N9 Kernel update project]]
 
* Raspberry Pi
 
* Raspberry Pi
−
** armv6l Initial bringup with alpha board http://wiki.meego.com/User:Vgrade#Raspberry_Pi <span style="color:red;">[DEAD LINK]</span>  
+
** armv6l Initial bringup with alpha board http://web.archive.org-main.us/web/20130417082315/http://wiki.meego.com/User:Vgrade#Raspberry_Pi <span style="color:red;">[ARCHIVE LINK]</span>  
 
** SDK Version [[Community Workspace/RaspberryPi]]
 
** SDK Version [[Community Workspace/RaspberryPi]]
 
* ExoPc
 
* ExoPc
Line 101: Line 103:
  
 
* Cordia HD
 
* Cordia HD
−
** http://cordiahd.org/download/HD/ <span style="color:red;">[DEAD LINK]</span>
+
** http://web.archive.org-main.us/web/20130521115736/http://cordiahd.org/download/HD/ <span style="color:red;">[ARCHIVE LINK]</span>
−
** http://cordiahd.org/ <span style="color:red;">[DEAD LINK]</span>
+
** http://web.archive.org-main.us/web/20120103171958/http://cordiahd.org/ <span style="color:red;">[ARCHIVE LINK]</span>
 
** http://www.youtube.com/watch?v=T4XxQpJpitY
 
** http://www.youtube.com/watch?v=T4XxQpJpitY
 
* Cordia Dawati
 
* Cordia Dawati
Line 139: Line 141:
 
* [[Sailfish]]  
 
* [[Sailfish]]  
 
* ...
 
* ...
 +
 +
==Benchmarks==
 +
[[Quality]] has some information about QA infrastructure (testing, quality metrics).  That infrastructure intends to provide for automated testing and benchmarking to assist in optimization, regression testing, etc.  Unfortunately the effort is stagnant. 
 +
 +
This section collects some information to quantify and summarize community end-user experience as a function of device, software release, etc.
 +
* General
 +
** http://openbenchmarking.org/ has a wide variety of modern benchmarks; the test framework has a dependency on php (php-cli) (as yet unpackaged).
 +
* Hardware
 +
** CPU
 +
*** nbench http://www.tux.org/~mayer/linux/bmark.html provide a suite of c codes to assess single-cpu performance. Since it depends only on a c compiler, it is of use on hardware for which no UI is available. (packaging in progress)
 +
** GPU / Graphics
 +
*** ?
 +
* UX
 +
** ?

Latest revision as of 20:35, 7 January 2015

Two quotes from the 'MeeGo Reconstructed' email (http://lists.meego.com/pipermail/meego-dev/2011-October/484215.html) [DEAD LINK] describe what can find here.

  • 'Initially the project will be developing a Core for basing products on and will split UX and hardware adaptations out into separate projects within the community surrounding the Core'
  • 'We will continue to welcome contribution and participation from the hacker community - in fact we aim to make it so easy to port to a new vendor device that a single hacker could do it for their device'

Some of the information is taken from the MeeGo project with which we share a number of tools and processes.

Contents

[edit] Community Resources

[edit] Device Adaptations

See also Adaptations

Adaptations available under obs (https://build.merproject.org/project/list_public) are typically (but not consistently) named hw:vendor:processor:sbc, e.g., hw:ti:omap4:pandaboard. (see also OBS_architecture_naming) The items below are typically listed by a common device or sbc (single board computer) name, which is not necessarily unique; e.g., Google Nexus 7 2012 is nv:tegra3:nexus7, Google Nexus 7 2013 might rather be google:msm:nexus7 or maybe it would be a child of qualcomm:s4pro.

To estimate the level of activity in an adaptation project on obs, you might look at the kernel adaptation package, and check the top line of the "changes" file, e.g., kernel-adaptation-pandaboard.changes to see the kernel version and/or date of recent patches. Many of the adaptations listed below are outdated, one-time, "proof-of-concept" activities, rather than useful, active hardware ports. There might also be adaptations hosted completely externally to the obs that are not documented here.

[edit] User Experience UX

[edit] Benchmarks

Quality has some information about QA infrastructure (testing, quality metrics). That infrastructure intends to provide for automated testing and benchmarking to assist in optimization, regression testing, etc. Unfortunately the effort is stagnant.

This section collects some information to quantify and summarize community end-user experience as a function of device, software release, etc.

  • General
    • http://openbenchmarking.org/ has a wide variety of modern benchmarks; the test framework has a dependency on php (php-cli) (as yet unpackaged).
  • Hardware
    • CPU
      • nbench http://www.tux.org/~mayer/linux/bmark.html provide a suite of c codes to assess single-cpu performance. Since it depends only on a c compiler, it is of use on hardware for which no UI is available. (packaging in progress)
    • GPU / Graphics
      •  ?
  • UX
    •  ?
Retrieved from "https://wiki.merproject.org/wiki/index.php?title=Community_Workspace&oldid=5258"
Personal tools