From: Benjamin Berg <benjamin@sipsolutions.net>
To: Alex Henrie <alexhenrie24@gmail.com>,
Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Huw Davies <huw@codeweavers.com>,
linux-pm@vger.kernel.org, Wine Devel <wine-devel@winehq.org>
Subject: Re: How to identify the primary battery (for Wine)
Date: Tue, 14 Jun 2022 10:05:46 +0200 [thread overview]
Message-ID: <be17cc9d88b557b0b9dab14ca92ecd257e766468.camel@sipsolutions.net> (raw)
In-Reply-To: <CAMMLpeTRZnpQ8b6puhHeKaDgzW12ZM_g3nAWjVP71HbSaeHktQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
Hi all,
On Mon, 2022-06-13 at 19:54 -0600, Alex Henrie wrote:
> I've been working to improve battery status reporting for applications
> running on Wine on Linux. However, we Wine developers are not sure
> what the best way is to determine which battery is the computer's
> primary battery. Could you take a look at
> https://gitlab.winehq.org/wine/wine/-/merge_requests/134 and leave a
> comment there or on the wine-devel mailing list?
Wouldn't it make sense for Wine to use the UPower provided
DisplayDevice that can be queried through DBus?
Benjamin
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-06-14 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 1:54 How to identify the primary battery (for Wine) Alex Henrie
2022-06-14 8:05 ` Benjamin Berg [this message]
2022-06-14 14:17 ` Sebastian Reichel
2022-06-14 15:17 ` Alex Henrie
2022-06-17 11:31 ` Benjamin Berg
2022-06-18 15:03 ` Alex Henrie
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=be17cc9d88b557b0b9dab14ca92ecd257e766468.camel@sipsolutions.net \
--to=benjamin@sipsolutions.net \
--cc=alexhenrie24@gmail.com \
--cc=huw@codeweavers.com \
--cc=linux-pm@vger.kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=wine-devel@winehq.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox