From: Pavel Machek <pavel@ucw.cz>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Pablo Ceballos <pceballos@google.com>,
Jiri Kosina <jikos@kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [PATCH] HID: Driver for Google Hangouts Meet Speakermic
Date: Sun, 22 May 2022 17:05:47 +0200 [thread overview]
Message-ID: <20220522150546.GA8071@localhost> (raw)
In-Reply-To: <CAO-hwJ+Rs=LYseLP7Vvr00vLvm+fTCRdh8pQ-rEduj4izSyiYA@mail.gmail.com>
Hi!
> > No, that is exactly what I had in mind, thank you. Please submit this
> > entry to upstream systemd/udev project (and we can cherry-pick it into
> > our udev as well).
> >
> > In general I think we should try to avoid trivial "fixup" HID drivers if
> > it is possible. I also wondered if we could be supplying fixed-up HID
> > descriptors via request_firmware() for HID devices.
>
> Just FYI, in case you haven't noticed it :)
> I am currently working on supporting exactly this kind of fixups
> through eBPF. I had in the past a request_firmware() patch for wacom
Is that good idea? eBPF is fairly dangerous thing, so I'd preffer
basic functionality not depend on it...
Best regards,
Pavel
next prev parent reply other threads:[~2022-05-22 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 18:39 [PATCH] HID: Driver for Google Hangouts Meet Speakermic Pablo Ceballos
2022-04-12 22:20 ` Pablo Ceballos
2022-04-21 7:48 ` Jiri Kosina
2022-05-12 9:34 ` Dmitry Torokhov
2022-05-12 10:53 ` Jiri Kosina
2022-05-12 22:35 ` Pablo Ceballos
2022-05-12 22:47 ` Dmitry Torokhov
2022-05-16 15:03 ` Pablo Ceballos
2022-05-16 18:23 ` Benjamin Tissoires
2022-05-22 15:05 ` Pavel Machek [this message]
2022-05-23 6:50 ` Jiri Kosina
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=20220522150546.GA8071@localhost \
--to=pavel@ucw.cz \
--cc=benjamin.tissoires@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pceballos@google.com \
/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.