like I could so something useful in the end. I'm
not worried yet we didn't have any reply from Richard, considering it's
an holiday season, but I really hope your stuff will get in. They fixes
everything, so kudos.
(Anyway, if things don't move in the upcoming weeks don't h
53%
It still is considered as discharging while having enough light so the
smiley is happy and says it's charging. There's a bug here I guess.
Did you see the light meter property too? It's not reported yet at
least.
(I'm sorry I didn't have time to dig throu
EV2 type=09
params=10 22 01 11 05 FA 47 4F 4F 44 00 00 00 00 00 00 00
Ah I recognize this! :-)
If I'm not mistaken the battery level is 0x22 so should be 34 %
And the light 0x0111 so 273 lux (which seems correct to me).
--
Julien Danjou
# Free Software hacker
On Wed, Aug 28 2013, Peter Wu wrote:
> On Tuesday 27 August 2013 23:08:07 Julien Danjou wrote:
>> >> I still the light meter I had implemented back then (don't know why it's
>> >
>> > "light meter"? You mean the current lux value? Where shoul
ome over-scaped strings in
> http://julien.danjou.info/blog/2012/logitech-k750-linux-support (#include
> <...>)
Thanks I'll fix it. :)
--
Julien Danjou
/* Free Software hacker * independent consultant
http://julien.danjou.info */
signature.asc
Description: PGP signature
___
On Fri, Jul 26 2013, Julien Danjou wrote:
> Does that release fixes the various regression on the HID++ protocol?
> Most of the code I provided for the K750 keyboard and others devices has
> been broken since the code refactor happened some months ago…
It doesn't fix the K750 co
fix uninit var
> - hidpp: fix properties for unreachable devices
> - hidpp: remove unnecessary HID++ 2.0 code
Awesome, that fixed the problem!
I'll test the whole patchset again next week when I'll regain access to
my K750 keyboard.
--
Julien Danjou
-- Free Software hacke
On Thu, Aug 15 2013, Julien Danjou wrote:
> I've tested the whole patch series, and it works fine. It actually seems
> to fix a small issue I had with the assocaited devices being marked as
> present while not. The hardware I had under the hand (literally) to test
> was a M
ally judge code, I didn't touch this for a year and it has
been majorly rewritten since then).
So +2 from me,
--
Julien Danjou
/* Free Software hacker * freelance consultant
http://julien.danjou.info */
signature.asc
Description: PGP signature
_
en since the code refactor happened some months ago…
--
Julien Danjou
-- Free Software hacker - freelance consultant
-- http://julien.danjou.info
signature.asc
Description: PGP signature
___
devkit-devel mailing list
devkit-devel@lists.freedesktop.org
h
On Thu, Jan 03 2013, Richard Hughes wrote:
Hi,
> On 3 January 2013 09:58, Julien Danjou wrote:
>> Hehe, that's awesome! I don't think the T620 is supported yet, it seems
>> recent, so it's likely to use HID++ 2.0 for battery status, which I
>> didn'
20 is supported yet, it seems
recent, so it's likely to use HID++ 2.0 for battery status, which I
didn't implement yet. I've the spec and even a mouse device to test
this, but not enough spare time for now.
--
Julien Danjou
// Free Software hacker & freelance
// http://julien.
; Released: 2013-01-02
>
> New Features:
> - Add a Documentation tag to the service file (Matthias Clasen)
> - Add luminosity property (Julien Danjou)
> - Add support for Logitech Unifying devices (Julien Danjou)
>
> Bugfixes:
> - Always return 0 from notify-upower.sh (Rich
On Tue, Oct 30 2012, Bastien Nocera wrote:
> Posting the patch to the upower bugzilla would be immensely more useful.
Sure, sorry! Opened bug #56582.
https://bugs.freedesktop.org/show_bug.cgi?id=56582
Cheers,
--
Julien Danjou
/* Free Software hacker & freelance
epository at:
git://people.freedesktop.org/~jdanjou/upower jd/logitech-unifying
for you to fetch changes up to f2993988290fbc9374217eeb83ff21ba04cf167c:
Add support for Logitech Unifying devices (2012-10-30 11:57:44 +0100)
--------
Julien D
15 matches
Mail list logo
