diff options
author | reillyg <reillyg@chromium.org> | 2014-10-03 17:41:09 -0700 |
---|---|---|
committer | Commit bot <commit-bot@chromium.org> | 2014-10-04 00:42:04 +0000 |
commit | ceb961140470e5e7a14e41b53ce244947b24a062 (patch) | |
tree | 2d1689624b36f3508e40dbaf2fee69510d5fa18a /chrome/browser/ui/browser_toolbar_model_delegate.h | |
parent | a15bee143f21dcc0fb91b8b7f81848a7e51a38bb (diff) | |
download | chromium_src-ceb961140470e5e7a14e41b53ce244947b24a062.zip chromium_src-ceb961140470e5e7a14e41b53ce244947b24a062.tar.gz chromium_src-ceb961140470e5e7a14e41b53ce244947b24a062.tar.bz2 |
hid: Don't interpret the report ID from incoming feature reports.
The USB HID GET_REPORT(Feature) request includes the report ID that the
host is requesting in the SETUP packet. When the report ID is not zero
the device will send this back to the host as the first byte of the
report. Unlike input and output reports we want to preserve this part of
the report because the device may in fact by sending a value other than
the report ID as the first byte of the response.
To achieve this, on Windows this patch stops stripping the report ID
from the buffer received from the OS. On OS X this was already the
behavior. On Linux this was the behavior if the report ID was non-zero,
otherwise it would artificially prepend a zero to the buffer which must
be removed.
BUG=420112
Review URL: https://codereview.chromium.org/623963003
Cr-Commit-Position: refs/heads/master@{#298135}
Diffstat (limited to 'chrome/browser/ui/browser_toolbar_model_delegate.h')
0 files changed, 0 insertions, 0 deletions