All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Dillinger <bear@sonic.net>
To: linux-input@vger.kernel.org
Subject: Corsair k90 keyboard
Date: Fri, 19 Apr 2013 01:13:35 -0700	[thread overview]
Message-ID: <5170FCAF.9030506@sonic.net> (raw)

Does Corsair cooperate with us when we need technical specs?

I have a Corsair K90 gaming keyboard.  The "standard" keys work,
but the macro keys (there are twelve), the macro record button,
the mode switch button, and the winkey lockout button do not
work.  The LED status light for caps lock works, but the numlock,
scroll lock, macro recording, and mode lock lights do not work.

The keyboard backlighting works, but I can't set the backlighting
light level to either of the other two brightness levels.  As a result
I'm not entirely sure which brightness level it's on now.

Most of the multimedia keys work, but the volume adjustment wheel
doesn't work.

It has two USB connectors and appears to register itself as three
USB devices.  One of these devices is recognized as a keyboard by
the current linux driver.

Three of the macro keys appear to report using the same USB ID as
the (recognized) keyboard, albeit with scan codes not known to the
driver.  They can be I/O mapped using codes from showkey. All
twelve, as well as the winkey lockout and macro-record button,
appear to send signals on the second of the three USB channels.

The third channel is probably supposed to appear as a USB-drive
interface, but it's unrecognized by anything on my system at this
time. I'm betting it appears as a memory device under some
circumstance because the keyboard has 360k of flash memory
for macro storage and the windows driver Corsair provides claims
to be able to load and unload macro profiles to the hard drive.

I want to write a driver (or tweek the driver) to handle this keyboard;
mechanically it's an excellent keyboard to type on, and the macro
keys they intended for gaming would be very handy in many
applications, not least of which would be in an IDE.

Can we get real technical specs from Corsair, or do I need to experiment
with this thing and risk bricking it?

             Ray Dillinger



                 reply	other threads:[~2013-04-19  8:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5170FCAF.9030506@sonic.net \
    --to=bear@sonic.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.