-sapphire-remote (7.1-1) UNRELEASED; urgency=medium
+sapphire-remote (7.2-1) UNRELEASED; urgency=medium
* New upstream release
+ * Remove patch move_rmmod.diff as it has been merged upstream.
- -- Andrew Ruthven <andrew@etc.gen.nz> Sat, 16 Feb 2019 07:19:10 +0000
+ -- Andrew Ruthven <andrew@etc.gen.nz> Wed, 20 Feb 2019 09:28:10 +0000
-sapphire-remote (6.6-1) stable; urgency=low
+sapphire-remote (7.1-1) unstable; urgency=medium
+
+ * New upstream release
+
+ -- Andrew Ruthven <andrew@etc.gen.nz> Tue, 19 Feb 2019 08:19:10 +0000
+
+sapphire-remote (6.6-1) unstable; urgency=low
* Automatically packaged by DKMS.
+++ /dev/null
-By leaving hid_topseed running, we can see what devices it had
-bound, then move them over to sapphire.
-
-I was running into a problem where after unloading hid_topseed,
-when I loaded sapphire the remote wasn't being registered
-with sapphire until I unplugged it and plugged it back it.
---- a/sapphire_startup.sh
-+++ b/sapphire_startup.sh
-@@ -8,8 +8,9 @@
- #
- TOPSEED=/sys/bus/hid/drivers/topseed
- SAPPHIRE=/sys/bus/hid/drivers/sapphire
--rmmod hid-topseed &>/dev/null
- modprobe sapphire &>/dev/null
-+
-+# Move any devices bound to hid-topseed over to sapphire.
- if [ -d $SAPPHIRE -a -e $TOPSEED/unbind ]; then
- cd $TOPSEED
- for dev in [0-9]*[-0-9A-F] ; do
-@@ -19,6 +20,8 @@
- fi
- done
- fi
-+
-+rmmod hid-topseed &>/dev/null
- #
- # Ubuntu/Mint kernels (and likely others too) don't like it
- # when we unload and reload the sapphire driver.