diff options
| author | rockot@chromium.org <rockot@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-02-11 04:49:12 +0000 |
|---|---|---|
| committer | rockot@chromium.org <rockot@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-02-11 04:49:12 +0000 |
| commit | 896ad659e3f78abb5ac9ac154fa963ccc39b3a6d (patch) | |
| tree | 17ec9eae22bc246ff9e839fb33dad6fb6fb0d374 /apps/shell/browser/shell_extensions_browser_client.h | |
| parent | ac18d6d54ca52ab266871f1005bf2f73191cbb87 (diff) | |
| download | chromium_src-896ad659e3f78abb5ac9ac154fa963ccc39b3a6d.zip chromium_src-896ad659e3f78abb5ac9ac154fa963ccc39b3a6d.tar.gz chromium_src-896ad659e3f78abb5ac9ac154fa963ccc39b3a6d.tar.bz2 | |
Reboot serial bitrate setting on OS X
IOSSIOSPEED support is bad and provides no suitable means
to query a device's speed once it's been set. Given that
most (all?) drivers which support custom bitrates seem to
happily accept literal rate values in the termios struct,
IOSSIOSPEED usage is being removed.
Additionally the getInfo impl will no longer refuse to
interpret tcgetattr's returned bitrate when it doesn't
correspond to a defined constant. Instead, non-zero,
non-standard bitrate values are interpretted literally.
This seems to be the "most correct" behavior for managing
these settings.
BUG=337482
Review URL: https://codereview.chromium.org/143383009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@250349 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'apps/shell/browser/shell_extensions_browser_client.h')
0 files changed, 0 insertions, 0 deletions