On Fri, Mar 30, 2012 at 11:50:42AM -0700, Ben Widawsky wrote:
> On Thu, 29 Mar 2012 21:31:21 +0200
> Daniel Vetter wrote:
>
> > On Sun, Mar 18, 2012 at 01:39:52PM -0700, Ben Widawsky wrote:
> > > paranoia
> > >
> > > For context support the HW expects the default context to always be
> > > avail
On Thu, 29 Mar 2012 21:31:21 +0200
Daniel Vetter wrote:
> On Sun, Mar 18, 2012 at 01:39:52PM -0700, Ben Widawsky wrote:
> > paranoia
> >
> > For context support the HW expects the default context to always be
> > available as there is no way to shut off HW contexts once turned on
> > (afaics). T
On Fri, Mar 30, 2012 at 09:54:31AM -0700, Jesse Barnes wrote:
> On Sun, 18 Mar 2012 13:39:52 -0700
> Ben Widawsky wrote:
>
> > paranoia
> >
> > For context support the HW expects the default context to always be
> > available as there is no way to shut off HW contexts once turned on
> > (afaics)
On Sun, 18 Mar 2012 13:39:52 -0700
Ben Widawsky wrote:
> paranoia
>
> For context support the HW expects the default context to always be
> available as there is no way to shut off HW contexts once turned on
> (afaics). This is problematic when unloading the driver as we have no
> way to prevent
On Sun, Mar 18, 2012 at 01:39:52PM -0700, Ben Widawsky wrote:
> paranoia
>
> For context support the HW expects the default context to always be
> available as there is no way to shut off HW contexts once turned on
> (afaics). This is problematic when unloading the driver as we have no
> way to pr
paranoia
For context support the HW expects the default context to always be
available as there is no way to shut off HW contexts once turned on
(afaics). This is problematic when unloading the driver as we have no
way to prevent the GPU from expecting the BO to still be present once
unloaded.
Th
