On Wed, 2006-10-25 at 14:40 -0600, Bjorn Helgaas wrote:
> On Friday 22 September 2006 03:14, Zhang Rui wrote:
> > Make ACPI use driver model.
>
> What's happening with this series? It doesn't seem to be in -mm
> yet. Some of this stuff has been kicking around for a year already.
> It'd be nice t
>-Original Message-
>From: Bjorn Helgaas [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, October 25, 2006 4:21 PM
>To: Pallipadi, Venkatesh
>Cc: linux-acpi@vger.kernel.org; linux-ia64@vger.kernel.org
>Subject: Re: ia64 acpi-cpufreq driver
>
>On Monday 23 October 2006 22:46, Pallipadi, Venka
Hi,
On Tue, Oct 10, 2006 at 02:41:03AM +0200, Matthias Hentges wrote:
> I'm the happy user of a shiny new C2D E6600 CPU. While cpufreq works, it
> only offers support for the lowest possible frequency (1596MHz)
That's probably because the BIOS only exposes the lowest and the highest
frequency.
>
Hi,
On Mon, Oct 16, 2006 at 06:50:02AM -0700, Mathew Brown wrote:
> I've successfully gotten CPU frequency scaling working (which I
> tested by looking at the cpu frequency before and during running a
> CPU intensive task). However, there are currently 2 issues:
>
> 1) cat /proc/
On Monday 23 October 2006 22:46, Pallipadi, Venkatesh wrote:
> >Section 8.4.4.1 (_PCT) of the 3.0 ACPI spec says:
> >
> > OSPM performs processor performance transitions by writing
> > the performance state-specific control value to a Performance
> > Control Register (PERF_CTRL).
> >
> >Accordin
On Friday 22 September 2006 03:14, Zhang Rui wrote:
> Make ACPI use driver model.
What's happening with this series? It doesn't seem to be in -mm
yet. Some of this stuff has been kicking around for a year already.
It'd be nice to go forward or give up on the idea.
> Patrick has posted patches o
This driver is for non-hot-pluggable hardware. Therefore, if the hardware
isn't present, we want to return -ENODEV so a module load will fail.
We previously returned "result" from the acpi_bus_register_driver() call.
Registering the driver usually succeeds even if no devices are present,
because
On Wednesday, 25 October 2006 18:35, Alexey Starikovskiy wrote:
> Here is a least intrusive patch by my opinion...
> Just copy pm_disk_mode from pm_ops supplied by platform.
> ACPI sets it to PM_DISK_PLATFORM if it has S4,
> and it should be zero otherwise, patch does not copy it then.
Well, I thi
On Wednesday 25 October 2006 15:07, Pavel Machek wrote:
> Hi!
>
> > > > a generic ACPI driver that exports the _BCL and _BCM method
> > > > implementations via that same interface, so that systems providing
> > > > that will "just work". drivers/acpi/video.c currently exports this
> > > > via /pro
Here is a least intrusive patch by my opinion...
Just copy pm_disk_mode from pm_ops supplied by platform.
ACPI sets it to PM_DISK_PLATFORM if it has S4,
and it should be zero otherwise, patch does not copy it then.
Regards,
Alex.
Yu, Luming wrote:
>> There is a problem with swsuspend and
>Obviously we can "fix" that in the short run by causing
>"platform" to be the
>default. Still, I think swsusp should work regardless of
>whether "platform"
>or "shutdown" is used.
If a platform support ACPI, I guess, we'd better enable
platform S4 by default. Otherwise, sooner or later,
it wi
>
>There is a problem with swsuspend and GPE events.
>Now they are restored from acpi_pm_finish(), which is called only if we
>suspend with "platform" option, what means that if we suspended to disk
>with the default "shutdown" option after resume all the GPEs
>will be disabled.
>This presents us
Hi,
On Wednesday, 25 October 2006 16:42, Alexey Starikovskiy wrote:
> Hi,
>
> There is a problem with swsuspend and GPE events.
> Now they are restored from acpi_pm_finish(), which is called only if we
> suspend with "platform" option, what means that if we suspended to disk
> with the default "s
Hi,
There is a problem with swsuspend and GPE events.
Now they are restored from acpi_pm_finish(), which is called only if we
suspend with "platform" option, what means that if we suspended to disk
with the default "shutdown" option after resume all the GPEs will be disabled.
This presents us with
Hi,
There is a bug in ibm_acpi module, which prevents its clean removal.
This patch fixes the problem by moving setting notify_installed to the right
place.
Thanks,
Alex.
make unload of ibm_acpi right.
From: Alexey Starikovskiy <[EMAIL PROTECTED]>
---
drivers/acpi/ibm_acpi.c |3 +--
1
On Wed, 2006-10-25 at 18:40 +0800, Zhang Rui wrote:
> We won't have such issues if we make ACPI use driver model.
> I've sent out a patch series which throw the legacy ACPI driver model
> away. The patches will be added to -mm tree.
>
> On Sat, 2006-10-21 at 00:55 +0800, Bjorn Helgaas wrote:
> > >
We won't have such issues if we make ACPI use driver model.
I've sent out a patch series which throw the legacy ACPI driver model
away. The patches will be added to -mm tree.
On Sat, 2006-10-21 at 00:55 +0800, Bjorn Helgaas wrote:
> > acpi_bus_register_driver must return -ENODEV when no device wit
Quoting r. Pavel Machek <[EMAIL PROTECTED]>:
> > >
> > > Subject: T60 stops triggering any ACPI events
> > > References : http://lkml.org/lkml/2006/10/4/425
> > > http://lkml.org/lkml/2006/10/16/262
> > > Submitter : "Michael S. Tsirkin" <[EMAIL PROTECTED]>
> > > Status : unkn
On Tue 2006-10-24 17:00:51, Michael S. Tsirkin wrote:
> Quoting r. Adrian Bunk <[EMAIL PROTECTED]>:
> > Subject: 2.6.19-rc2: known unfixed regressions (v3)
> >
> > This email lists some known unfixed regressions in 2.6.19-rc2 compared
> > to 2.6.18 that are not yet fixed Linus' tree.
> >
> > If
Hi!
> > > a generic ACPI driver that exports the _BCL and _BCM method
> > > implementations via that same interface, so that systems providing
> > > that will "just work". drivers/acpi/video.c currently exports this
> > > via /proc/acpi/video/$DEVICE/brightness, which isn't the same as
> > > /sys
20 matches
Mail list logo