From: Alexey Starikovskiy <aystarik@gmail.com>
To: trenn@suse.de
Cc: Carlos Corbacho <carlos@strangeworlds.co.uk>,
Alexey Starikovskiy <astarikovskiy@suse.de>,
linux-acpi@vger.kernel.org,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Len Brown <lenb@kernel.org>
Subject: Re: [RFC] EC registers - Adding sysfs interface?
Date: Wed, 28 Nov 2007 21:25:06 +0300 [thread overview]
Message-ID: <474DB282.4050003@gmail.com> (raw)
In-Reply-To: <1196267304.23251.165.camel@queen.suse.de>
Thomas Renninger wrote:
> On Tue, 2007-11-13 at 19:03 +0000, 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 /devices/misc?
>>>
>> A debate of "would it be easier for me to maintain an in kernel driver (if/
>> when I can get it upstream) or a userspace application". At the moment, the
>> idea of a full blown userspace application is just something I'm toying with
>> in my head whilst working on WMI userspace.
>>
>
> I very much like the idea of a general EC debug/devel interface to
> userspace.
> It should be a separate CONFIG, marked "DEBUG", "EXPERIMENTAL" or
> whatever and be per default off.
> It is stupid that everybody who wants to debug a bit on EC registers
> needs to duplicate the IBM EC implementation, this should IMO be moved
> where it belongs to:
> drivers/acpi/ec.c
>
> The question is whether Len will accept/like it, Len?
>
>
Having it as /dev/ec0 should not introduce too many problems...
Also, it has much smaller impact than /dev/mem or /dev/ioport...
Regards,
Alex.
next prev parent reply other threads:[~2007-11-28 18:24 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
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 [this message]
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=474DB282.4050003@gmail.com \
--to=aystarik@gmail.com \
--cc=astarikovskiy@suse.de \
--cc=carlos@strangeworlds.co.uk \
--cc=hmh@hmh.eng.br \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=trenn@suse.de \
/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