LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Romano Giannetti <romanol@upcomillas.es>
Cc: Frans Pop <elendil@planet.nl>,
	Stefan Richter <stefanr@s5r6.in-berlin.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Intel 945GM: 2.6.25-rc3 report (with a possible regression)
Date: Fri, 29 Feb 2008 21:14:55 -0800	[thread overview]
Message-ID: <200802292114.55352.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <1204190794.16668.4.camel@pern>

On Thursday, February 28, 2008 1:26 am Romano Giannetti wrote:
> On Wed, 2008-02-27 at 13:32 +0100, Frans Pop wrote:
> > This sounds like that could be a bug I filed recently and which was
> > solved in 2.2.1: http://bugs.freedesktop.org/show_bug.cgi?id=14481.
>
> Yes, it seems the same. I will try as soon as I came around to a way to
> do it.

Good to see we're fixing things for some people at least (re: Stephan's 
message).

> Could this account to the LCD/CRT switching problem to? This is the most
> critical to me, since I can't use the laptop to give presentations. I
> double checked if the key combination is managed in user space, but it
> seems that it did not send ACPI events nor keypresses, so I suspect that
> it is a kernel matter (or BIOS, maybe).

The 2.2.1 release may nor may not affect your LCD/CRT switching, but I know at 
least 2.6.25-rc3 has some ACPI key event reporting issues that may be fixed 
now (at least in the ACPI tree).

Jesse

      parent reply	other threads:[~2008-03-01  5:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 20:09 Romano Giannetti
2008-02-27  0:29 ` Stefan Richter
2008-02-27 12:32   ` Frans Pop
2008-02-27 16:03     ` Stefan Richter
2008-02-28  9:26     ` Romano Giannetti
2008-02-28 15:50       ` Frans Pop
2008-02-28 18:23         ` Romano Giannetti
2008-02-28 18:54           ` Frans Pop
2008-03-01  5:14       ` Jesse Barnes [this message]

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=200802292114.55352.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=elendil@planet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romanol@upcomillas.es \
    --cc=stefanr@s5r6.in-berlin.de \
    --subject='Re: Intel 945GM: 2.6.25-rc3 report (with a possible regression)' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).