From: Keith Packard <keith.packard@intel.com>
To: Nicholas Miell <nmiell@comcast.net>
Cc: keith.packard@intel.com, Jeff Garzik <jeff@garzik.org>,
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: Sat, 12 Aug 2006 00:31:33 -0700 [thread overview]
Message-ID: <1155367893.6386.179.camel@neko.keithp.com> (raw)
In-Reply-To: <1155190917.2349.4.camel@entropy>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
On Wed, 2006-08-09 at 23:21 -0700, Nicholas Miell wrote:
> More importantly, where's the source to intel_hal.so?
This module contains stuff which Intel can't publish in source form,
like Macrovision register stuff and other trade secrets. It's optional,
so if you don't want to use a binary module, you don't get to use code
written by Intel agents for these features. And, we also haven't figured
out how and when to release this binary blob, so there's no way you can
use it today. The driver remains completely functional in the absense of
the binary piece, and in fact has no reduction in functionality from
previous driver releases.
One important note -- the interface for the binary module exists only in
user-mode code which is licensed under the MIT license, not the GPL.
--
keith.packard@intel.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-08-12 7:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 19:31 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
2006-08-11 23:42 ` Alex Riesen
2006-08-14 9:49 ` Alex Riesen
2006-08-12 7:31 ` Keith Packard [this message]
2006-08-10 7:15 ` Keith Packard
2006-08-10 7:26 ` Jeff Garzik
2006-08-10 7:48 ` Keith Packard
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=1155367893.6386.179.camel@neko.keithp.com \
--to=keith.packard@intel.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=dirk.hohndel@intel.com \
--cc=imad.sousou@intel.com \
--cc=jeff@garzik.org \
--cc=nmiell@comcast.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome