On Friday 26 October 2007, Alexey Starikovskiy wrote:
Your cat's Bad address means -EFAULT, according to man errno.
Please apply this patch to see what exactly failed...
[ 1191.471572] ACPI: element[12]-type = 1, expected string
[ 1196.640065] ACPI: element[12]-type = 1, expected string
[
On Fri, 2007-10-26 at 17:41 +0200, Raúl Sánchez Siles wrote:
Hello All:
Some time ago(2007/09/17) I wrote this e-mail:
Raúl Sánchez Siles wrote:
Hello all:
I've searched for a more user related ML, but this is the closest I've
found. I own a Dell inspiron 510m laptop
Hello:
Peter Clifton wrote:
On Fri, 2007-10-26 at 17:41 +0200, Raúl Sánchez Siles wrote:
Hello All:
Some time ago(2007/09/17) I wrote this e-mail:
Raúl Sánchez Siles wrote:
Hello all:
I've searched for a more user related ML, but this is the closest
I've
found. I
Andrey,
Please try the attached patch. I choose to do snprintf() instead of direct copy,
as your previous message showed empty OEM type.
Thanks,
Alex.
Andrey Borzenkov wrote:
On Friday 26 October 2007, Alexey Starikovskiy wrote:
Your cat's Bad address means -EFAULT, according to man errno.
On Saturday 27 October 2007, Alexey Starikovskiy wrote:
Andrey,
Please try the attached patch. I choose to do snprintf() instead of direct
copy, as your previous message showed empty OEM type.
Not quite. Now I get
OEM info:0
while before I got empty string. If I read
On Thu, Oct 25, 2007 at 09:06:22AM -0600, Bjorn Helgaas wrote:
But we really *should* reserve things used by opregions, shouldn't
we? After all, the whole point of resource reservation is to prevent
conflicts.
Only if you're happy to lose functionality like IDE, sadly.
--
Matthew Garrett |
Andrey Borzenkov wrote:
On Saturday 27 October 2007, Alexey Starikovskiy wrote:
Andrey,
Please try the attached patch. I choose to do snprintf() instead of direct
copy, as your previous message showed empty OEM type.
Not quite. Now I get
OEM info:0
Ok, I was hoping to
Hmm. Things seem to have progressed since I was last online :-)
With Alexey's original patch I also get a number of times:
ACPI: element[12]-type = 1, expected string
On Saturday 27 October 2007, Alexey Starikovskiy wrote:
As you wish... :) Please check the attached patch.
With
I am not exactly sure about this one ... what other power_supply class drivers
do? Should I fix HAL instead (but then, I do not know whether HAL is the only
application that is using this interface).
Subject: [PATCH] 2.6.24-rc1: ensure present sysfs attribute even if battery is absent
From:
Andrey Borzenkov wrote:
On Saturday 27 October 2007, Alexey Starikovskiy wrote:
As you wish... :) Please check the attached patch.
Not sure why you need to reimplement acpi_extract_package, but ...
Take a look on memory allocations around it... :)
Tested-by: Andrey Borzenkov [EMAIL
Andrey Borzenkov wrote:
I am not exactly sure about this one ... what other power_supply class
drivers
do? Should I fix HAL instead (but then, I do not know whether HAL is the only
application that is using this interface).
Hm, do you need separate set of properties for that? You could
Ash Milsted wrote:
Hi again,
I just thought I'd say that this is still occuring with the current
linux-acpi-2.6 git tree on top of Linus' latest.. I don't get
(dis)charge uevents and, oddly, the sysfs charge_now value is
As I remember, you did not found uevents in 2.6.23 as well?
initially
On Saturday 27 October 2007, Alexey Starikovskiy wrote:
Andrey Borzenkov wrote:
I am not exactly sure about this one ... what other power_supply class
drivers do? Should I fix HAL instead (but then, I do not know whether HAL
is the only application that is using this interface).
Hm, do
Andrey Borzenkov wrote:
On Saturday 27 October 2007, Alexey Starikovskiy wrote:
Andrey Borzenkov wrote:
I am not exactly sure about this one ... what other power_supply class
drivers do? Should I fix HAL instead (but then, I do not know whether HAL
is the only application that is using this
On Sat, Oct 27, 2007 at 08:54:30PM +0400, Andrey Borzenkov wrote:
I am not exactly sure about this one ... what other power_supply class
drivers
do? Should I fix HAL instead (but then, I do not know whether HAL is the only
application that is using this interface).
Well, PROP_PRESENT
On Sat, 2007-10-27 at 22:42 +0400, Anton Vorontsov wrote:
Well, PROP_PRESENT wasn't my idea, currently it's used by pmu and
olpc drivers becuase it's not trivial to register/unregister their
batteries on physical insertion/removal. I have some plans to teach
at least pmu batteries to not use
On Sat, Oct 27, 2007 at 03:32:04PM -0400, David Woodhouse wrote:
On Sat, 2007-10-27 at 22:42 +0400, Anton Vorontsov wrote:
Well, PROP_PRESENT wasn't my idea, currently it's used by pmu and
olpc drivers becuase it's not trivial to register/unregister their
batteries on physical
Hi,
Currently I'm having two acpi problems on linux.
1. My temperature is reported as -47°C (THRM/temperature).
2. And sometimes the pc is automatically shutdown due to a critical
temperature event (not often).
I've tried to decompile it with iasl and changed some dsdt logic
but I am not able
Bart wrote:
Hi,
Currently I'm having two acpi problems on linux.
1. My temperature is reported as -47°C (THRM/temperature).
2. And sometimes the pc is automatically shutdown due to a critical
temperature event (not often).
First, check if you use lm_sensors.
They work with the same
On Sun, 2007-10-28 at 00:00 +0400, Alexey Starikovskiy wrote:
Bart wrote:
Hi,
Currently I'm having two acpi problems on linux.
1. My temperature is reported as -47°C (THRM/temperature).
2. And sometimes the pc is automatically shutdown due to a critical
temperature event (not
20 matches
Mail list logo
