Announcement

Collapse
No announcement yet.

Arm's ASTC Encoder Replaces Its Restrictive EULA With Apache 2.0 License

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • bridgman
    replied
    Originally posted by archsway View Post
    As far as I can recall (it's not on their website any more) I never saw any licensing agreement, so I was never authorised to use it...
    Ah yes, that would be a problem

    Leave a comment:


  • archsway
    replied
    Originally posted by bridgman View Post

    Other than not being an open source license, what do you feel is wrong with that text ? IIRC that is also the text that was just removed by the commit discussed here.
    As far as I can recall (it's not on their website any more) I never saw any licensing agreement, so I was never authorised to use it...

    The ASTC encoder at least had a EULA:

    https://github.com/ARM-software/astc...e04/LICENSE.md

    Also, the documentation states:

    The Mali OpenCL SDK v1.1.0 provides developers a framework and series of samples for developing OpenCL 1.1 application on ARM Mali based platforms such as the Mali-T600 family of GPUs.
    A restrictive license for a texture encoder could make sense, but for sample code?

    Leave a comment:


  • bridgman
    replied
    Originally posted by archsway View Post
    Arm don't seem to be very good at sticking a proper license on when releasing code.

    I have their old OpenCL "SDK", which has licence headers which look like this:

    Code:
    /*
    * This confidential and proprietary software may be used only as
    * authorised by a licensing agreement from ARM Limited
    * (C) COPYRIGHT 2013 ARM Limited
    * ALL RIGHTS RESERVED
    * The entire notice above must be reproduced on all authorised
    * copies and copies may only be made to the extent permitted
    * by a licensing agreement from ARM Limited.
    */
    Other than not being an open source license, what do you feel is wrong with that text ? IIRC that is also the text that was just removed by the commit discussed here.

    Leave a comment:


  • frep
    replied
    nice move, arm is with the future of graphics nonetheless.

    Leave a comment:


  • archsway
    replied
    Arm don't seem to be very good at sticking a proper license on when releasing code.

    I have their old OpenCL "SDK", which has licence headers which look like this:

    Code:
    /*
     * This confidential and proprietary software may be used only as
     * authorised by a licensing agreement from ARM Limited
     *    (C) COPYRIGHT 2013 ARM Limited
     *        ALL RIGHTS RESERVED
     * The entire notice above must be reproduced on all authorised
     * copies and copies may only be made to the extent permitted
     * by a licensing agreement from ARM Limited.
     */
    Last edited by archsway; 02-18-2020, 05:14 AM. Reason: Quote "SDK"

    Leave a comment:


  • Remdul
    replied
    @ [email protected]: unknown. It's not given whether the patent was granted (valid) in the first place, nor whether Arm intends to license it to 3rd parties, or if it's just a defensive patent. If anyone has the relevant USPTO number that would be helpful.
    That said, by explicitly re-licensing the encoder from a very restricted (unworkable really) license to Apache 2.0 would probably significantly restrict their ability to litigate. But it all depends on the fine print of the claims in the patent of course. Historically, AFAIK most texture texture compression patents (e.g. S3TC) applied only to hardware decoding, not software encoding (unlike e.g. MP3, in which encoding was patented). This is why Arm's ASTC licensing was regarded as remarkable and unusual.

    Leave a comment:


  • nuetzel
    replied
    Now, if AMD can follow?

    Leave a comment:


  • M@yeulC
    replied
    How's the patent situation?

    Leave a comment:


  • microcode
    replied
    Fekkin finally. They went to all this trouble to make this excellent format, but then hobbled its adoption like this. So many years later, it's supported in a handful of places.

    Leave a comment:


  • Remdul
    replied
    What a pleasant surprise. I suspect Rich Geldreich had something to do with this. Nice work!
    Let's hope this furthers adoption on desktops.

    Leave a comment:

Working...
X