All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 31682] Radeon console output very slow with kms
Date: Tue, 22 Mar 2011 19:14:39 GMT	[thread overview]
Message-ID: <201103221914.p2MJEdFV019174@demeter2.kernel.org> (raw)
In-Reply-To: <bug-31682-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=31682





--- Comment #2 from Kurt Roeckx <kurt@roeckx.be>  2011-03-22 19:14:36 ---
So then see this as a feature request or something.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

  parent reply	other threads:[~2011-03-22 19:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-22 18:30 [Bug 31682] New: Radeon console output very slow with kms bugzilla-daemon
2011-03-22 18:40 ` [Bug 31682] " bugzilla-daemon
2011-03-22 19:14 ` bugzilla-daemon [this message]
2011-08-19 14:26 ` bugzilla-daemon
2011-08-19 14:45 ` bugzilla-daemon
2012-08-20 15:13 ` bugzilla-daemon
2013-11-15 16:06 ` bugzilla-daemon
2013-11-15 16:18 ` 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=201103221914.p2MJEdFV019174@demeter2.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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.