mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rick L. Vinyard, Jr." <rvinyard@cs.nmsu.edu>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Greg KH" <greg@kroah.com>,
	"Linux USB" <linux-usb@vger.kernel.org>,
	"LKML" <linux-kernel@vger.kernel.org>
Subject: Re: Purpose of parameter in sysfs binary read
Date: Wed, 19 Aug 2009 11:41:28 -0600	[thread overview]
Message-ID: <5ea7c6a46fa1e051d69a302fdc8961ac.squirrel@intranet.cs.nmsu.edu> (raw)
In-Reply-To: <20090819170501.1dbd29a8@lxorguk.ukuu.org.uk>

Alan Cox wrote:
> On Tue, 18 Aug 2009 09:41:56 -0600
> "Rick L. Vinyard, Jr." <rvinyard@cs.nmsu.edu> wrote:
>
>> Greg KH wrote:
>> > On Tue, Aug 18, 2009 at 08:55:29AM -0600, Rick L. Vinyard, Jr. wrote:
>> > What are you using the binary sysfs attribute for?  It should ONLY be
>> > used as a pass-through to and from hardware, with no interpretation by
>> > the kernel at all.
>>
>> It's for the Logitech G13's game panel image (a simple binary bitmap of
>> the pixels).
>>
>> It doesn't do any interpretation... just a few checks on the magic
>> number
>> and size.
>
> If its a bitmap image why not register the device as a framebuffer ?
>

Would that preclude it also being registered as a HID? The primary purpose
of the device is to function as a keypad input.

But, in addition to sending keystroke output you can send a usb control
message to change the backlight color and an interrupt message to load a
bitmap as an image.

The bitmap itself is simple, but requires a specific format. Byte 0 must
be 0x03 followed by 31 bytes of null. The low bit of byte 32 is x,y (0,0)
second high bit is (0,1)... with low bit of byte 33 being (1,0)...




  reply	other threads:[~2009-08-19 17:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18 14:55 Rick L. Vinyard, Jr.
2009-08-18 15:14 ` Greg KH
2009-08-18 15:41   ` Rick L. Vinyard, Jr.
2009-08-18 16:02     ` Greg KH
2009-08-18 17:46       ` Rick L. Vinyard, Jr.
2009-08-19 16:05     ` Alan Cox
2009-08-19 17:41       ` Rick L. Vinyard, Jr. [this message]
2009-08-19 18:11         ` Greg KH
2009-08-19 18:26           ` Rick L. Vinyard, Jr.
2009-08-19 18:19         ` Alan Cox
2009-08-19 18:25           ` Rick L. Vinyard, Jr.
2009-08-19 18:34             ` Alan Cox
2009-11-25 19:19               ` Rick L. Vinyard, Jr.
2009-11-25 20:09                 ` Alan Cox
2009-12-02 17:06                   ` Dynamically attaching fbcon to a framebuffer Rick L. Vinyard, Jr.
2009-08-25 11:36         ` Purpose of parameter in sysfs binary read Pavel Machek
2009-08-18 15:16 ` Alan Stern
2009-08-18 15:43   ` 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=5ea7c6a46fa1e051d69a302fdc8961ac.squirrel@intranet.cs.nmsu.edu \
    --to=rvinyard@cs.nmsu.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --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®