public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: Nils Faerber <nils-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	julien.lerouge-GANU6spQydw@public.gmane.org
Subject: Re: ANNOUNCE: Asus ACPI driver v0.22
Date: Thu, 22 May 2003 18:42:51 +0200	[thread overview]
Message-ID: <20030522164251.GA17475@hell.org.pl> (raw)
In-Reply-To: <20030522181941.748c2f71.nils-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>

Thus wrote Nils Faerber:
> OK, I'll have to test if switching screens, especially to and from
> TV-out. Last version prohibited this, I think because the hotkey event
> then went into the asus-ACPI driver instead of some builtin-BIOS code...
> very weird. I'll let you know.

I tested it a couple of hours ago. It seems it still does not work --
strange, especially when the part of the code that handles events is
completely different. I will try to fix it, but not until I implement the
display output switching. Hopefully it will provide a workaround for that
feature.

Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org


-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

      parent reply	other threads:[~2003-05-22 16:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 13:07 ANNOUNCE: Asus ACPI driver v0.22 Karol Kozimor
     [not found] ` <20030522130747.GC12331-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2003-05-22 16:19   ` Nils Faerber
     [not found]     ` <20030522181941.748c2f71.nils-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>
2003-05-22 16:42       ` Karol Kozimor [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=20030522164251.GA17475@hell.org.pl \
    --to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=julien.lerouge-GANU6spQydw@public.gmane.org \
    --cc=nils-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@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