All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 215945] New: No way to get user buffer in ll_driver->raw_request of hid driver sent via hidraw HIDIOCGFEATURE
Date: Thu, 05 May 2022 14:15:22 +0000	[thread overview]
Message-ID: <bug-215945-208809@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=215945

            Bug ID: 215945
           Summary: No way to get user buffer in ll_driver->raw_request of
                    hid driver sent via hidraw HIDIOCGFEATURE
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.17.5
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: ga2mer@yandex.ru
        Regression: No

I am writing support in the custom hid driver for the screen built into the
Thrustmaster T248 steering wheel.

Unfortunately, I can't send what I want in any way and I have to repeat the
flow of their Windows Kernel Driver.

They use a dll to communicate with the screen, which sends a feature report via
HidD_GetFeature, which is sent to their kernel driver and they use one report
id per bunch of actions:
ef 75 .. .. ..
ef 17 .. .. ..
ef 7d .. .. ..

And unfortunately (as I understood from the source code) hidraw_get_report
sends an empty buffer to my raw_request and I can't understand what this report
about.

It would be nice if it was possible to take the user buffer from somewhere.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

                 reply	other threads:[~2022-05-05 14:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-215945-208809@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.