public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Timo Hoenig <thoenig-dCxI//HcOdFeoWH0uzbU5w@public.gmane.org>
To: Stelian Pop <stelian-ibX4/ixPftWsTnJN9+BGXg@public.gmane.org>
Cc: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>,
	ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Re: [patch 11/12] new sony_acpi driver
Date: Thu, 03 Mar 2005 11:01:23 +0100	[thread overview]
Message-ID: <1109844083.4866.25.camel@nouse.net> (raw)
In-Reply-To: <20050303094554.GC3346-KwDxFO93HejPHUqn3ntIkQ@public.gmane.org>

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

Hi,

On Thu, 2005-03-03 at 10:45 +0100, Stelian Pop wrote:
[...]
>
>But the discussion here is pretty unrelated. We are talking about
>the implementation not interface, and what Len wants is to remove
>the specific {ibm,toshiba,asus} implementations and make generic ones 
>based on the ACPI stantard.

Ah, OK.  I did not get this before.  Then, we've got a problem.  I mean,
when looking at the different implementations of the drivers it is
obvious that this will  not  work at all.  For example, I'm thinking of
the Toshiba HCI which needs to be polled to get hotkey information...

So, I'd really appreciate to see a comment from Len about his thoughts
which way to go.

>Stelian.

See you,

   -- Timo

..............................................................
Timo Hönig <thoenig at nouse dot net>
..................................................:: gpg ::...
Fingerprint: 0998 0ACA A1D2 2612 4D96 DD8B E03F 084B B305 4066

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-03-03 10:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02 22:37 [patch 11/12] new sony_acpi driver Brown, Len
     [not found] ` <F7DC2337C7631D4386A2DF6E8FB22B3002E2E026-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-03-03  9:27   ` Stelian Pop
     [not found]     ` <20050303092725.GA3346-KwDxFO93HejPHUqn3ntIkQ@public.gmane.org>
2005-03-03  9:34       ` Timo Hoenig
     [not found]         ` <1109842444.4866.16.camel-dCxI//HcOdFeoWH0uzbU5w@public.gmane.org>
2005-03-03  9:45           ` Stelian Pop
     [not found]             ` <20050303094554.GC3346-KwDxFO93HejPHUqn3ntIkQ@public.gmane.org>
2005-03-03 10:01               ` Timo Hoenig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-23  9:53 akpm-3NddpPZAyC0
2005-03-02 19:12 ` Len Brown
2005-03-02 20:53   ` Stelian Pop
     [not found]     ` <20050302205324.GA5486-/EcPb+iqZQprbWk4mQFQhaxOck334EZe@public.gmane.org>
2005-03-03  8:40       ` Timo Hoenig
     [not found]         ` <1109839245.4866.10.camel-dCxI//HcOdFeoWH0uzbU5w@public.gmane.org>
2005-03-03  9:39           ` Stelian Pop
     [not found]             ` <20050303093949.GB3346-KwDxFO93HejPHUqn3ntIkQ@public.gmane.org>
2005-03-03 10:06               ` Timo Hoenig

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=1109844083.4866.25.camel@nouse.net \
    --to=thoenig-dcxi//hcodfeowh0uzbu5w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=akpm-3NddpPZAyC0@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=stelian-ibX4/ixPftWsTnJN9+BGXg@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