public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Rick L. Vinyard, Jr." <rvinyard@cs.nmsu.edu>
Cc: Jiri Kosina <jkosina@suse.cz>,
	linux-kernel@vger.kernel.org, krzysztof.h1@wp.pl,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-usb@vger.kernel.org, Oliver Neukum <oliver@neukum.org>,
	linux-input@vger.kernel.org
Subject: Re: [PATCH] Logitech G13 driver (fixed cc list --- ignore others)
Date: Mon, 4 Jan 2010 23:48:17 +0100	[thread overview]
Message-ID: <20100104224817.GA21695@elf.ucw.cz> (raw)
In-Reply-To: <7f9100aac5f9b06ec78efff25c7a5a71.squirrel@intranet.cs.nmsu.edu>

Hi!

> > Well, the device is still primarily HID device in its nature, so either
> > keeping the whole driver in drivers/hid, or separating it into two
> > drivers, one for the HID part and second for the framebuffer part should
> > be acceptable.
> 
> The framebuffer part uses the same interrupt endpoint for both HID and
> display. IIRC there were issues with two drivers using the same interrupt
> endpoint.

Ok, but I guess you should cc auxdisplay people in future.

> >> I'd prefer to go without another logo. Just make sure default penguin
> >> gets
> >> there or something.
> >
> > What logo is this, BTW? :)
> 
> It's similar to the default G13 load image, but with tux on the left and
> the GNU gnu on the right.
> 
> I tried to particularly clean up tux a bit since the default monochrome
> logo is 80x80 and the display is 160x43.
> 
> The only alternatives I could think of were to use the default logo and
> load it at 80x43 which cuts off Tux at the nipples, resample in the
> driver, or leave the logo off.

Or put something simple&stupid there like checkerboard?

Or just resample penguin -- skipping every second line should not be
particulary hard...
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2010-01-04 22:48 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
2009-12-16 14:08   ` Jiri Kosina
2010-01-04 22:23     ` Rick L. Vinyard, Jr.
2010-01-04 22:48       ` Pavel Machek [this message]
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=20100104224817.GA21695@elf.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