From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 32325] New: [radeon] DRM version check only looks at minor number.
Date: Sat, 11 Dec 2010 14:33:16 -0800 (PST) [thread overview]
Message-ID: <bug-32325-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=32325
Summary: [radeon] DRM version check only looks at minor number.
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: rankincj@googlemail.com
Created an attachment (id=41020)
View: https://bugs.freedesktop.org/attachment.cgi?id=41020
Review: https://bugs.freedesktop.org/review?bug=32325&attachment=41020
[PATCH] Enable HyperZ and microtiling for R100 if DRM >= v2.x
I have noticed that Mesa 7.9 prints the following message with a recent 2.6.3x
kernel:
"DRM version 1.6 too old to support HyperZ, disabling."
The reason for this is that the DRM in the 2.6.36 kernel is v2.6:
[drm] Initialized radeon 2.6.0 20080528 for 0000:01:00.0 on minor 0
and Mesa only checks the minor version number. (Assuming that the major version
number is always 1.)
I have attached a patch that will also enable both HyperZ and texture
microtiling(?) on R100 if DRM >= v2.x.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-12-11 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-11 22:33 bugzilla-daemon [this message]
2010-12-11 22:58 ` [Bug 32325] [radeon] DRM version check only looks at minor number bugzilla-daemon
2010-12-12 14:07 ` bugzilla-daemon
2019-09-18 18:40 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-32325-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.