From: Chris Wilson <chris@chris-wilson.co.uk>
To: Eric Anholt <eric@anholt.net>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/4] Store the chipset info struct in the PCI match struct, instead of a switch().
Date: Sun, 08 May 2011 08:11:42 +0100 [thread overview]
Message-ID: <b9dded$j1vsng@orsmga002.jf.intel.com> (raw)
In-Reply-To: <1304726935-8428-1-git-send-email-eric@anholt.net>
The PCI matching cleanup is most welcome and that does appear to be the
least invasive method of not sending invalid render programs and commands
to gen7. Bring on the change!
Driver+backend initialisation is a mess, but that is a much larger
patchset...
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2011-05-08 7:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 0:08 [PATCH 1/4] Store the chipset info struct in the PCI match struct, instead of a switch() Eric Anholt
2011-05-07 0:08 ` [PATCH 2/4] Use the existing deviceID -> name mapping in SymTabRec instead of duping it Eric Anholt
2011-05-07 0:08 ` [PATCH 3/4] Remove the static list of PciChipset and construct it from SymTabRec instead Eric Anholt
2011-05-08 5:24 ` Kenneth Graunke
2011-05-07 0:08 ` [PATCH 4/4] Add support for Ivybridge chipset Eric Anholt
2011-05-07 20:17 ` Kenneth Graunke
2011-05-08 7:11 ` Chris Wilson [this message]
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='b9dded$j1vsng@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=eric@anholt.net \
--cc=intel-gfx@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.