<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Dragonboard on Insignificant Bits</title>
    <link>https://bobcopeland.com/blog/tags/dragonboard/</link>
    <description>Recent content in Dragonboard on Insignificant Bits</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 07 Jul 2016 13:20:22 +0000</lastBuildDate>
    <atom:link href="https://bobcopeland.com/blog/tags/dragonboard/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fake clicky</title>
      <link>https://bobcopeland.com/blog/2016/07/fake-clicky/</link>
      <pubDate>Thu, 07 Jul 2016 13:20:22 +0000</pubDate>
       <guid isPermaLink="false">http://bobcopeland.com/blog/?p=2297</guid> 
      <description>&lt;p&gt;In the &lt;a href=&#34;https://bobcopeland.com/blog/2016/06/clicky/&#34;&gt;previous installment&lt;/a&gt; I had opined about the untapped power inside my new mechanical keyboard. I haven&amp;rsquo;t had much time to continue looking into the firmware, but I did find the original source of the firmware tools for a similar product. His &lt;a href=&#34;http://spritesmods.com/?art=rapidisnake&amp;amp;page=1&#34;&gt;blog post&lt;/a&gt; is well worth a read.&lt;/p&gt;
&lt;p&gt;Thus far the new device is performing admirably, but it did come with an unforeseen problem.&lt;/p&gt;
&lt;p&gt;I always have a bunch of computers here at my desk, and so for some time I&amp;rsquo;ve had a physical KVM switch to share a single monitor and input devices among them. This switch has a special USB port on the back just for the keyboard, which it monitors for the double-scroll-lock macro command to switch the display. Unfortunately, said port will not power the new keyboard and also won&amp;rsquo;t work with a hub.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
