| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#333457}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#333019}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#332793}
|
|
|
|
|
|
|
|
|
|
| |
This updates the remaining users of the "using"
BUG=
Review URL: https://codereview.chromium.org/1144333006
Cr-Commit-Position: refs/heads/master@{#332731}
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is everything but the chrome directory
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
TBR=zelidrag@chromium.org (chromeos)
TBR=keybuk@chromium.org (device/bluetooth)
Review URL: https://codereview.chromium.org/1162943002
Cr-Commit-Position: refs/heads/master@{#332626}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When switching from Chrome to Frecon, Frecon waits for the dbus reply to
take ownership of the DRM device. Since NativeDisplayDelegate calls may
be async, the current code responds back to Frecon at the same time as
the IPC to release master happens. As a consequence it is possible that
Frecon tries to acquire master before Chrome releases it.
This change updates the NativeDisplayDelegate API to allow
asynchronously taking and releasing of the display control (DRM master)
and updates the console service provider to use the async API.
BUG=none
Review URL: https://codereview.chromium.org/1160973005
Cr-Commit-Position: refs/heads/master@{#332604}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#332565}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When running with --stub-cros-settings, skip the owner settings service and
go straight to the CrosSettings for managing settings. This allows changes to
settings to persist to the in-memory stub copy.
This is useful for testing with a CrOS simulated environment on a linux desktop.
BUG=495403
Review URL: https://codereview.chromium.org/1164523006
Cr-Commit-Position: refs/heads/master@{#332530}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#332353}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#332164}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#332134}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#332118}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#331931}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#331749}
|
|
|
|
|
|
|
|
| |
BUG=480007
Review URL: https://codereview.chromium.org/1128323004
Cr-Commit-Position: refs/heads/master@{#331746}
|
|
|
|
|
|
|
|
|
|
|
| |
A visitor of the command line list page on peter.sh found this typo,
so let's fix the comment in the source :-).
BUG=none
Review URL: https://codereview.chromium.org/1155163005
Cr-Commit-Position: refs/heads/master@{#331582}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#331542}
|
|
|
|
|
|
|
|
|
|
| |
The NetworkChangeNotifier is adding support for the theoretical maximum bandwidth of a connection based upon the NetInfo v3 spec: http://w3c.github.io/netinfo/. This CL adds ChromeOS support for the GetCurrentMaxBandwidth function and the max bandwidth changed notification.
BUG=412741
Review URL: https://codereview.chromium.org/1143293002
Cr-Commit-Position: refs/heads/master@{#331373}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#331329}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#331265}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#331247}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#331233}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are many callers, so all could not be updated at once. The old version is renamed to JSONReader::DeprecatedRead, and a new version of JSONReader::Read that returns scoped_ptr takes its place.
Much of this patch was generated with sed. Some callsites of the form
scoped_ptr<Value> value(Read());
have been updated to
scoped_ptr<Value> value = Read();
but most Read() calls are simply converted to DeprecatedRead. Actually updating them is a TODO.
BUG=none
Review URL: https://codereview.chromium.org/1136643005
Cr-Commit-Position: refs/heads/master@{#331120}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#331075}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a mechanical rename from subdirs into memory/ with _platform
suffixes instead. This avoids having duplicate basenames.
It would probably be better to have only
memory/memory_pressure_monitor.h and then _win.cc, _mac.cc, _chromeos.cc
implementations, but that's a more invasive change because of the
slightly different interfaces/members.
TBR=jam@chromium.org, oshima@chromium.org
R=thakis@chromium.org, chrisha@chromium.org
BUG=490824, gyp:384,472772
Review URL: https://codereview.chromium.org/1149223002
Cr-Commit-Position: refs/heads/master@{#331006}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#330908}
|
|
|
|
|
|
|
|
|
|
|
| |
Because I no longer work on code in these directories these days.
Add hashimoto@ to chrome/browser/chromeos/dbus/OWNERS.
BUG=none
Review URL: https://codereview.chromium.org/1144023003
Cr-Commit-Position: refs/heads/master@{#330709}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#330706}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Following https://codereview.chromium.org/1129863003/ which added
support for loading an apply an ICC file based on EDID product id a new
entry was added to the chromeos paths switch statement. Unfortunately
the break statement was missing in the newly added case.
Failing to break from the switch statement triggered a DCHECK failure in
path_service.cc which would result in in asserts in builds where DCHECK
is fatal.
BUG=489643
TEST=None
Review URL: https://codereview.chromium.org/1145793002
Cr-Commit-Position: refs/heads/master@{#330549}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#330488}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#330332}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#330303}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#330283}
|
|
|
|
|
|
|
|
|
|
|
|
| |
Clearer API; flushes out a lot of unnecessary heap allocations.
depends on https://codereview.chromium.org/1129083003/
BUG=none
Review URL: https://codereview.chromium.org/1131113004
Cr-Commit-Position: refs/heads/master@{#330255}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The only place where Device ID is stored on Chrome OS is the local state from now on.
Order of events:
1) User logs in. There are two options:
a) User athenticated through GAIA. We read known user device ID from local state if it exists or generate a new one if it doesn't. Then we save the device ID in a user context.
b) Otherwise, we don't store device ID in user context.
2) If it is GAIA_WITHOUT_SAML-mode, we send device ID to LSO in "oauth2/token" request (OAuth2TokenInitializer class). If it is not, we'll send it in "o/oauth2/programmatic_auth" request on step (5).
3) After NotifyUserLoggedIn() call, we store the device ID from the user context (if it is set) to local state. Then we start to create/load a profile for the user.
4) In constructor of ChromeSinginClient we migrate device id from kGoogleServicesSigninScopedDeviceId pref to the local state, if a value in the local state is empty.
5) We request tokens with "o/oauth2/programmatic_auth" if we haven't done that on step (2). Old code for sending device ID works here, because it relies on ChromeSigninClient which returns device ID set on step (4).
BUG=486044,486136
Review URL: https://codereview.chromium.org/1138143002
Cr-Commit-Position: refs/heads/master@{#330207}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#330055}
|
|
|
|
|
|
|
|
|
|
| |
This is cleanup from https://codereview.chromium.org/1122863005/
BUG=472772
Review URL: https://codereview.chromium.org/1124163003
Cr-Commit-Position: refs/heads/master@{#330032}
|
|
|
|
|
|
|
|
|
|
|
| |
Enable firewall hole punching for Chrome Apps by taking this feature out
from behind a flag.
BUG=478231
Review URL: https://codereview.chromium.org/1136843008
Cr-Commit-Position: refs/heads/master@{#329959}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes crosh process creation (used by terminalPrivate API) fail
gracefully when file descriptors used to observe process output
cannot be used by select (as opposed to crashing).
BUG=480616
TEST=Open huge number of crosh terminals in short time, until terminal
launching starts failing.
Review URL: https://codereview.chromium.org/1135823007
Cr-Commit-Position: refs/heads/master@{#329901}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change adds a new member to ui::DisplaySnapshot, 'product_id',
which is populated from the EDID in DrmDisplaySnapshot when it is
created.
DisplaySnapshot::product_id() is then turned into a hexadecimal string
and used to try and load an ICC file from a common path.
BUG=471749
TEST=On a link_freon system blue-vcgt-test-color-profile.icc was copied into
/usr/share/color/icc/30e400000000.icc and the system rebooted and the display
was observed tinted blue.
Review URL: https://codereview.chromium.org/1129863003
Cr-Commit-Position: refs/heads/master@{#329888}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#329816}
|
|
|
|
|
|
|
|
|
|
| |
TBR=suzhe@chromium.org
BUG=407456
TEST=Verified on linux_chromeos & clapper device.
Review URL: https://codereview.chromium.org/1132333002
Cr-Commit-Position: refs/heads/master@{#329810}
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds wiring to expose TxPower field during device discovery.
BUG=407773
R=armansito@chromium.org
Review URL: https://codereview.chromium.org/1133173002
Cr-Commit-Position: refs/heads/master@{#329694}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#329600}
|
|
|
|
|
|
|
|
|
| |
BUG=486738
R=stevenjb@chromium.org, pneubeck@chromium.org
Review URL: https://codereview.chromium.org/1137633003
Cr-Commit-Position: refs/heads/master@{#329291}
|
|
|
|
|
|
|
|
|
|
| |
Function "DisconnectRequested" name contained a typo.
BUG=
Review URL: https://codereview.chromium.org/1136463008
Cr-Commit-Position: refs/heads/master@{#329123}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#329042}
|
|
|
|
|
|
|
|
|
|
|
| |
Default becomes enabled.
BUG=413541
TEST=manually tested
Review URL: https://codereview.chromium.org/1114123005
Cr-Commit-Position: refs/heads/master@{#328715}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the command line switch --internal-display-color-profile-file is provided
load the given ICC file using qcms and extract the VCGT data. Use this VCGT
data to apply a gamma ramp to change the output on the internal display using
drmModeCrtcSetGammaRamp.
Original CL: https://codereview.chromium.org/1028563003/
Reason for reland: Linux ChromiumOS GN (dbg) build broke (missing qcms dep in
ash/BUILD.gn)
BUG=471749
TEST=On a link_freon device add the command line option to load a sample ICC
file (e.g. Bluish.icc to give a blue tint) and observe on startup that the
internal display is blue tinted.
TBR=sievers@chromium.org
Review URL: https://codereview.chromium.org/1119113004
Cr-Commit-Position: refs/heads/master@{#328514}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#328497}
|