Bug 50247 - [SNB, IVB, VLV] save media VSC regs
Summary: [SNB, IVB, VLV] save media VSC regs
Status: CLOSED WONTFIX
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Daniel Vetter
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-22 14:52 UTC by Jesse Barnes
Modified: 2017-07-24 23:01 UTC (History)
4 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Jesse Barnes 2012-05-22 14:52:54 UTC
Save the registers!

http://dt.igk.intel.com/wa_database/DetailsView/Show?wa_name_id=1280
Comment 1 Chris Wilson 2012-12-05 16:26:18 UTC
What VSC regs?
Comment 2 Ben Widawsky 2013-04-17 18:29:54 UTC
VCS? Jesse, can you post what's actually required since I can't find it in the bspec, and the link doesn't seem to work for me.
Comment 3 Ben Widawsky 2013-04-18 23:11:22 UTC
(In reply to comment #2)
> VCS? Jesse, can you post what's actually required since I can't find it in
> the bspec, and the link doesn't seem to work for me.

The controller for path '/wa_database/DetailsView/Show' was not found or does not implement IController. 
at System.Web.Mvc.DefaultControllerFactory.GetControllerInstance(RequestContext requestContext, Type controllerType) 
at System.Web.Mvc.DefaultControllerFactory.CreateController(RequestContext requestContext, String controllerName) 
at System.Web.Mvc.MvcHandler.ProcessRequestInit(HttpContextBase httpContext, IController& controller, IControllerFactory& factory) 
at System.Web.Mvc.MvcHandler.<>c__DisplayClass6.b__2() 
at System.Web.Mvc.SecurityUtil.<>c__DisplayClassb`1.b__a() 
at System.Web.Mvc.SecurityUtil.ProcessInApplicationTrust[TResult](Func`1 func) 
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() 
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.