From: Bastien Nocera <hadess@hadess.net>
To: Roderick Colenbrander <roderick@gaikai.com>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: linux-input@vger.kernel.org,
Roderick Colenbrander <roderick.colenbrander@sony.com>
Subject: Re: [PATCH v2 3/3] HID: playstation: support updated DualSense rumble mode.
Date: Tue, 11 Oct 2022 12:15:43 +0200 [thread overview]
Message-ID: <c582cc7d81bbfb2bcf9b397da36324fb84624fa1.camel@hadess.net> (raw)
In-Reply-To: <20221010212313.78275-4-roderick.colenbrander@sony.com>
On Mon, 2022-10-10 at 14:23 -0700, Roderick Colenbrander wrote:
> Newer DualSense firmware supports a revised classic rumble mode,
> which feels more similar to rumble as supported on previous
> PlayStation
> controllers. It has been made the default on PlayStation and non-
> PlayStation
> devices now (e.g. iOS and Windows). Default to this new mode when
> supported.
Are there any ways to update the firmware without a PS5? Using LVFS to
distribute the firmware, on Linux platforms at least, would be great
for end-users.
next prev parent reply other threads:[~2022-10-11 10:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 21:23 [PATCH v2 0/3] improvements and new device support Roderick Colenbrander
2022-10-10 21:23 ` [PATCH v2 1/3] HID: playstation: stop DualSense output work on remove Roderick Colenbrander
2022-10-10 21:23 ` [PATCH v2 2/3] HID: playstation: add initial DualSense Edge controller support Roderick Colenbrander
2022-10-10 21:23 ` [PATCH v2 3/3] HID: playstation: support updated DualSense rumble mode Roderick Colenbrander
2022-10-11 10:15 ` Bastien Nocera [this message]
2022-10-11 14:00 ` Roderick Colenbrander
2022-10-14 11:47 ` Benjamin Tissoires
2022-10-14 14:45 ` Roderick Colenbrander
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=c582cc7d81bbfb2bcf9b397da36324fb84624fa1.camel@hadess.net \
--to=hadess@hadess.net \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=roderick.colenbrander@sony.com \
--cc=roderick@gaikai.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).