All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99843] Geometry Shader - Incorrect Output
Date: Mon, 06 Nov 2017 07:56:40 +0000	[thread overview]
Message-ID: <bug-99843-502-OfcTJ8mfUM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99843-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 332 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=99843

--- Comment #13 from dan@jerber.co.uk ---
Hi,

It is still a problem. I detailed the card in comment 8 (HD 4890). Could you
advise what other information you would need about the GPU?

Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1097 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-11-06  7:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 20:24 [Bug 99843] Geometry Shader - Incorrect Output bugzilla-daemon
2017-02-16 21:13 ` bugzilla-daemon
2017-02-16 22:13 ` bugzilla-daemon
2017-02-16 22:16 ` bugzilla-daemon
2017-02-17 17:00 ` bugzilla-daemon
2017-02-17 17:01 ` bugzilla-daemon
2017-02-17 23:53 ` bugzilla-daemon
2017-02-17 23:55 ` bugzilla-daemon
2017-02-18  6:42 ` bugzilla-daemon
2017-02-18 11:38 ` bugzilla-daemon
2017-02-19 17:46 ` bugzilla-daemon
2017-06-22 17:07 ` bugzilla-daemon
2017-11-01 15:24 ` bugzilla-daemon
2017-11-01 15:30 ` bugzilla-daemon
2017-11-06  7:56 ` bugzilla-daemon [this message]
2017-11-06 10:10 ` bugzilla-daemon
2017-11-06 20:09 ` bugzilla-daemon
2019-09-18 19:22 ` 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-99843-502-OfcTJ8mfUM@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.