Hi!
>From the backtrace, it looks evdev related...?
Oct 4 00:59:47 duo wpa_supplicant[3824]: wlan0: SME: Trying to authenticate
with 00:11:95:05:30:d7 (SSID='pavel' freq=2412 MHz)
Oct 4 00:59:47 duo wpa_supplicant[3824]: wlan0: Trying to associate with
00:11:95:05:30:d7 (SSID='pavel' freq=24
On Fri, Oct 3, 2014 at 2:03 PM, Dmitry Torokhov
wrote:
> Input: driver for Elan I2C/SMbus touchpad
>
> From: Duson Lin
>
> This driver supports Elan I2C/SMbous touchpads found in some laptops and
s/SMbous/SMBus
> also in many Chromebooks.
>
> Signed-off-by: Duson Lin
> Signed-off-by: Dmitry To
Hi Andrew,
On Oct 02 2014 or thereabouts, Andrew Duggan wrote:
> On composite HID devices there may be multiple HID devices on separate
> interfaces, but hid-rmi
> should only bind to the touchpad. Commit
> e19ff99f256aeeff6c07b373e01883b72e049552 simply checked
> that the interface protocol was
[adding devicetree folks...]
On Fri, Oct 03, 2014 at 02:03:57PM -0700, Dmitry Torokhov wrote:
> Hi Duson,
>
> On Tue, Jan 07, 2014 at 11:08:03AM +0800, Duson Lin wrote:
> > This driver adds support for elan i2c/smbus touchpad found on some
> > laptops PC
> >
>
> I was looking at your original pa
Hi Duson,
On Tue, Jan 07, 2014 at 11:08:03AM +0800, Duson Lin wrote:
> This driver adds support for elan i2c/smbus touchpad found on some
> laptops PC
>
I was looking at your original patch together with varous other patchs
for the device in ChromeOS trees and I ended up with the following
versio
Sure, but I would prefer to use my chromium account:
Tested-by: Andrew de los Reyes
On Fri, Oct 3, 2014 at 4:09 AM, Jiri Kosina wrote:
> On Thu, 2 Oct 2014, Andrew de los Reyes wrote:
>
>> I've tested these patches successfully on a Chromebook Pixel with the
>> following devices:
>>
>> - T650 t
Hi,
On 10/03/2014 01:03 PM, Hans de Goede wrote:
> Hi,
>
> On 10/03/2014 12:23 PM, Pali Rohár wrote:
>> On Friday 03 October 2014 12:18:51 Hans de Goede wrote:
On my E6440 machine it somehow working. When driver
doing ps/2 reset keyboard, touchpad and trackstick not
responding.
>>>
On Thu, 2 Oct 2014, Andrew de los Reyes wrote:
> I've tested these patches successfully on a Chromebook Pixel with the
> following devices:
>
> - T650 touchpad
> - TK820 keyboard/touchpad
> - Original WTP touchpad
>
> I also tested a touch mouse and as expected it continued to function
> as a pl
Hi,
On 10/03/2014 12:23 PM, Pali Rohár wrote:
> On Friday 03 October 2014 12:18:51 Hans de Goede wrote:
>>> On my E6440 machine it somehow working. When driver
>>> doing ps/2 reset keyboard, touchpad and trackstick not
>>> responding.
>>
>> Right, but I would expect that to be for only a short per
On Friday 03 October 2014 12:18:51 Hans de Goede wrote:
> > On my E6440 machine it somehow working. When driver
> > doing ps/2 reset keyboard, touchpad and trackstick not
> > responding.
>
> Right, but I would expect that to be for only a short period
> of time, or does the whole reset take a sign
Hi,
On 10/03/2014 12:05 PM, Pali Rohár wrote:
> On Friday 03 October 2014 11:55:52 Hans de Goede wrote:
>> Hi,
>>
>> On 10/03/2014 11:43 AM, Pali Rohár wrote:
>>> For unknown reasons linux psmouse alps driver sometimes
>>> receive totally invalid packet sequences on Dell Latitude
>>> laptops. Acco
On Friday 03 October 2014 11:55:52 Hans de Goede wrote:
> Hi,
>
> On 10/03/2014 11:43 AM, Pali Rohár wrote:
> > For unknown reasons linux psmouse alps driver sometimes
> > receive totally invalid packet sequences on Dell Latitude
> > laptops. According to ALPS HW engineers these invalid
> > packet
Hi,
On 10/03/2014 11:58 AM, Pali Rohár wrote:
> On Friday 03 October 2014 11:51:22 Hans de Goede wrote:
>> Hi,
>>
>> On 10/03/2014 11:43 AM, Pali Rohár wrote:
>>> Sometimes laptops with closed lid receive invalid ALPS
>>> protocol V3 packets with last bit7 set.
>>>
>>> This happens on Dell Latitud
On Friday 03 October 2014 11:51:22 Hans de Goede wrote:
> Hi,
>
> On 10/03/2014 11:43 AM, Pali Rohár wrote:
> > Sometimes laptops with closed lid receive invalid ALPS
> > protocol V3 packets with last bit7 set.
> >
> > This happens on Dell Latitude laptops and it looks like it
> > is BIOS bug. Pr
Hi,
On 10/03/2014 11:43 AM, Pali Rohár wrote:
> For unknown reasons linux psmouse alps driver sometimes receive totally
> invalid
> packet sequences on Dell Latitude laptops. According to ALPS HW engineers
> these
> invalid packets do not come from ALPS devices. So it looks like bug in BIOS
> a
Hi,
On 10/03/2014 11:43 AM, Pali Rohár wrote:
> Sometimes laptops with closed lid receive invalid ALPS protocol V3 packets
> with
> last bit7 set.
>
> This happens on Dell Latitude laptops and it looks like it is BIOS bug.
> Probably
> EC does not correctly split keyboard and touchpad PS/2 data
Hi,
Thanks for working on this!
On 10/03/2014 11:43 AM, Pali Rohár wrote:
> On some systems after starting computer function alps_identify() does not
> detect
> dual ALPS touchpad+trackstick device correctly and detect only touchpad.
>
> Resetting ALPS device before identifiying it fixing this
On some systems after starting computer function alps_identify() does not detect
dual ALPS touchpad+trackstick device correctly and detect only touchpad.
Resetting ALPS device before identifiying it fixing this problem and both parts
touchpad and trackstick are detected.
Signed-off-by: Pali Rohár
Sometimes laptops with closed lid receive invalid ALPS protocol V3 packets with
last bit7 set.
This happens on Dell Latitude laptops and it looks like it is BIOS bug. Probably
EC does not correctly split keyboard and touchpad PS/2 data and when laptop lid
is closed it adds 0xFF packet into touchpa
This patch series trying to fix problems with ALPS dualpoint touchpad on
Dell Latitude laptops which are probably caused by bugs in Dell BIOS.
Reported bugs:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1320022
https://bugs.launc
For unknown reasons linux psmouse alps driver sometimes receive totally invalid
packet sequences on Dell Latitude laptops. According to ALPS HW engineers these
invalid packets do not come from ALPS devices. So it looks like bug in BIOS and
EC incorrectly split keyboard and touchpad PS/2 data when l
21 matches
Mail list logo
