From: Przemo Firszt <przemo@firszt.eu>
To: Daniel Nicoletti <dantti12@gmail.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org
Subject: Re: HID battery strength does not emit power_suppy udev events
Date: Tue, 01 Jan 2013 19:46:26 +0000 [thread overview]
Message-ID: <1357069586.8915.11.camel@localhost> (raw)
In-Reply-To: <CACo8zOc5QkhotrEPdeK23rfkjPeOa5PgXpXjBUeFPrPWbTAJ1w@mail.gmail.com>
Dnia 2012-12-27, czw o godzinie 22:16 -0200, Daniel Nicoletti pisze:
> Hi, I've sent this message a while ago but forgot to add
> linux-input, I'm really willing to give it a final fix to the issue
> but I need directions, I really can't see what's wrong with
> the udev thing, so again (with linux-input):
>
> The problem is that when a HID device that has a battery
> is added to the system it doesn't emit the udev events
> for the battery added or removed, which breaks upower..s
Hi Daniel,
I have a wacom device with battery. A "udevadm monitor" report when
connecting Intuos4 Wireless over bluetooth: http://pastebin.com/zyaXeqcS
Battery state is only updated when the tablet is in use.
What kind of problems you have? Intuos4 Wireless battery reporting seems
to be working fine (except wrong name, but that's a gnome issue)
--
Kind regards,
Przemo Firszt
next prev parent reply other threads:[~2013-01-01 20:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 2:30 HID battery strength does not emit power_suppy udev events Daniel Nicoletti
[not found] ` <CAD2FfiEbqUvfuUYpgQFaXoUBAn_7TnV4FnGXNDeD-jHCCfpGVQ@mail.gmail.com>
[not found] ` <CACo8zOeSf_0ump=ChJKvgLQL1_OVoOE5Ts0ybw=5S3ZFMzZcGw@mail.gmail.com>
2012-12-28 0:16 ` Daniel Nicoletti
2013-01-01 19:46 ` Przemo Firszt [this message]
[not found] ` <CACo8zOf9LdPA_OZSLZp3iQj80+DvVvQh_Wc6Or902SSJ2hMWVg@mail.gmail.com>
2013-01-01 20:56 ` Przemo Firszt
[not found] ` <CACo8zOe6muNzxE+u-V3dFD27e-2h9w7267Pk3SAUZFsF-Ok9Vw@mail.gmail.com>
2013-01-02 3:24 ` Daniel Nicoletti
2013-01-02 15:04 ` Przemo Firszt
2013-01-02 23:57 ` Daniel Nicoletti
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=1357069586.8915.11.camel@localhost \
--to=przemo@firszt.eu \
--cc=dantti12@gmail.com \
--cc=jeremy@goop.org \
--cc=jkosina@suse.cz \
--cc=linux-input@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 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).