From: Chris Wilson <chris@chris-wilson.co.uk>
To: chris2553@googlemail.com
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Handle the no-interrupts case for UMS by polling
Date: Thu, 10 Feb 2011 20:37:23 +0000 [thread overview]
Message-ID: <1bdc18$ji32t3@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <201102101958.12842.chris2553@googlemail.com>
On Thu, 10 Feb 2011 19:58:12 +0000, Chris Clayton <chris2553@googlemail.com> wrote:
> OK, I haven't raised the bug report yet, but I now know how to create it -
> reboot via kexec which is what I must have done when I built and installed the
> kernel to test your patches. I guess not having booted via the bios is leaving
> the card in an odd state. Do you care any more, please? If you do, I'll open
> the bug report.
Please, I think we left my very small field of expertise so a bug may help
attract the attention of those in the know...
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-02-10 20:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <:201101220935.03623.chris2553@googlemail.com>
2011-01-22 10:11 ` [PATCH] drm/i915: Increase the amount of defense before computing vblank timestamps Chris Wilson
2011-01-22 11:18 ` Chris Clayton
2011-01-22 18:01 ` Chris Wilson
2011-01-23 8:56 ` Chris Clayton
2011-01-23 9:32 ` Chris Clayton
2011-01-23 10:50 ` [PATCH] drm/i915: Disable high-precision vblank timestamping for UMS Chris Wilson
2011-01-23 11:28 ` Chris Clayton
2011-01-23 12:44 ` Chris Wilson
2011-01-23 12:55 ` Chris Clayton
2011-01-23 13:06 ` [PATCH] drm/i915: Handle the no-interrupts case for UMS by polling Chris Wilson
2011-01-23 13:06 ` Chris Wilson
2011-01-23 15:38 ` Chris Clayton
2011-01-23 15:59 ` Chris Wilson
2011-02-10 19:58 ` Chris Clayton
2011-02-10 20:37 ` Chris Wilson [this message]
2011-01-23 10:52 ` [PATCH] drm/i915: Increase the amount of defense before computing vblank timestamps Chris Wilson
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='1bdc18$ji32t3@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=chris2553@googlemail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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.