<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to patches</title><link href="https://sourceforge.net/p/g15tools/patches/" rel="alternate"/><link href="https://sourceforge.net/p/g15tools/patches/feed.atom" rel="self"/><id>https://sourceforge.net/p/g15tools/patches/</id><updated>2015-05-29T13:18:50.760000Z</updated><subtitle>Recent changes to patches</subtitle><entry><title>Continue to work after suspend/resume</title><link href="https://sourceforge.net/p/g15tools/patches/5/" rel="alternate"/><published>2015-05-29T13:18:50.760000Z</published><updated>2015-05-29T13:18:50.760000Z</updated><author><name>Alexander Ponyatykh</name><uri>https://sourceforge.net/u/lazyranma/</uri></author><id>https://sourceforge.netfc826165c8f2b1984a91ac8698855f6bd7379759</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;g15daemon doesn't always recover from suspend/resume and never recovers from keyboard being replugged, despite having code to handle at least replugging. I've made a patch fix that. It does the following:&lt;br /&gt;
1) Changes re_initLibG15() to properly (and always) reset it's internal state.&lt;br /&gt;
2) Makes g15daemon to call re_initLibG15() on every libusb error (was only on ENODEV). &lt;br /&gt;
Please note, that there is a bug in libusb, that periodically makes g15daemon hang after resume. For more information please see this page: &lt;a href="https://bugs.launchpad.net/ubuntu/+source/g15daemon/+bug/1357556" rel="nofollow"&gt;https://bugs.launchpad.net/ubuntu/+source/g15daemon/+bug/1357556&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>G510 media keys support</title><link href="https://sourceforge.net/p/g15tools/patches/4/" rel="alternate"/><published>2011-06-27T06:33:08Z</published><updated>2011-06-27T06:33:08Z</updated><author><name>multitude</name><uri>https://sourceforge.net/u/multitude/</uri></author><id>https://sourceforge.net2eb0fdf77f685cecd1e2c012c26bfc874a4c06de</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Adds media keys support for the G510 keyboard&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Preliminary G510 support</title><link href="https://sourceforge.net/p/g15tools/patches/3/" rel="alternate"/><published>2011-01-05T23:31:35Z</published><updated>2011-01-05T23:31:35Z</updated><author><name>multitude</name><uri>https://sourceforge.net/u/multitude/</uri></author><id>https://sourceforge.neta4028a4e969444905e8c4638d8ec5a6574715e12</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Custom LED colouring, preliminary extra key handling&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Patch for Dell M1730</title><link href="https://sourceforge.net/p/g15tools/patches/2/" rel="alternate"/><published>2008-01-09T23:36:58Z</published><updated>2008-01-09T23:36:58Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.nete317169bde23c48aa60a5ecdf1607d50fc8851b7</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This patch is to identify the "Logitech GamePanel" device on the DELL M1730.&lt;/p&gt;
&lt;p&gt;I'm unsure whether the device (which is integrated) ID is unique to the M1730 or whether Logitech has a generic "GamePanel" device.  I have assumed the latter in naming the device.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>clock plugin</title><link href="https://sourceforge.net/p/g15tools/patches/1/" rel="alternate"/><published>2007-07-26T13:03:45Z</published><updated>2007-07-26T13:03:45Z</updated><author><name>Lars Randers</name><uri>https://sourceforge.net/u/lranders/</uri></author><id>https://sourceforge.net73744840112b83de793aecdecad60909f0c07b63</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Fixed potential crash bug in initfunc if malloc fails to allocate the canvas. Some code cleanups and optimization as well.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>