On Fri, 07 Dec 2007, Thomas Renninger wrote:
I see the danger of applications misusing this as an interface and
implementing workarounds for unsupported ACPI parts and (this is the
real problem) stop working on the real problems or a proper
implementation.
Exactly. Or causing shadow issues
On Thu, 2007-12-06 at 21:52 -0500, Len Brown wrote:
On Wednesday 28 November 2007 11:28, Thomas Renninger wrote:
On Tue, 2007-11-13 at 19:03 +, Carlos Corbacho wrote:
Alexey,
How about character /dev/ec0?
Yes, that would be fine.
On Tuesday 13 November 2007 18:54:51
On Wednesday 28 November 2007 11:28, Thomas Renninger wrote:
On Tue, 2007-11-13 at 19:03 +, Carlos Corbacho wrote:
Alexey,
How about character /dev/ec0?
Yes, that would be fine.
On Tuesday 13 November 2007 18:54:51 Alexey Starikovskiy wrote:
What is the benefit of having
On Tue, 2007-11-13 at 19:03 +, Carlos Corbacho wrote:
Alexey,
How about character /dev/ec0?
Yes, that would be fine.
On Tuesday 13 November 2007 18:54:51 Alexey Starikovskiy wrote:
What is the benefit of having acer_acpi in userspace, rather than one more
*-laptop in
On Wed, 28 Nov 2007, Alexey Starikovskiy wrote:
Having it as /dev/ec0 should not introduce too many problems...
As long as it is with a debugging intent, and not as a place to plug
userspace drivers at. That would be much too dangerous IMO.
Also, it has much smaller impact than /dev/mem or
Alexey,
I'm considering writing a sysfs interface for the EC registers, and was
wondering if you would be ok with such a patch (before I start work on it)?
I'd like to expose the registers to userspace, as it is already possible to
access the EC registers in userspace via /dev/ports (and quite
Carlos Corbacho wrote:
Alexey,
I'm considering writing a sysfs interface for the EC registers, and was
wondering if you would be ok with such a patch (before I start work on it)?
What do you need that for?
I'd like to expose the registers to userspace, as it is already possible to
access
Alexey Starikovskiy wrote:
Carlos Corbacho wrote:
Alexey,
I'm considering writing a sysfs interface for the EC registers, and
was wondering if you would be ok with such a patch (before I start
work on it)?
What do you need that for?
I'd like to expose the registers to userspace, as it is
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
Carlos Corbacho wrote:
Alexey,
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
Alexey,
How about character /dev/ec0?
Yes, that would be fine.
On Tuesday 13 November 2007 18:54:51 Alexey Starikovskiy wrote:
What is the benefit of having acer_acpi in userspace, rather than one more
*-laptop in /devices/misc?
A debate of would it be easier for me to maintain an in kernel
On Tue, 13 Nov 2007, Carlos Corbacho wrote:
I'm considering writing a sysfs interface for the EC registers, and was
wondering if you would be ok with such a patch (before I start work on it)?
I have exactly such a beast in thinkpad-acpi (using /proc, though),
inherited from ibm-acpi who has
12 matches
Mail list logo
