On Tue, Mar 11, 2014 at 02:08:55PM +0100, Andreas Noever wrote:
> That seems to do it. I was afraid that setting OSDW globally would
> affect other parts (USB?) But that does not seem to be the case.
I think it results in the USB ports coming up in XHCI mode by default,
but we can handle that. T
On Sat, Mar 8, 2014 at 3:40 AM, Matthew Garrett wrote:
> Ok, can you try this one?
>
That seems to do it. I was afraid that setting OSDW globally would
affect other parts (USB?) But that does not seem to be the case.
What is the reason for clearing the PME flag?
Andreas
--
To unsubscribe from t
Ok, can you try this one?
diff --git a/drivers/acpi/acpica/utosi.c b/drivers/acpi/acpica/utosi.c
index 8856bd3..202b4da 100644
--- a/drivers/acpi/acpica/utosi.c
+++ b/drivers/acpi/acpica/utosi.c
@@ -62,6 +62,7 @@ ACPI_MODULE_NAME("utosi")
static struct acpi_interface_info acpi_default_supported_i
On Wed, Mar 05, 2014 at 12:59:54AM +0100, Andreas Noever wrote:
>
> I belive that the patch has the same effect as passing
> acpi_osi=! acpi_osi=Darwin
> to the kernel. The problem with that approach is that it changes the
> firmware behaviour quite a lot. In particular it prevents Linux from
On Tue, Mar 4, 2014 at 1:09 AM, Matthew Garrett wrote:
>
> Actually, turns out there's a much easier way. Can you try this patch?
> I see the Thunderbolt controller after resume, although it doesn't seem
> to be in a working state.
>
> commit 102547d63e2cbbda42a25f650df9a33cf929a385
> Author: Matt
Actually, turns out there's a much easier way. Can you try this patch?
I see the Thunderbolt controller after resume, although it doesn't seem
to be in a working state.
commit 102547d63e2cbbda42a25f650df9a33cf929a385
Author: Matthew Garrett
Date: Mon Mar 3 18:49:28 2014 -0500
ACPI: Suppo
On Fri, Nov 29, 2013 at 02:35:37AM +0100, Andreas Noever wrote:>
> There are still a number of limitations:
> (1) The system must be booted with acpi_osi=Darwin. Otherwise ACPI will cut
> power to the controller.
> (2) After suspend the controller is gone. I think that ACPI thinks that we
> are
On 2 December 2013 18:53, Andreas Noever wrote:
> On Mon, Dec 2, 2013 at 3:51 AM, Daniel J Blueman wrote:
>> On Friday, 29 November 2013 09:40:02 UTC+8, Andreas Noever wrote:
>>
>> Booting with 3.12.2, your patch series, with acpi_osi=Darwin and no
>> thunderbolt devices plugged, I run into this
On Friday, 29 November 2013 09:40:02 UTC+8, Andreas Noever wrote:
> Thunderbolt hotplug is supposed to be implemented by the firmware. But Apple's
> firmeware only initializes devices during boot and ignores hotplugged devices.
> This patch series adds a driver for the Intel Cactus Ridge Thunderbo
On Friday, 29 November 2013 09:40:02 UTC+8, Andreas Noever wrote:
> Thunderbolt hotplug is supposed to be implemented by the firmware. But Apple's
> firmeware only initializes devices during boot and ignores hotplugged devices.
> This patch series adds a driver for the Intel Cactus Ridge Thunderbo
Thunderbolt hotplug is supposed to be implemented by the firmware. But Apple's
firmeware only initializes devices during boot and ignores hotplugged devices.
This patch series adds a driver for the Intel Cactus Ridge Thunderbolt
controller. The driver supports hotplug operations of simple (one PCI
11 matches
Mail list logo
