public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlos Corbacho <carlos@strangeworlds.co.uk>
To: Alexey Starikovskiy <astarikovskiy@suse.de>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [RFC] EC registers - Adding sysfs interface?
Date: Tue, 13 Nov 2007 18:49:56 +0000	[thread overview]
Message-ID: <200711131849.56964.carlos@strangeworlds.co.uk> (raw)
In-Reply-To: <4739EFB0.7080507@suse.de>

Alexey,

On Tuesday 13 November 2007 18:40:48 Alexey Starikovskiy wrote:
> I think it is better to do it in file system that allows seek(). So you
> could do with 1 file instead of 256 of them.

Fair enough.

> Carlos, I don't like the idea of 256 files. This will consume too many
> resources and will not bring much value. If you want to have something
> permanent, it should be slim and fast. If we talk about some
> debug/research/RE, do it as you like, but don't ask for submission into
> kernel :)

Two reasons:

1) Yes, the obvious reverse engineering (being well behaved when reading EC 
registers, without doing strange things to ACPI when it also wants to call 
the EC - I've had at least one report where going through /dev/ports on an 
Acer laptop managed to cause the keyboard to lockup, until the system was 
reset).

2) I'm toying with the idea of re-implementing acer_acpi as a userspace 
application (which also requires EC access for certain functions - I don't 
mind poking /dev/ports for the odd bit of reverse engineering, but for any 
other kind of normal usage access to the EC, I really wouldn't want to be 
poking in /dev/ports and tripping over the EC kernel driver).

-Carlos
-- 
E-Mail: carlos@strangeworlds.co.uk
Web: strangeworlds.co.uk
GPG Key ID: 0x23EE722D

  parent reply	other threads:[~2007-11-13 18:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 17:24 [RFC] EC registers - Adding sysfs interface? Carlos Corbacho
2007-11-13 18:40 ` Alexey Starikovskiy
2007-11-13 18:46   ` Alexey Starikovskiy
2007-11-13 18:49   ` Carlos Corbacho [this message]
2007-11-13 18:54     ` Alexey Starikovskiy
2007-11-13 19:03       ` Carlos Corbacho
2007-11-28 16:28         ` Thomas Renninger
2007-11-28 18:25           ` Alexey Starikovskiy
2007-11-28 23:12             ` Henrique de Moraes Holschuh
2007-12-07  2:52           ` Len Brown
2007-12-07  8:53             ` Thomas Renninger
2007-12-10 20:36               ` Henrique de Moraes Holschuh
2007-11-14  2:40 ` Henrique de Moraes Holschuh

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=200711131849.56964.carlos@strangeworlds.co.uk \
    --to=carlos@strangeworlds.co.uk \
    --cc=astarikovskiy@suse.de \
    --cc=linux-acpi@vger.kernel.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