Linux Input/HID development
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Anisse Astier <anisse@astier.eu>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: i8042 - add Dell Vostro 1520 and 1720 to the reset list
Date: Mon, 30 Nov 2009 01:35:44 -0800	[thread overview]
Message-ID: <20091130093544.GH10295@core.coreip.homeip.net> (raw)
In-Reply-To: <20091126110500.735461ac@destiny.ordissimo>

On Thu, Nov 26, 2009 at 11:05:00AM +0100, Anisse Astier wrote:
> Hi Dmitry,
> 
> Sorry for the badly threaded reply, I wasn't subscribed to the list and
> didn't ask explicitely to be Cc-ed.
> 
> >On Wed, 25 Nov 2009 12:17:37 -0800, Dmitry Torokhov wrote:
> >Could youplease explain in more detail what the "bad state" is.
> >And what exactly do you mean by "first boot"? Cold boot? The very
> >first boot after assembling? Something else?
> 
> By bad state I mean that neither touchpad nor keyboard are working. They
> are both unresponsive. You can fix this by adding i8042.reset on the
> kernel command line, or removing the battery and waiting long enough.
> By very first boot I mean when the laptops are received from Dell and
> booted in Linux.
> 
> If you cold boot with a working non-Dell power supply (with same
> electrical characteristics), you can reproduce the "first boot" bug as
> much as you want, and laptops won't work unless you remove the battery
> and wait long enough OR add i8042.reset on the cmdline.
> 

Ok, I see... what about 1320? I did a quick round of googling and it
seem to have the similar issue...

-- 
Dmitry

  reply	other threads:[~2009-11-30  9:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24 14:12 [PATCH] Input: i8042 - add Dell Vostro 1520 and 1720 to the reset list Anisse Astier
2009-11-25 20:17 ` Dmitry Torokhov
2009-11-26 10:05 ` Anisse Astier
2009-11-30  9:35   ` Dmitry Torokhov [this message]
2009-11-30  9:55     ` Anisse Astier

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=20091130093544.GH10295@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=anisse@astier.eu \
    --cc=linux-input@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox