All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Henschel <acpi-1rjuZeEg9oEb1SvskN2V4Q@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] acpi4asus update
Date: Tue, 23 Mar 2004 15:50:48 +0100	[thread overview]
Message-ID: <20040323145048.GA5028@fuchi> (raw)
In-Reply-To: <20040323122735.GA18934-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1429 bytes --]

rehi..

* Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org> [2004-03-23 15:45 +0100]:
> Thus wrote Sebastian Henschel:
> > since i am currently working on a M6800N...
> > seems to work, although i do not see any difference to the unsupported
> > default values before, perhaps brightness. :)
> > what still does not work is the the display switch. when i cat
> > /proc/acpi/asus/disp i get random values like:
> > -583194208
> > -583193696
> > -1007965376
> > -588481760
> > 
> > the key strokes on Fn+F8 are recognized by acpid.
> 
> Hmm, reading the value should not be supported currently and it seems I
> have neglected something (looks like reading an uninitialized value here).
> I'll take a look at this in a couple of hours.
> 
> OTOH, echoing a value (see the current acpi4asus README) to asus/disp
> should switch the displays -- at least I was told it worked on M3700N, and
> M6800N is similar. 

no, nothing happens when echoing values. well, now the machine is gone
and i do not know when i will be able to lay hands on a m6800n again.

> Anyway, if it doesn't, there's not really much more
> (than what's already in the README) I can do. A word from someone at ASUS
> could really help, but you surely know how it looks in the reality...

aight.

thanks,
 sebastian
-- 
::: .O.
::: ..O
::: OOO
::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-03-23 14:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23  0:01 [PATCH] acpi4asus update Karol Kozimor
     [not found] ` <20040323000143.GA13711-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-03-23  9:46   ` Sebastian Henschel
     [not found]     ` <20040323094627.GA3413-5sK/Rx+du8M@public.gmane.org>
2004-03-23 12:27       ` Karol Kozimor
     [not found]         ` <20040323122735.GA18934-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-03-23 14:50           ` Sebastian Henschel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-27 22:13 Karol Kozimor
     [not found] ` <20040127221341.GA19793-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-02-07  7:19   ` Len Brown

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=20040323145048.GA5028@fuchi \
    --to=acpi-1rjuzeeg9oeb1svskn2v4q@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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 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.