Hi Kevin,
Am 19.05.2015 um 02:44 schrieb [email protected]:
Hi All,
We're proud to announce a new code release today for CedarX. Before
delving
into the details, I'd like to share some context:
i'm glad to see, that AW tries to make a move in the right direction.
Although steps are not finished.
1. As a growing company, we are doing our best to understand the needs
of the
open source software community. This is a learning process. We're working
with different people across the Linux development community to better
understand best practices.
2. Open source software development is a collaborative process. It works
because people genuinely want to help others improve and be
successful. Some
people are new and others help them learn the ropes over time. We hope
that
this same positive feedback process can be applied to GPL.
With that context, here's an update on our CedarX code release (we welcome
constructive feedback!)
1. New code architecture. Driver has been split into several plugins, one
plugin per video format.
2. GPL-complaint. We have scanned and analyzed the code to ensure that
there
is no GPL code used or called.
3. Partial CedarX video decoder source code release. MPEG2, MPEG4,
MJPEG, and
H264 drivers source code available.
I wonder, if you guys have ever recognized
http://linux-sunxi.org/VE_Register_guide or
http://linux-sunxi.org/Cedrus from our community wiki.
Most of the registers, that are needed to make the VE (MPEG1/2/4, H264)
work without the recent source code drop or the old binaries, are known
already - figured out by reverse engineering.
So, i wonder, why there are still missing register descriptions. For
example
https://github.com/allwinner-zh/media-codec/blob/master/sunxi-cedarx/SOURCE/vdecoder/include/veregister.h#L193
, which are known to deal with the maf deinterlacer.
We hope this is helpful to everyone. If not, please let us know how we
can improve. Thanks!
Although it's fine and essential to try to resolve the GPL issues by
publishing the source code, another step to help the open source
community will be to complete the register documentation, we already
know in most parts anyway. In addition, there are missing some
schematics about what versions of the VE is used within which SoC and
what registers are available or have been altered. The user manuals are
in genreal a good resource when someone wants to figure out sth about
the registers, but the Video Engine is sadly completely missing there...
Please also read the other thread
https://www.mail-archive.com/[email protected]/msg11469.html
and think about the statements.
------------------------------------------------------------------------
Best Regards,
kevin.z.m
Regards
Andreas
NOTICE: This e-mail and any included attachments are intended only for
the sole use of named and intended recipient (s) only. If you are the
named and intended recipient, please note that the information
contained in this email and its embedded files are confidential and
privileged. If you are neither the intended nor named recipient, you
are hereby notified that any unauthorized review, use, disclosure,
dissemination, distribution, or copying of this communication, or any
of its contents, is strictly prohibited. Please reply to the sender
and destroy the original message and all your records of this message
(whether electronic or otherwise). Furthermore, you should not
disclose to any other person, use, copy or disseminate the contents of
this e-mail and/or the documents accompanying it. --
You received this message because you are subscribed to the Google
Groups "linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
