[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4effccadf47be8ed42ec057bfc84d586.squirrel@intranet.cs.nmsu.edu>
Date: Wed, 19 Aug 2009 12:26:52 -0600
From: "Rick L. Vinyard, Jr." <rvinyard@...nmsu.edu>
To: "Greg KH" <greg@...ah.com>
Cc: "Alan Cox" <alan@...rguk.ukuu.org.uk>,
"Linux USB" <linux-usb@...r.kernel.org>,
"LKML" <linux-kernel@...r.kernel.org>
Subject: Re: Purpose of parameter in sysfs binary read
Greg KH wrote:
> On Wed, Aug 19, 2009 at 11:41:28AM -0600, Rick L. Vinyard, Jr. wrote:
>> Alan Cox wrote:
>> > On Tue, 18 Aug 2009 09:41:56 -0600
>> > "Rick L. Vinyard, Jr." <rvinyard@...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.
>
> Is the framebuffer a different USB interface? Or are they all
> controlled through the same one?
>
Same USB interface. That's why I was thinking it might not work out. In
fact, it uses the same interrupt pipe as the HID reports.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists