From: Hans de Goede <hdegoede@redhat.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] i8042: Add noloop quirk for Asus X750LN
Date: Fri, 31 Oct 2014 09:21:53 +0100 [thread overview]
Message-ID: <545346A1.3070708@redhat.com> (raw)
In-Reply-To: <20141030183410.GG36444@dtor-ws>
Hi,
On 10/30/2014 07:34 PM, Dmitry Torokhov wrote:
> On Sat, Oct 11, 2014 at 11:35:23AM -0700, Dmitry Torokhov wrote:
>> On Sat, Oct 11, 2014 at 03:09:06PM +0200, Hans de Goede wrote:
>>> Without this the aux port does not get detected, and consequently the touchpad
>>> will not work.
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1110011
>>>
>>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>>
>> Applied, thank you.
>
> Hans,
>
> Do you still have dmidecode for this laptop around?
No I took the necessary identification strings from the dmesg, which is here:
https://bugzilla.redhat.com/attachment.cgi?id=944389
I'll drop you a private mail with the users email address, then you
can get into contact with him directly, I expect him to be willing to
help debug this further.
> Can I see it? I am
> just wondering what part of AUX_LOOP was causing issues. Was it aux
> delivery test or loop test itself?
I was wondering myself, which is why the above dmesg is with:
"dyndbg=file drivers/input/serio/* +p"
But that does not seem to print anything extra ..., is the i8042 code
properly using one of the foo_dbg macro's ?
Regards,
Hans
next prev parent reply other threads:[~2014-10-31 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-11 13:09 [PATCH] i8042: Add noloop quirk for Asus X750LN Hans de Goede
2014-10-11 18:35 ` Dmitry Torokhov
2014-10-30 18:34 ` Dmitry Torokhov
2014-10-31 8:21 ` Hans de Goede [this message]
2014-10-31 8:23 ` Hans de Goede
2014-10-31 16:46 ` Dmitry Torokhov
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=545346A1.3070708@redhat.com \
--to=hdegoede@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.