Project

General

Profile

Actions

Bug #311

closed

acpica components are using export restricted license

Added by Sevan Janiyan over 12 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
kernel
Start date:
2010-10-07
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:
External Bug:


Related issues

Related to illumos gate - Feature #1621: update acpica code to newer version (Joyent OS-441)ResolvedGordon Ross2011-10-10

Actions
Actions #1

Updated by Albert Lee over 12 years ago

This needs to be brought to attention of the Illumos developers. I think this is technically equivalent to the problem of a missing licence header, because:
  • If we don't accept the terms of the licence currently in the header, we gain no rights from it, but we aren't bound by its terms
  • There is (fortunately) another applicable licence
    It's interesting that FreeBSD doesn't consider it a pressing issue.
Actions #2

Updated by Sevan Janiyan over 12 years ago

whilst acpisrc will take care of inserting the correct license into the source code from the stock acpica source from acpica.org, any fixes in the opensolaris/OI tree would be against the export restricted license version, were does that put us?

Actions #3

Updated by Sevan Janiyan over 12 years ago

Albert Lee wrote:

I think this is technically equivalent to the problem of a missing licence header, because:

It's not though is it, cause the terms are clearly stated at the top of each file.

  • If we don't accept the terms of the licence currently in the header, we gain no rights from it, but we aren't bound by its terms

but you cant turn around & say you don't accept the terms of the license then use the code, you need to replace it, right?

Actions #4

Updated by Albert Lee over 12 years ago

Sevan Janiyan wrote:

whilst acpisrc will take care of inserting the correct license into the source code from the stock acpica source from acpica.org, any fixes in the opensolaris/OI tree would be against the export restricted license version, were does that put us?

I'm not aware of any legal difference between using acpisrc and adding the header by hand, so it's probably not okay to use it if the source we have does differ from the stock Intel acpica. If that is the case, we have a problem on our hands. :(

Actions #5

Updated by Garrett D'Amore over 12 years ago

  • Project changed from OpenIndiana Distribution to illumos gate
  • Target version deleted (oi_148)
Actions #6

Updated by Garrett D'Amore over 12 years ago

  • Category set to kernel
  • Assignee set to Albert Lee

Albert, please take a look at this... if we can legitimately obtain files from somewhere else (or generate them ourselves using Intel provided tools!) that are 100% identical except for the license header, then we need to do that.

That should be done fairly urgently. Please include richlowe and I in any review before you integrate.

Thanks.

Actions #7

Updated by Albert Lee almost 12 years ago

  • Difficulty set to Medium
  • Tags set to needs-triage
Actions #8

Updated by Yuri Pankov over 11 years ago

Can be closed as ACPICA update was integrated?

Actions #9

Updated by Albert Lee about 11 years ago

  • Status changed from New to Resolved

Resolved by putback for #1621.

Actions

Also available in: Atom PDF