I am trying to add the newer Sony Google TV remote, and am looking for some
advice on how to get this implemented. This is my first experience with hid
drivers and multitouch.
Some base info:
Bluetooth only
Keyboard
Multitouch trackpad
Accelerometer
http://discover.store.sony.com/googletv/#remo
si...@mungewell.org wrote:
>> With a little more digging on this I think the issue is down to the
>> default calibration values.
>
>I have further confirmation that this is due to the calibration used
>when
>the dial is presented via the joystick interface. The values in the
>event
>interface are
> With a little more digging on this I think the issue is down to the
> default calibration values.
I have further confirmation that this is due to the calibration used when
the dial is presented via the joystick interface. The values in the event
interface are correct.
See 'joydev_correct()' fro
Benson,
On Fri, Dec 7, 2012 at 3:24 PM, Benson Leung wrote:
> This patch introduces a driver for Cypress All Points Addressable
> I2C Trackpad, including the ones in 2012 Samsung Chromebooks.
I tried this patch out on my ARM Chromebook running a kernel based on 3.8-rc1
(it has a bunch of other l
On Tue, 22 Jan 2013, Brad Tilley wrote:
> See attached. Two dmesgs from the same machine. One from 3.7.3, the
> other from 3.8-rc4 (with a ps2 keyboard). USB keyboards on this machine
> never work with 3.8, but always works with 3.7.
>
> I used an old ps2 keyboard to enter the dm-crypt password
The ThingM blink(1) is an open source hardware USB RGB LED. It contains
an internal EEPROM, allowing to configure up to 12 light patterns. A
light pattern is a RGB color plus a fade time. This driver registers a
LED class instance with additional sysfs attributes to support basic
functions such as
> > The vendor's name is "ThingM" and the product's name is "blink(1)",
> > not "blink".
> > Given that, would you prefer to keep "blink(1)::1234", or would it
> > rather be
> > "thingm-blink1::1234" (avoiding parenthesis)?
> >
> > I ask the same question for the driver name, which is actually
>
On Tue, Jan 22, 2013 at 02:51:08PM +0100, Jiri Kosina wrote:
> On Tue, 22 Jan 2013, Brad Tilley wrote:
>
> > > Could you please provide dmesg output from both working and non-working
> > > case?
> >
> > See attached. Two dmesgs from the same machine. One from 3.7.3, the
> > other from 3.8-rc4 (
On Tue, 22 Jan 2013, Brad Tilley wrote:
> > Could you please provide dmesg output from both working and non-working
> > case?
>
> See attached. Two dmesgs from the same machine. One from 3.7.3, the
> other from 3.8-rc4 (with a ps2 keyboard). USB keyboards on this machine
> never work with 3.8,
On Tue, 22 Jan 2013, Vivien Didelot wrote:
> > > > Shouldn't the name presented in the sys/class/leds directories
> > > > change
> > > > appropriately too?
> > >
> > > The directory name for the device under /sys/class/leds is
> > > "blink(1)::",
> > > where is the last 4 digits of the device se
Hi,
> > > Shouldn't the name presented in the sys/class/leds directories
> > > change
> > > appropriately too?
> >
> > The directory name for the device under /sys/class/leds is
> > "blink(1)::",
> > where is the last 4 digits of the device serial number
> > (the first 4
> > digits are always th
On Tue, 22 Jan 2013, Brad Tilley wrote:
> > > > Here is info from a computer where the keyboard works occasionally at
> > > > boot (about 50% of the time). Users reboot until the keyboard works.
> > > >
> > >
> > > Hmm, this is a USB keyboard so let's CC Jiri in addition to
> > > linux-input...
On Tue, Jan 22, 2013 at 11:23:27AM +0100, Jiri Kosina wrote:
> On Mon, 21 Jan 2013, Dmitry Torokhov wrote:
>
> > > Here is info from a computer where the keyboard works occasionally at
> > > boot (about 50% of the time). Users reboot until the keyboard works.
> > >
> >
> > Hmm, this is a USB key
On Mon, 21 Jan 2013, Vivien Didelot wrote:
> > > +++ b/Documentation/ABI/testing/sysfs-driver-hid-blink1
> > > @@ -0,0 +1,23 @@
> > > +What:/sys/class/leds/blink(1)::/rgb
> > > +Date:January 2013
> > > +Contact: Vivien Didelot
> > > +Description: The ThingM blink(1) is
On Mon, 21 Jan 2013, Dmitry Torokhov wrote:
> > Here is info from a computer where the keyboard works occasionally at
> > boot (about 50% of the time). Users reboot until the keyboard works.
> >
>
> Hmm, this is a USB keyboard so let's CC Jiri in addition to
> linux-input...
Thanks for the repo
On Tue, 22 Jan 2013, Fernando Luis Vázquez Cao wrote:
> Document what the fix-up is does and make it more robust by ensuring
> that it is only applied to the USB interface that corresponds to the
> mouse (sony_report_fixup() is called once per interface during probing).
Applied.
--
Jiri Kosina
On Tue, 22 Jan 2013, Fernando Luis Vazquez Cao wrote:
> > > If possible, I would like to get it backported to 3.7-stable (and
> > > possibly 3.2 stable), since without it a whole family of Sony desktop
> > > computers is unusable under Linux out of the box. Should I do it myself
> > > or do you ha
Hi Alan,
On Mon, Jan 21, 2013 at 11:45:58PM +, Alan Cox wrote:
> From: Brian Swetland
>
> This device is a direct pipe from "hardware" to the input
> event subsystem, allowing us to avoid having to route
> "keypad" style events through an AT keyboard driver (gross!)
>
> As with the other su
Hi,
On Sun, Jan 20, 2013 at 03:58:14, Lars-Peter Clausen wrote:
> Hi,
>
> On 01/18/2013 11:48 AM, Patil, Rachna wrote:
> > From: "Patil, Rachna"
> >
> > Signed-off-by: Patil, Rachna
> > ---
> > .../devicetree/bindings/mfd/ti_am335x_tscadc.txt | 35
> >
> > 1 file cha
19 matches
Mail list logo
