On Thu, 3 May 2012 09:15:23 +0100
Dave Airlie wrote:
> On Tue, May 1, 2012 at 2:33 PM, Alan Cox wrote:
> > From: Alan Cox
> >
> > Add the opregion support and bring us in line with the opregion
> > functionality in the
> > reference driver code. We can't share this with i915 currently because
On Tue, May 1, 2012 at 2:33 PM, Alan Cox wrote:
> From: Alan Cox
>
> Add the opregion support and bring us in line with the opregion functionality
> in the
> reference driver code. We can't share this with i915 currently because there
> are
> hardcoded assumptions about dev_priv etc in both ver
On Thu, 3 May 2012 09:15:23 +0100
Dave Airlie wrote:
> On Tue, May 1, 2012 at 2:33 PM, Alan Cox wrote:
> > From: Alan Cox
> >
> > Add the opregion support and bring us in line with the opregion
> > functionality in the
> > reference driver code. We can't share this with i915 currently because
On Tue, May 1, 2012 at 2:33 PM, Alan Cox wrote:
> From: Alan Cox
>
> Add the opregion support and bring us in line with the opregion functionality
> in the
> reference driver code. We can't share this with i915 currently because there
> are
> hardcoded assumptions about dev_priv etc in both ver
From: Alan Cox
Add the opregion support and bring us in line with the opregion functionality
in the
reference driver code. We can't share this with i915 currently because there are
hardcoded assumptions about dev_priv etc in both versions.
Signed-off-by: Alan Cox
---
drivers/gpu/drm/gma500/M
From: Alan Cox
Add the opregion support and bring us in line with the opregion functionality
in the
reference driver code. We can't share this with i915 currently because there are
hardcoded assumptions about dev_priv etc in both versions.
Signed-off-by: Alan Cox
---
drivers/gpu/drm/gma500/M
