From: Nicholas Miell <nmiell@comcast.net>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
keith.packard@intel.com, Linux-kernel@vger.kernel.org,
Dirk Hohndel <dirk.hohndel@intel.com>,
Imad Sousou <imad.sousou@intel.com>
Subject: Re: Announcing free software graphics drivers for Intel i965 chipset
Date: Fri, 11 Aug 2006 11:31:03 -0700 [thread overview]
Message-ID: <1155321063.2522.1.camel@entropy> (raw)
In-Reply-To: <81b0412b0608110705y75cd5307vf73dd0b6ee107f81@mail.gmail.com>
On Fri, 2006-08-11 at 16:05 +0200, Alex Riesen wrote:
> On 8/10/06, Nicholas Miell <nmiell@comcast.net> wrote:
> > > > The Intel Open Source Technology Center graphics team is pleased to announce
> > > > the immediate availability of free software drivers for the Intel(r) 965
> > > > Express Chipset family graphics controller. These drivers include support
> > > > for 2D and 3D graphics features for the newest generation Intel graphics
> > > > architecture. The project Web site is http://IntelLinuxGraphics.org.
> > >
> ...
> >
> > More importantly, where's the source to intel_hal.so?
> >
>
> ...and what'd break if the call to intel_hal_set_content_protection is omited?
Where's that call at?
All I saw were intel_hal_wm_pass and intel_hal_recalculate_urb_fence in
Mesa, both of which appear to be strictly optimizations.
--
Nicholas Miell <nmiell@comcast.net>
next prev parent reply other threads:[~2006-08-11 18:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 19:31 Announcing free software graphics drivers for Intel i965 chipset Keith Packard
2006-08-10 6:08 ` Jeff Garzik
2006-08-10 6:21 ` Nicholas Miell
2006-08-11 14:05 ` Alex Riesen
2006-08-11 18:31 ` Nicholas Miell [this message]
2006-08-11 23:42 ` Alex Riesen
2006-08-14 9:49 ` Alex Riesen
2006-08-12 7:31 ` Keith Packard
2006-08-10 7:15 ` Keith Packard
2006-08-10 7:26 ` Jeff Garzik
2006-08-10 7:48 ` Keith Packard
-- strict thread matches above, loose matches on Subject: below --
2006-08-09 19:43 Keith Packard
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=1155321063.2522.1.camel@entropy \
--to=nmiell@comcast.net \
--cc=Linux-kernel@vger.kernel.org \
--cc=dirk.hohndel@intel.com \
--cc=imad.sousou@intel.com \
--cc=jeff@garzik.org \
--cc=keith.packard@intel.com \
--cc=raa.lkml@gmail.com \
/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.