On 04/10/2015 09:19 PM, Ben Gamari wrote:
Mario Limonciello mario_limoncie...@dell.com writes:
snip
snip
Is this to say that the issue will be fixed with a BIOS update?
Cheers,
- Ben
From what I have gathered this is expected behavior that won't change. The EC
will intentionally drop
On Wednesday 25 February 2015 21:45:22 Pali Rohár wrote:
On Wednesday 25 February 2015 19:48:55 Mario Limonciello wrote:
On 02/20/2015 02:41 PM, Pali Rohár wrote:
On Friday 20 February 2015 20:56:23 Mario Limonciello
wrote:
resetafter=0 means to never reset (even if driver receive
On 04/10/2015 05:39 PM, Pali Rohár wrote:
On Wednesday 25 February 2015 21:45:22 Pali Rohár wrote:
Hello Mario,
have you patched synaptics driver with some resetafter parameter?
And have some team in dell found reason for invalid packets?
Hi Pali,
The reason was found for the invalid packets
On Saturday 11 April 2015 01:07:03 Mario Limonciello wrote:
On 04/10/2015 05:39 PM, Pali Rohár wrote:
On Wednesday 25 February 2015 21:45:22 Pali Rohár wrote:
Hello Mario,
have you patched synaptics driver with some resetafter
parameter? And have some team in dell found reason for
On 04/10/2015 06:14 PM, Pali Rohár wrote:
On Saturday 11 April 2015 01:07:03 Mario Limonciello wrote:
I could see problem with using older kernels which are in more
stable or LTS distribution versions...
But it is nice that problems are fixes for future 4.0/4.1
versions.
And if you located
Mario Limonciello mario_limoncie...@dell.com writes:
On 04/10/2015 06:14 PM, Pali Rohár wrote:
snip
Can you comment if this is also same problem with invalid packets
on E6440/E7440 machines?
Hi Pali,
snip
The invalid packets on the Exx40 machines I believe is caused by some
behavior
On 03/16/2015 04:07 PM, Benjamin Tissoires wrote:
On Mon, Mar 16, 2015 at 4:57 PM, Jason Ekstrand ja...@jlekstrand.net wrote:
Yes, that's the gist of it.
Mario, you might not have seen the problem because you are not running
wayland and/or libinput. The xorg synaptics driver is much more
On 03/14/2015 02:17 PM, Benjamin Tissoires wrote:
[top posting, sorry]
Jason made some interesting progress today:
with the patch in https://lkml.org/lkml/2015/3/12/149, the sound card
is not switched in the I2S mode and works while the touchpad keeps
using I2C.
It looks like suspend/resume is
On Mon, Mar 16, 2015 at 10:29 AM, Mario Limonciello
mario_limoncie...@dell.com wrote:
On 03/14/2015 02:17 PM, Benjamin Tissoires wrote:
[top posting, sorry]
Jason made some interesting progress today:
with the patch in https://lkml.org/lkml/2015/3/12/149, the sound card
is not switched in
On Mon, Mar 16, 2015 at 7:29 AM, Mario Limonciello
mario_limoncie...@dell.com wrote:
On 03/14/2015 02:17 PM, Benjamin Tissoires wrote:
[top posting, sorry]
Jason made some interesting progress today:
with the patch in https://lkml.org/lkml/2015/3/12/149, the sound card
is not switched in
On Mon, Mar 16, 2015 at 1:50 PM, Mario Limonciello
mario_limoncie...@dell.com wrote:
On 03/16/2015 03:42 PM, Jason Ekstrand wrote:
On Mon, Mar 16, 2015 at 11:50 AM, Mario Limonciello
mario_limoncie...@dell.com wrote:
Thanks,
I'm now running a hacked up kernel that's Torvalds' tree from
On Mon, Mar 16, 2015 at 11:50 AM, Mario Limonciello
mario_limoncie...@dell.com wrote:
On 03/16/2015 12:10 PM, Jason Ekstrand wrote:
On Mon, Mar 16, 2015 at 7:29 AM, Mario Limonciello
mario_limoncie...@dell.com wrote:
It's nothing about the wireless. I swapped it out for an intel card
on
On Mon, Mar 16, 2015 at 4:57 PM, Jason Ekstrand ja...@jlekstrand.net wrote:
On Mon, Mar 16, 2015 at 1:50 PM, Mario Limonciello
mario_limoncie...@dell.com wrote:
On 03/16/2015 03:42 PM, Jason Ekstrand wrote:
On Mon, Mar 16, 2015 at 11:50 AM, Mario Limonciello
mario_limoncie...@dell.com
On 03/16/2015 03:42 PM, Jason Ekstrand wrote:
On Mon, Mar 16, 2015 at 11:50 AM, Mario Limonciello
mario_limoncie...@dell.com wrote:
Thanks,
I'm now running a hacked up kernel that's Torvalds' tree from Saturday
morning (same as before) + a patch from Benjamin to fix the touchpad +
the DSDT hack
On 03/16/2015 12:10 PM, Jason Ekstrand wrote:
On Mon, Mar 16, 2015 at 7:29 AM, Mario Limonciello
mario_limoncie...@dell.com wrote:
It's nothing about the wireless. I swapped it out for an intel card
on day 3 or so.
Yes, I am almost 100% sure that this affects suspend/resume. Prior to
the
[top posting, sorry]
Jason made some interesting progress today:
with the patch in https://lkml.org/lkml/2015/3/12/149, the sound card
is not switched in the I2S mode and works while the touchpad keeps
using I2C.
It looks like suspend/resume is also fixed by that :)
I thought it was worth
On 02/23/2015 06:51 PM, Dmitry Torokhov wrote:
On Sun, Feb 22, 2015 at 05:55:05PM +0100, Pali Rohár wrote:
I am not sure what exactly the issue is... We do need to have the break
code to know when the key is released. We can't go and say that we will
release old key when we detect another key
On 02/23/2015 06:01 PM, Pali Rohár wrote:
On Tuesday 24 February 2015 00:31:52 Mario Limonciello wrote:
For older dell models (some old inspirions and maybe also
latitude) it was possible to use undocumented DELLDIAG interface
(which enter into SMM mode and call some functions) to enable
that
On 02/20/2015 02:41 PM, Pali Rohár wrote:
On Friday 20 February 2015 20:56:23 Mario Limonciello wrote:
resetafter=0 means to never reset (even if driver receive e.g
thousand invalid packets). I think this is very dangerous if
there will be other bugs either in linux driver or some other HW
On Wednesday 25 February 2015 19:48:55 Mario Limonciello wrote:
On 02/20/2015 02:41 PM, Pali Rohár wrote:
On Friday 20 February 2015 20:56:23 Mario Limonciello wrote:
resetafter=0 means to never reset (even if driver receive
e.g thousand invalid packets). I think this is very
dangerous
On Sun, Feb 22, 2015 at 05:55:05PM +0100, Pali Rohár wrote:
On Friday 20 February 2015 22:21:43 Mario Limonciello wrote:
On 02/20/2015 02:41 PM, Pali Rohár wrote:
On Friday 20 February 2015 20:56:23 Mario Limonciello wrote:
I have BIOS version A05 on my E6440 machine. That version
does
On Tuesday 24 February 2015 00:31:52 Mario Limonciello wrote:
On 02/22/2015 10:55 AM, Pali Rohár wrote:
Thank you for information!
Sure, no problem.
Mario, do you know if it is possible to switch keyboard
into mode under which Fn key will send scancode (like Ctrl
or Alt) when
On 02/22/2015 10:55 AM, Pali Rohár wrote:
Thank you for information!
Sure, no problem.
Mario, do you know if it is possible to switch keyboard into
mode under which Fn key will send scancode (like Ctrl or Alt)
when presses, so it could be possible to use any Fn+key
combination for keyboard
On Friday 20 February 2015 20:56:23 Mario Limonciello wrote:
Hi Pali Dmitry,
On 02/20/2015 01:24 PM, Pali Rohár wrote:
On Friday 20 February 2015 19:47:17 Dmitry Torokhov wrote:
Hi Mario,
On Thu, Feb 19, 2015 at 12:16:51PM -0600, Mario Limonciello
wrote:
Can it be related to
On Friday 20 February 2015 22:40:38 Mario Limonciello wrote:
On 02/20/2015 03:31 PM, Benjamin Tissoires wrote:
What is most likely happening is that the synaptics driver
switches the touchpad into the i2c/hid protocol. And yes
Synaptics told us that only a reset re-enables the touchpad
in
On 02/20/2015 02:41 PM, Pali Rohár wrote:
On Friday 20 February 2015 20:56:23 Mario Limonciello wrote:
I have BIOS version A05 on my E6440 machine. That version does
not have problems with repeating keys and my workaround for
ALPS touchpad (which is in mainline tree and -stable trees now)
works
On Fri, Feb 20, 2015 at 4:21 PM, Mario Limonciello
mario_limoncie...@dell.com wrote:
On 02/20/2015 02:41 PM, Pali Rohár wrote:
[snipped]
There is problem with some synaptics touchpad on some laptops
(probably not dell). Windows driver loads own firmware into
synaptics touchpad which use
On 02/20/2015 03:46 PM, Pali Rohár wrote:
On Friday 20 February 2015 22:40:38 Mario Limonciello wrote:
Maybe stupid question, but cannot you call that code which put
sound card into HDA mode from kernel? It could fix problem when
either sound or touchpad is not working...
As I understand
On 02/20/2015 03:31 PM, Benjamin Tissoires wrote:
What is most likely happening is that the synaptics driver switches
the touchpad into the i2c/hid protocol. And yes Synaptics told us that
only a reset re-enables the touchpad in the PS/2 mode.
Kernels 3.11 and later know how to deal with this
Hi Mario,
On Thu, Feb 19, 2015 at 12:16:51PM -0600, Mario Limonciello wrote:
Hi Dmitry,
On 02/19/2015 11:16 AM, Dmitry Torokhov wrote:
What kind of glitch is this? Is there a certain pattern to it? Even if we do
not reset the mouse the logs will be full of error messages.
Thanks.
On Friday 20 February 2015 19:47:17 Dmitry Torokhov wrote:
Hi Mario,
On Thu, Feb 19, 2015 at 12:16:51PM -0600, Mario Limonciello
wrote:
Hi Dmitry,
On 02/19/2015 11:16 AM, Dmitry Torokhov wrote:
What kind of glitch is this? Is there a certain pattern to
it? Even if we do not reset
Hi Pali Dmitry,
On 02/20/2015 01:24 PM, Pali Rohár wrote:
On Friday 20 February 2015 19:47:17 Dmitry Torokhov wrote:
Hi Mario,
On Thu, Feb 19, 2015 at 12:16:51PM -0600, Mario Limonciello
wrote:
Can it be related to ther Dell models (Latitudes with ALPS
touchpad) also sending junk data
Hi Dmitry,
On 02/19/2015 11:16 AM, Dmitry Torokhov wrote:
What kind of glitch is this? Is there a certain pattern to it? Even if we do
not reset the mouse the logs will be full of error messages.
Thanks.
From waveform capture data leaving the touchpad is valid, but when it is resent
Hi Mario,
On Wed, Feb 18, 2015 at 07:43:00PM -0600, Mario Limonciello wrote:
When the touchpad for the Dell XPS 13 is running in PS/2 mode the
EC has a tendency to glitch causing the driver to receive bad data.
This doesn't affect the usage of the touchpad until enough bad data
is received
When the touchpad for the Dell XPS 13 is running in PS/2 mode the
EC has a tendency to glitch causing the driver to receive bad data.
This doesn't affect the usage of the touchpad until enough bad data
is received that causes the driver to reset and freeze.
Signed-off-by: Mario Limonciello
35 matches
Mail list logo
