From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: Jonathan Brandmeyer
<jbrandmeyer-ihVZJaRskl1bRRN4PJnoQQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: trackpoint dead after suspend-to-RAM
Date: Thu, 2 Dec 2004 23:11:54 +0100 [thread overview]
Message-ID: <20041202221154.GA19095@hell.org.pl> (raw)
In-Reply-To: <1102018182.9867.15.camel@illuvatar>
Thus wrote Jonathan Brandmeyer:
> The issue appears to be similar to what was discussed in the thread "Re:
> trackpoint dead after S3 suspend" in late November, 2003 on this mailing
> list [1]. The last post in that thread said (with regard to a patch
> reported to at least partially fix the problem), "See l-k to find
> similar code done less ugly way... (I did it yesterday)." Does anyone
> know which patch the poster was referencing?
Ugh, that was finally properly fixed and merged around 2.6.3, so you're
probably facing something different. Please also try with a vanilla kernel.
Best regards,
--
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-02 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 20:09 trackpoint dead after suspend-to-RAM Jonathan Brandmeyer
2004-12-02 22:11 ` Karol Kozimor [this message]
[not found] ` <20041202221154.GA19095-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-12-03 4:59 ` Jonathan Brandmeyer
2004-12-03 4:48 ` ole.rohne-vJEk5272eHo
[not found] ` <yzo653kxa05.fsf-vJEk5272eHo@public.gmane.org>
2004-12-04 4:13 ` Jonathan Brandmeyer
2004-12-04 17:44 ` Jonathan Brandmeyer
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=20041202221154.GA19095@hell.org.pl \
--to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=jbrandmeyer-ihVZJaRskl1bRRN4PJnoQQ@public.gmane.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