From: "Doran, Mark" <mark.doran@intel.com>
To: "Jamie Lokier" <jamie@shareable.org>
Cc: "Linus Torvalds" <torvalds@osdl.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"Andrew Morton" <akpm@osdl.org>,
"Matt Tolentino" <metolent@snoqualmie.dp.intel.com>,
<linux-kernel@vger.kernel.org>,
"Saxena, Sunil" <sunil.saxena@intel.com>
Subject: RE: [UPDATED PATCH] EFI support for ia32 kernels
Date: Fri, 5 Sep 2003 15:22:50 -0700 [thread overview]
Message-ID: <0448350A99F69145AEACC4B950ECB3260455FE7A@fmsmsx406.fm.intel.com> (raw)
On Friday, September 05, 2003 2:24 PM Jamie Lokier wrote:
> EFI is covered by patents? What are they?
Actually no, there are no patents that I'm aware of that read on EFI.
We made a point of not filing any on the spec. We told everyone we
talked to during the spec's development that we wouldn't file any so
that the spec would end up free of any IP considerations when
complete. This was a deliberate effort to support the goal of
minimizing any potential barriers to adoption of EFI as much as
possible.
The patent license grant is thus in some sense a double coverage
approach...you don't really need a patent license grant since there
aren't any patents that read but to reinforce that you don't need to
worry about patents we give you the grant anyway. This helped make
some corporate entities more comfortable about implementing support
for EFI.
In practice we have required that any feedback or contribution to the
EFI spec or code from third parties that is given to us also comes
without any IP encumbrances. There are a couple of things that I've
been offered that I would like to have included but couldn't in the
end because it would not have been possible to continue telling folks
using the EFI spec that they can do so without concern for IP issues.
Cheers,
Mark.
next reply other threads:[~2003-09-05 22:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 22:22 Doran, Mark [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-05 3:52 Doran, Mark
2003-09-05 21:24 ` Jamie Lokier
2003-09-04 18:07 Tolentino, Matthew E
2003-09-04 18:24 ` Linus Torvalds
2003-09-04 19:30 ` Alan Cox
2003-09-06 4:42 ` Eric W. Biederman
2003-09-02 20:21 Tolentino, Matthew E
2003-09-03 8:25 ` Eric W. Biederman
2003-09-02 20:02 Tolentino, Matthew E
2003-09-04 15:35 ` Eric W. Biederman
2003-09-05 22:00 ` Mark Gross
2003-09-06 4:34 ` Eric W. Biederman
2003-08-29 20:19 Matt Tolentino
2003-08-29 22:29 ` Andrew Morton
2003-08-31 20:24 ` Eric W. Biederman
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=0448350A99F69145AEACC4B950ECB3260455FE7A@fmsmsx406.fm.intel.com \
--to=mark.doran@intel.com \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=metolent@snoqualmie.dp.intel.com \
--cc=sunil.saxena@intel.com \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®