All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor@insightbb.com>
To: "Emmanuel Fusté" <emmanuel.fuste@laposte.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [INPUT] i8042 not detecting AUX port
Date: Thu, 24 May 2007 01:40:05 -0400	[thread overview]
Message-ID: <200705240140.06027.dtor@insightbb.com> (raw)
In-Reply-To: <JIIHGD$2DAB7F59E2B2F7B6E1FB7AF26BA117EB@laposte.net>

On Wednesday 23 May 2007 16:41, Emmanuel Fusté wrote:
> Hi,
> > Hi,
> > 
> > On Tuesday 22 May 2007 18:23, Emmanuel Fusté wrote:
> > > Hello,
> > > 
> > > Just to let you know that since I jumped from 2.6.16 to
> > > 2.6.20.7 and 2.6.21, I need the i8042.noloop option to get the
> > > AUX port detected.
> > > Without this option, the kernel silently omit the AUX port,
> > > only the KBD port is detected.
> > > 
> > > If Dmitry is interested by a debug log, I will recompile a
> > > kernel with i8042.debug support.
> > 
> > You do not need to recompile anymore, just boot with
> i8042.debug. 
> > 
> Ok loglevel=8 and i8042.debug do the trick.
> 

Hmm, it looks like your box does not want to generate interrupts for
loop command. Oh, well... I think the best solution would be to 
automatically set i8042_noloop on your box. Can I please get dmidecode
output?

-- 
Dmitry

  reply	other threads:[~2007-05-24  5:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23 20:41 [INPUT] i8042 not detecting AUX port Emmanuel Fusté
2007-05-24  5:40 ` Dmitry Torokhov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-06-12 22:08 Emmanuel Fusté
2007-05-26 22:00 Emmanuel Fusté
2007-05-25  8:58 Emmanuel Fusté
2007-05-24 20:50 Emmanuel Fusté
2007-05-25  3:10 ` Dmitry Torokhov
2007-05-22 22:23 Emmanuel Fusté
2007-05-23  2:50 ` 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=200705240140.06027.dtor@insightbb.com \
    --to=dtor@insightbb.com \
    --cc=emmanuel.fuste@laposte.net \
    --cc=linux-kernel@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.