Re: Re: [linux-sunxi] Discussion about mainlining the A83T

[ke...@allwinnertech.com]

Hi, ChenYu,

> Kevin, Shuge, do you know if the 2 chips are actually the same?
> 請問 A83T 和 H8 是一樣的晶片嗎? 提供給我們的板子上是印 H8，
> 但告知我們是 A83T 的原型機，讓人不是很有把握。
Yes, I have checked with my hardware colleague.
Some chips of H8 is same as A83T, and others are not.
The chips on the develop boards are same as the A83T, just different mark.


Best Regards,
ke...@allwinnertech.com

From: Chen-Yu Tsai<mailto:w...@csie.org>
Date: 2015-06-15 15:56
To: Simos Xenitellis<mailto:simos.li...@googlemail.com>; Meng 
Zhang<mailto:ke...@allwinnertech.com>; shuge<mailto:sh...@allwinnertech.com>
CC: linux-sunxi<mailto:linux-sunxi@googlegroups.com>
Subject: Re: [linux-sunxi] Discussion about mainlining the A83T
On Sat, Jun 13, 2015 at 5:05 PM, 'Simos Xenitellis' via linux-sunxi
 wrote:
> Hi All!
>
> Recently, several people received developer boards with the A83T SoC.
>
> I have collected information from a few sources and put them on
> https://linux-sunxi.org/User:Simos/H8HomletProtoV20_A83T
>
> The page includes a comparison of modules of the A83T with other A-line SoCs.
> There are high-resolution images of the board.
> In addition, the page has boot messages and also output of commands
> from the pre-installed BR Linux (kernel version: 3.4).

Some facts about the board:

Boot0 is V4.0.0.
DRAM is 1GB DDR3 @ 672 MHz.
eMMC is 8GB (7.32 GiB).
AXP818 is a PMIC & audio codec combo.
AC200 is a audio codec (unused here), TV encoder, ethernet PHY and RTC
4-in-1 chip.
USB0 (OTG) and USB1 (EHCI/OHCI) are routed directly to the 2 USB ports.
That means no actual OTG, only host mode.

The board (and schematics) say this is an H8.
However I won't be removing the heatsink to verify.
I don't recommend it either. It is quite warm just idling.
That said, the A83T has the same packing as the H8 (BGA 345),
though I have not compared the actual pin signals.

Kevin, Shuge, do you know if the 2 chips are actually the same?
請問 A83T 和 H8 是一樣的晶片嗎? 提供給我們的板子上是印 H8，
但告知我們是 A83T 的原型機，讓人不是很有把握。

The board runs a customized Android system.

Not sure if FEL mode or Android fastboot would work on this board.
If not, it's going to be hard to mainline without U-boot support.

UART0 is the 5 pin-out next to the WiFi module and AXP818.
It shares the same pinout as the micro-SD breakout, or the
A80 Optimus. Note that the onboard OS muxes UART0 onto mmc0
instead. :|

ChenYu

> I'ld like to start a thread about the planning of the mainlining of the A83T.
>
> If there are any other topics not directly related to this thread,
> please start a new thread.
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 linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[linux-sunxi] [ANNOUNCE] Allwinner releasing CedarX open source

[ke...@allwinnertech.com]

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:

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.

We hope this is helpful to everyone. If not, please let us know how we can
improve. Thanks!


Best Regards,
kevin.z.m


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 linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[linux-sunxi] Annoucement about Allwinner's CedarX Software Licensing

[ke...@allwinnertech.com]

To better support media codec framework and media player applications, 
Allwinner has
published the newest version of CedarX (Media Codec framework) to github, at 
this url:
https://github.com/allwinner-zh/media-codec

Recently, there have been some questions about CedarX's software licensing. To 
clear up
any misconceptions about Allwinner's support and respect for the open source 
community,
the CedarX media codec framework is now released with full open source code 
under the
LGPL license. Everyone can get the complete source code from github:
https://github.com/allwinner-zh/media-codec.
 With this, we believe Allwinner's CedarX license is fully compiliant and 
resolves concerns
from the community.

On another positive note, with the release of this framework developers can now 
support
media encode and decode with Allwinner's media libraries (hardware module 
implemented
in user space), or the third media library. We believe this is an important 
benefit for developers
who want more freedom to write code for their projects.

We thank the community for working together with us to expand our open source 
support.
 If there are any questions or further requests please don't hesitate to reach 
out to us via
direct channels or via existing mailing lists. We'll do our best to help out.

____
Best Regards,
ke...@allwinnertech.com
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 linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[linux-sunxi] Re: Allwinner GPL violations: definitive proof.

[ke...@allwinnertech.com]

Hi, Luc,

Allwinner is trying to fix the GPL issue taken on Cedarx.
We have release the latest version of cedarx with LGPL. And just close the code 
of Video Engine hardware, the framework and API is opensource.
We will review the code again, to fix the GPL issues still existed. We are 
trying to do better, if you found any GPL issue, please let us know, we will 
fix it and update it ASAP.

About the kernel GPL issue, we are fixing it now, we will update the code to 
open some drivers.
Thanks.

Best Regards.

ke...@allwinnertech.com

From: Luc Verhaegen<mailto:l...@skynet.be>
Date: 2015-02-25 11:55
To: linux-sunxi@googlegroups.com<mailto:linux-sunxi@googlegroups.com>
CC: Meng Zhang<mailto:ke...@allwinnertech.com>; 
sh...@allwinnertech.com<mailto:sh...@allwinnertech.com>
Subject: Allwinner GPL violations: definitive proof.
This was just posted on the allwinner github account:

https://github.com/allwinner-zh/media-codec

This contains:

https://github.com/allwinner-zh/media-codec/blob/master/sunxi-cedarx/LIBRARY/CODEC/VIDEO/DECODER/libvdecoder.so

This binary contains symbols from both ffmpeg (LGPL, but altered/hacked
up) and libVP62 (anti-compiled from java, and taken off the web in
2006). The LGPL forces Allwinner to produce the full and complete source
code of these binaries. How they are going to explain libVP62 to On2
Technologies, now google, is beyond me (cfr.
http://en.wikipedia.org/wiki/VP6)

With all the previous "indiscretions", it was always possible to claim
that there was some chance that Allwinner was not the source of the many
violations. It was always pretty clear that Allwinner was the source,
there were just too many coincidences, the violation was too all
encompassing, and not a single device maker spilled the goods. The fact
that they threw out a kernel tree with most code and all binaries
removed, was, despite being a ludicrous and laughable action, another
very clear sign that Allwinner was indeed the source of these
violations.

Now however, the fact that allwinner posted this very clearly shows that
Allwinner is the source. It is absolutely unequivocal this time round.

To top this off, it is 6 months after the last GPL violation shitstorm.
This puts serious doubts behind the claims that Allwinner truly is
learning and willing to cooperate.

Allwinner, it is very high time to start playing nice. You've been at it
for 4 years now and seem utterly incapable of or unwilling to change.

Luc Verhaegen.
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 linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Re: [linux-sunxi] Allwinner documentation (hardware datasheet, user manual) for A10, A10s, A13, A20, A31, A31s

[ke...@allwinnertech.com]

Hi, Raanan,

About the A80's manual, there is no a clear time now.
We are trying to make it available as soon as possible.



Best Regards,
kevin.z.m


 
From: RFat
Date: 2014-10-06 20:55
To: linux-sunxi@googlegroups.com
CC: hen...@henriknordstrom.net; sh...@allwinnertech.com; ke...@allwinnertech.com
Subject: Re: Re: [linux-sunxi] Allwinner documentation (hardware datasheet, 
user manual) for A10, A10s, A13, A20, A31, A31s
Hi Kevin,

Publishing the user manuals will certainly increase Allwinner's chips 
popularity. 

I was wondering if there is a rough estimate as to when the A80's manual will 
be made available?

Thanks!
Raanan

On Monday, September 29, 2014 12:46:53 PM UTC+3, ke...@allwinnertech.com wrote: 
Hi All,

I have put the documents on github, and the url is 
https://github.com/allwinner-zh/documents.git 
Thanks Simos, Henrik and Luc's suggestion. And other documents will be upated 
to here when released.




Best Regards,
kevin.z.m


 
From: HenrikNordström
Date: 2014-09-29 08:46
To: linux...@googlegroups.com
CC: sh...@allwinnertech.com; Meng Zhang
Subject: Re: [linux-sunxi] Allwinner documentation (hardware datasheet, user 
manual) for A10, A10s, A13, A20, A31, A31s
sön 2014-09-28 klockan 02:18 +0200 skrev Luc Verhaegen:
 
> Why didn't someone from Allwinner send these documents in him/herself?
 
The current person discussion the matter with Allwiner was Simos, who is
part of the linux-sunxi community. Allwinner sent current versions of
the documents to Simos for distribution in the community. What is wrong?
 
Mailing the full set of documents as attachments directly to the
mailinglist is not appropriate. And for some strange and unknown reason
Allwinner do not appear to have a public document archive for this kind
of documents themselves, and seems to only distribute them via email to
their customers when requested.
 
The real question is why AW do not make the documents available in
public themselves, and likewise why they do not have a public git
repository for SDK sources etc (github or elsewhere).
 
Regards
Henrik
 
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 linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Re: [linux-sunxi] Allwinner documentation (hardware datasheet, user manual) for A10, A10s, A13, A20, A31, A31s

[ke...@allwinnertech.com]

Hi All,

I have put the documents on github, and the url is 
https://github.com/allwinner-zh/documents.git
Thanks Simos, Henrik and Luc's suggestion. And other documents will be upated 
to here when released.



Best Regards,
kevin.z.m



From: HenrikNordström
Date: 2014-09-29 08:46
To: linux-sunxi@googlegroups.com
CC: sh...@allwinnertech.com; Meng 
Zhang
Subject: Re: [linux-sunxi] Allwinner documentation (hardware datasheet, user 
manual) for A10, A10s, A13, A20, A31, A31s
sön 2014-09-28 klockan 02:18 +0200 skrev Luc Verhaegen:

> Why didn't someone from Allwinner send these documents in him/herself?

The current person discussion the matter with Allwiner was Simos, who is
part of the linux-sunxi community. Allwinner sent current versions of
the documents to Simos for distribution in the community. What is wrong?

Mailing the full set of documents as attachments directly to the
mailinglist is not appropriate. And for some strange and unknown reason
Allwinner do not appear to have a public document archive for this kind
of documents themselves, and seems to only distribute them via email to
their customers when requested.

The real question is why AW do not make the documents available in
public themselves, and likewise why they do not have a public git
repository for SDK sources etc (github or elsewhere).

Regards
Henrik

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 linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.