Summary: | Inconsistent warnings among DDXen when DRI fails to initialize | ||
---|---|---|---|
Product: | DRI | Reporter: | Adam Jackson <ajax> |
Component: | General | Assignee: | Adam Jackson <ajax> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | minor | ||
Priority: | medium | CC: | mharris |
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
URL: | http://marc.theaimsgroup.com/?l=dri-devel&m=108242198901833&w=2 | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 3116 |
Description
Adam Jackson
2004-07-26 12:55:51 UTC
while i'm at it, audit the libdrm.a code, many failure conditions are only listed as X_INFO. Adding the URL to a comment, so it doesn't get lost: ;o) http://marc.theaimsgroup.com/?l=dri-devel&m=108242198901833&w=2 (I hate the bugzilla URL field) really going to do this, i promise... I have resolved this by making all the "Direct rendering disabled" messages X_WARNING and all the "Direct rendering enabled" messages X_INFO. Ideally, we need to factor some of this stuff out to common code. There is a *LOT* of duplication among the *_dri.c files under programs/Xserver/hw/xfree86/drivers. I'm trying to clean up as much low hanging fruit as I can and got tired of waiting for ajax. :P |
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.