Ozone documentation: Take into account recent changes in Linux Desktop

docs/ozone_overview.md

Index: docs/ozone_overview.md
diff --git a/docs/ozone_overview.md b/docs/ozone_overview.md
index 965c3320dcb49e59ffaf170dd466abc30a07980a..2bfe5792f80386daf3671719ff28e08e151ec991 100644
--- a/docs/ozone_overview.md
+++ b/docs/ozone_overview.md
@@ -160,10 +160,30 @@ Then to run for example the headless platform:
                                   --ozone-dump-file=/tmp/
 ```
 
-### Linux Desktop - ([bug](http://crbug.com/295089))
+### Linux Desktop - ([waterfall](https://build.chromium.org/p/chromium.fyi/builders/Ozone%20Linux/))
+Support for Linux Desktop is currently [in-progress](http://crbug.com/295089).
 
-This is not supported by any of the in-tree platforms. Please see above and try
-a ChromeOS or embedded build for now.
+The following targets are currently working:
+
+* various unit tests
+* `content_shell`

[tonikitoo, 2016/11/08 13:09:21]

lets omit content_shell for now, since it is build-able but non-functional at
this point.

[fwang, 2016/11/08 13:12:18]

OK

+* `chrome`
+
+To build `chrome`, do this from the `src` directory:
+
+``` shell
+gn args out/OzoneLinuxDesktop --args="use_ozone=true enable_package_mash_services=true"
+ninja -C out/OzoneLinuxDesktop chrome
+```
+Then to run for example the X11 platform:
+
+``` shell
+./out/OzoneLinuxDesktop/chrome --ozone-platform=x11 \
+                               --disable-setuid-sandbox \
+                               --mash
+```
+
+Note: You may need to apply [this patch](https://codereview.chromium.org/2485673002/) to avoid missing ash resources during chrome execution.
 
 ### GN Configuration notes
 
@@ -242,18 +262,16 @@ and then partially upstreamed.
 It is still actively being developed in the chromium tree, feel free to discuss
 with us on freenode.net, `#ozone-wayland` channel or on `ozone-dev`.
 
-In order to run an Ozone build of `chrome`, you currently (2016/10/28)
-need to compile it for ChromeOS, where software rendering is not allowed.
-Also, accelerated rendering only works in Ozone/Wayland when the UI and GPU
-components are running in the same process. Below are some quick build & run
-instructions. It is assumed that you are launching `chrome` from a Wayland
-environment such as `weston`.
+Below are some quick build & run instructions. It is assumed that you are
+launching `chrome` from a Wayland environment such as `weston`. Apply
+[this patch](https://codereview.chromium.org/2485673002/) and execute the
+following commands:
 
 ``` shell
-gn args out/OzoneWayland --args="use_ozone=true ozone_platform_wayland=true target_os=\"chromeos\""
+gn args out/OzoneWayland --args="use_ozone=true enable_package_mash_services=true"
 ninja -C out/OzoneWayland chrome
 ./out/OzoneWayland/chrome --ozone-platform=wayland \
-                          --in-process-gpu \
+                          --mash \
                           --disable-setuid-sandbox

[tonikitoo, 2016/11/08 13:09:21]

can we launch with it, if we build the 'chrome_sandbox' target?

[fwang, 2016/11/08 13:12:18]

I guess so. But I think the sandbox and all these --disable-setuid-sandbox
option changes should be handled in a separate CL.

 ```