mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rick L. Vinyard, Jr." <rvinyard@cs.nmsu.edu>
To: "Linux" <linux-kernel@vger.kernel.org>,
	"Linux Input" <linux-input@vger.kernel.org>,
	"Linux USB" <linux-usb@vger.kernel.org>
Subject: Logitech G13 driver + user-space libraries available
Date: Fri, 11 Dec 2009 10:24:52 -0700	[thread overview]
Message-ID: <d4690bfe19cee0dc8c5355a684fa7e09.squirrel@intranet.cs.nmsu.edu> (raw)

Here's a first look at the G13 driver I've been playing around with:
     git://g13.git.sourceforge.net/gitroot/g13/g13

I've been building the driver out-of-tree and this is my first (untested)
shot at moving it in-tree. There are still a number of things to do (and
clean up) in the driver but it is rather functional.

I'll test it later today and update the repo as necessary, but I thought
I'd throw it out there now.

Here's the repo for the support libraries:
     svn co https://g13.svn.sourceforge.net/svnroot/g13/trunk g13

The Gtk and Gtkmm libs are empty for now, but I have tested the g13 and
g13-cairo libs.

The g13 library uses udev for device discovery and exports many of the
sysfs attributes in a little bit friendlier API. See the 'utilities'
directory and 'examples/g13-draw-checkerboard' for examples of the API.

The g13-cairo library similarly provides an API that bridges the
framebuffer functions of the g13 library with cairo making it a little
more friendly to draw directly on the framebuffer. See
'examples/cairo/g13-cairo-helloworld' for an animated example drawing with
cairo to the g13 framebuffer.

Feedback, comments, critiques and flames are welcome.

---

Rick



             reply	other threads:[~2009-12-11 17:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11 17:24 Rick L. Vinyard, Jr. [this message]
2009-12-11 19:04 ` Greg KH

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=d4690bfe19cee0dc8c5355a684fa7e09.squirrel@intranet.cs.nmsu.edu \
    --to=rvinyard@cs.nmsu.edu \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®