From: Pavel Machek <pavel@ucw.cz>
To: "Rick L. Vinyard Jr." <rvinyard@cs.nmsu.edu>
Cc: linux-kernel@vger.kernel.org, krzysztof.h1@wp.pl,
akpm@linux-foundation.org, linux-usb@vger.kernel.org,
oliver@neukum.org, linux-input@vger.kernel.org, jkosina@suse.cz
Subject: Re: [PATCH] Logitech G13 driver (fixed cc list --- ignore others)
Date: Wed, 16 Dec 2009 11:34:23 +0100 [thread overview]
Message-ID: <20091216103423.GE1377@ucw.cz> (raw)
In-Reply-To: <200912142122.nBELMW7d001243@mustang.cs.nmsu.edu>
Hi!
> This is a driver for the Logitech G13 gamepad, and contains three
> key parts. In the USB reports the device identifies itself as a
> HID, and as a result this driver is under the HID framework.
>
> There are two primary sub-components to this driver; an input
> device and a framebuffer device.
>
> Although identified as a HID, the device does not support standard
> HID input messages. As a result, a sub-input device is allocated and
> registered separately in g13_probe(). The raw events are monitored
> and key presses/joystick activity is reported through the input device
> after referencing an indexed keymap.
>
> Additionally, this device contains a 160x43 monochrome LCD display.
> A registered framebuffer device manages this display. The design
> of this portion of the driver was based on the design of the
> hecubafb driver with deferred framebuffer I/O since there is
> no real memory to map.
>
> This patch is against the torvalds/linux-2.6.git tree.
Should this use auxdisplay framework and be located there?
> --- /dev/null
> +++ b/drivers/hid/hid-g13-logo.xbm
> @@ -0,0 +1,75 @@
> +#define g13_lcd_width 160
> +#define g13_lcd_height 43
> +static unsigned char g13_lcd_bits[] = {
> + 0x00, 0x00, 0x07, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
> + 0x00, 0x00, 0x00, 0x28, 0x03, 0x00, 0x40, 0x01, 0x00, 0xc0, 0x3f, 0x00,
> + 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xa1,
> + 0x08, 0x00, 0x08, 0x00, 0x00, 0xe0, 0x7f, 0x00, 0x00, 0x00,
> 0x00, 0x00,
I'd prefer to go without another logo. Just make sure default penguin gets
there or something.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-12-16 10:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 21:22 [PATCH] Logitech G13 driver (fixed cc list --- ignore others) Rick L. Vinyard Jr.
2009-12-14 21:26 ` Rick L. Vinyard, Jr.
2009-12-14 22:02 ` Felipe Balbi
2009-12-14 22:48 ` Rick L. Vinyard, Jr.
2009-12-16 10:34 ` Pavel Machek [this message]
2009-12-16 14:08 ` Jiri Kosina
2010-01-04 22:23 ` Rick L. Vinyard, Jr.
2010-01-04 22:48 ` Pavel Machek
2010-01-05 0:14 ` Jaya Kumar
2010-01-14 21:08 ` Miguel Ojeda
2010-01-14 21:48 ` Rick L. Vinyard, Jr.
2010-01-14 22:34 ` Miguel Ojeda
2010-01-14 23:03 ` Rick L. Vinyard, Jr.
2010-01-14 23:34 ` Miguel Ojeda
2010-01-05 9:52 ` Jiri Kosina
2010-01-04 23:57 ` Jaya Kumar
2010-01-07 15:59 ` Rick L. Vinyard, Jr.
2010-01-08 14:21 ` Giacomo A. Catenazzi
2010-01-08 16:45 ` Rick L. Vinyard, Jr.
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=20091216103423.GE1377@ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=jkosina@suse.cz \
--cc=krzysztof.h1@wp.pl \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=rvinyard@cs.nmsu.edu \
/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