> 
alan:snip

> > [Jordan:] 
> > Another option besides from the timeout loop in
> > iris_create_hw_context() might be to check I915_PARAM_PXP_STATUS after
> > the context create fails to tweak the debug message.
> alan: Yeah, that is an option - I'm thinking we can add a DBG that reads
> either "PXP context failure expected due not ready" vs
> "Unexpected PXP context failure" 

Hi Jordan, should i proceed this way? (I can repost the UMD patch accordingly)

Reply via email to