When doing a GET_REPORT request on the keyboard control endpoint,
the report ID should 0 (ie report ID not used) rather than 1
as reports are not used in boot mode.
Signed-off-by: Vincent Palatin vpala...@chromium.org
---
common/usb_kbd.c |2 +-
1 files changed, 1 insertions(+), 1
Hi,
2012/1/9 Vincent Palatin vpala...@chromium.org:
When doing a GET_REPORT request on the keyboard control endpoint,
the report ID should 0 (ie report ID not used) rather than 1
as reports are not used in boot mode.
Signed-off-by: Vincent Palatin vpala...@chromium.org
---
Applied to
When doing a GET_REPORT request on the keyboard control endpoint,
the report ID should 0 (ie report ID not used) rather than 1
as reports are not used in boot mode.
Signed-off-by: Vincent Palatin vpala...@chromium.org
---
common/usb_kbd.c |2 +-
1 files changed, 1 insertions(+), 1
When doing a GET_REPORT request on the keyboard control endpoint,
the report ID should 0 (ie report ID not used) rather than 1
as reports are not used in boot mode.
Signed-off-by: Vincent Palatin vpala...@chromium.org
---
common/usb_kbd.c |2 +-
1 files changed, 1 insertions(+), 1
On Mon, Jan 9, 2012 at 12:46, Marek Vasut marek.va...@gmail.com wrote:
When doing a GET_REPORT request on the keyboard control endpoint,
the report ID should 0 (ie report ID not used) rather than 1
as reports are not used in boot mode.
Signed-off-by: Vincent Palatin vpala...@chromium.org
---
On Mon, Jan 9, 2012 at 12:46, Marek Vasut marek.va...@gmail.com wrote:
When doing a GET_REPORT request on the keyboard control endpoint,
the report ID should 0 (ie report ID not used) rather than 1
as reports are not used in boot mode.
Signed-off-by: Vincent Palatin
6 matches
Mail list logo