[FFmpeg-devel] [PATCH] Optimization of AMR NB and WB decoders for MIPS

compn tempn at twmi.rr.com
Tue Jun 5 16:00:21 CEST 2012

On Tue, 5 Jun 2012 13:32:52 +0000, Babic, Nedeljko wrote:
>Would it be enough to create texi file (mips.texi for example) in 
>doc folder that has this copyright and list of files on which this 
>copyright is applicable?

if my reading of the notice is correct, then yes, that would be enough
to satisfy its demands. i am not a lawyer, so if someone wants to
verify this by asking fsf or sflc about it, that would be nice.

>I could add what was our targeted CPU architecture for 
>optimization in the same file.
>Regarding targeted devices, for this optimization and 
>optimizations that will be contributed to ffmpeg in the future we 
>are targeting particular CPU architecture. Some optimization are 
>relying more on properties of this architecture and some are 
>relying less (and can be used on most MIPS architectures without 
>degradation in performance), so I am not sure if separate 
>document regarding this is necessary.

ok, i just thought you may have been optimizing for iphone or some other
popular device. optimizing for a whole arch is good too :)


>From: ffmpeg-devel-bounces at ffmpeg.org [ffmpeg-devel-bounces at ffmpeg.org] on behalf of compn [tempn at twmi.rr.com]
>Sent: Monday, June 04, 2012 22:41
>To: ffmpeg-devel at ffmpeg.org
>Subject: Re: [FFmpeg-devel] [PATCH] Optimization of AMR NB and WB decoders for MIPS
>On Mon,  4 Jun 2012 18:02:56 +0200, Nedeljko Babic wrote:
>>+ * Copyright (c) 2012
>>+ *      MIPS Technologies, Inc., California.
>>+ *
>>+ * Redistribution and use in source and binary forms, with or without
>>+ * modification, are permitted provided that the following conditions
>>+ * are met:
>>+ * 1. Redistributions of source code must retain the above copyright
>>+ *    notice, this list of conditions and the following disclaimer.
>>+ * 2. Redistributions in binary form must reproduce the above copyright
>>+ *    notice, this list of conditions and the following disclaimer in the
>>+ *    documentation and/or other materials provided with the distribution.
>if the above is true, you are missing a docs patch. so that
>binary distributors dont each have to rip out this disclaimer and
>insert it into the documentation themselves.
>some other documentation would be nice, maybe some simple table of what
>devices are best served by these optmizations? this isnt a requirement,
>i just thought it would be nice for users to know which (popular)
>devices these work best on.
>ffmpeg-devel mailing list
>ffmpeg-devel at ffmpeg.org
>ffmpeg-devel mailing list
>ffmpeg-devel at ffmpeg.org

More information about the ffmpeg-devel mailing list