On Sun, Jan 30, 2011 at 9:50 PM, Chris Wilson
wrote:
> On Mon, 24 Jan 2011 15:55:27 +, Chris Wilson chris-wilson.co.uk> wrote:
>> For i915 there is a need to invalidate some cached state after resuming or
>> reseting the GPU. This is not quite the same as simply restoring saved
>> state (i.e
On Mon, 31 Jan 2011 06:03:25 +1000, Dave Airlie wrote:
> It seems like an interface we could use, I just wasn't sure how a regression
> fix
> for something in. 38 isn't a revert but requires a whole new interface
> in the core
> drm to fix. Perhaps if you can enlighten me on that I'd be happier.
On Mon, 31 Jan 2011 06:03:25 +1000, Dave Airlie wrote:
> It seems like an interface we could use, I just wasn't sure how a regression
> fix
> for something in. 38 isn't a revert but requires a whole new interface
> in the core
> drm to fix. Perhaps if you can enlighten me on that I'd be happier.
On Sun, Jan 30, 2011 at 9:50 PM, Chris Wilson wrote:
> On Mon, 24 Jan 2011 15:55:27 +, Chris Wilson
> wrote:
>> For i915 there is a need to invalidate some cached state after resuming or
>> reseting the GPU. This is not quite the same as simply restoring saved
>> state (i.e. the standard sus
On Mon, 24 Jan 2011 15:55:27 +, Chris Wilson
wrote:
> For i915 there is a need to invalidate some cached state after resuming or
> reseting the GPU. This is not quite the same as simply restoring saved
> state (i.e. the standard suspend resume method), so do not seem to merit
> reusing the sa
On Mon, 24 Jan 2011 15:55:27 +, Chris Wilson
wrote:
> For i915 there is a need to invalidate some cached state after resuming or
> reseting the GPU. This is not quite the same as simply restoring saved
> state (i.e. the standard suspend resume method), so do not seem to merit
> reusing the sa
At Mon, 24 Jan 2011 15:55:27 +,
Chris Wilson wrote:
>
> For i915 there is a need to invalidate some cached state after resuming or
> reseting the GPU. This is not quite the same as simply restoring saved
> state (i.e. the standard suspend resume method), so do not seem to merit
> reusing the s
For i915 there is a need to invalidate some cached state after resuming or
reseting the GPU. This is not quite the same as simply restoring saved
state (i.e. the standard suspend resume method), so do not seem to merit
reusing the save|restore vfuncs. Instead I propose a
drm_mode_config_reset(
At Mon, 24 Jan 2011 15:55:27 +,
Chris Wilson wrote:
>
> For i915 there is a need to invalidate some cached state after resuming or
> reseting the GPU. This is not quite the same as simply restoring saved
> state (i.e. the standard suspend resume method), so do not seem to merit
> reusing the s
For i915 there is a need to invalidate some cached state after resuming or
reseting the GPU. This is not quite the same as simply restoring saved
state (i.e. the standard suspend resume method), so do not seem to merit
reusing the save|restore vfuncs. Instead I propose a
drm_mode_config_reset(
10 matches
Mail list logo
