Re: Userspace ACPI interpreter ( was RE: [ACPI] [RFC] dev_acpi: support for userspace access to acpi)

From: Pavel Machek (pavel_at_suse.cz)
Date: 10/31/04

  • Next message: Adrian Bunk: "RFC: [2.6 patch] ieee1394 cleanup" 
    Date:	Sun, 31 Oct 2004 22:29:14 +0100
To: "Yu, Luming" <luming.yu@intel.com>

    Hi!

    > >> On IA64 platform, ACPI interpreter seems to be mandatory for those
    > >> stuff, but IA32 is not. So, the ram disk is the generic solution
    > >> for loading user space interpreter for boot.
    > >
    > >In two sentences: If you want to play with moving the interpreter
    > >to user-space, please do so, and do it on ia64, so you have to
    > >deal with the interesting problems.
    > >
    > >And this whole thing is a gigantic tangent that is only distracting
    > >attention from the real question at hand, namely, Alex's dev_acpi
    > >patch, which exists today and enables some very interesting new
    > >functionality.
    > >
    >
    > Yes, I agree Alex's dev_acpi is interesting, which could result in
    > the removal of some acpi specific drive such as battery.c, button.c,
    > fan.c, thermal.c .... So, I raised the question of userspace ACPI
    > interpreter. Intuitively, userspace is the right place for interpreter.

    I do not think you want to put thermal/fan into userspace. If you boot
    machine with init=/bin/bash, you should have working system. System
    without fan fail... fast.

    Plus you want to do suspend/resume.
                                                                    Pavel 

    -- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
  • Next message: Adrian Bunk: "RFC: [2.6 patch] ieee1394 cleanup"