Displaying 5 results from an estimated 5 matches for "has_x".
Did you mean:
has_s
2016 May 30
2
[PATCH 4/4] drm/nouveau/acpi: fix lockup with PCIe runtime PM
...0) and the
> Nvidia one (01:00.0).
>
I agree with Lukas idea that one could/should be checking for nvidia
devices (perhaps in nouveau_dsm_pci_probe() or just before calling it
?).
> The previous detection method would fail in this scenario:
> 1. One device reports support for X and Y (has_x = 1, has_y = 1). Write
> ACPI handle A to nouveau_dsm_priv.dhandle.
> 2. Another device reports support for X only (has_x = 1). Write
> ACPI handle B to nouveau_dsm_priv.dhandle.
> 3. End result: has_x = 1, has_y = 1, dhandle = B. But ACPI handle B
> does not really sup...
2016 May 27
3
[PATCH 4/4] drm/nouveau/acpi: fix lockup with PCIe runtime PM
Hi Peter,
On 24 May 2016 at 23:53, Peter Wu <peter at lekensteyn.nl> wrote:
> Since "PCI: Add runtime PM support for PCIe ports", the parent PCIe port
> can be runtime-suspended which disables power resources via ACPI. This
> is incompatible with DSM, resulting in a GPU device which is still in D3
> and locks up the kernel on resume.
>
> Mirror the behavior of
2016 May 27
0
[PATCH 4/4] drm/nouveau/acpi: fix lockup with PCIe runtime PM
...rts_opt)
+ return;
The reason why later calls override early ones is because some Optimus
laptops have the _DSM method on both the Intel GPU (00:02.0) and the
Nvidia one (01:00.0).
The previous detection method would fail in this scenario:
1. One device reports support for X and Y (has_x = 1, has_y = 1). Write
ACPI handle A to nouveau_dsm_priv.dhandle.
2. Another device reports support for X only (has_x = 1). Write
ACPI handle B to nouveau_dsm_priv.dhandle.
3. End result: has_x = 1, has_y = 1, dhandle = B. But ACPI handle B
does not really support Y!
This is theoretic...
2006 May 23
5
AR Caching and Reflection
When I do this:
term = Term.find(1, :include => :definition)
term.definition.term
Two SQL queries are fired, why?
--
Posted via http://www.ruby-forum.com/.
2016 May 30
0
[PATCH 4/4] drm/nouveau/acpi: fix lockup with PCIe runtime PM
...he WMI
interface for some reason. No idea of Acer has hacked up some drivers to
work with this, outside these models I do not know others that are also
affected by this issue.
> > The previous detection method would fail in this scenario:
> > 1. One device reports support for X and Y (has_x = 1, has_y = 1). Write
> > ACPI handle A to nouveau_dsm_priv.dhandle.
> > 2. Another device reports support for X only (has_x = 1). Write
> > ACPI handle B to nouveau_dsm_priv.dhandle.
> > 3. End result: has_x = 1, has_y = 1, dhandle = B. But ACPI handle B
> >...