On Sat, Oct 11, 2014 at 10:31 AM, jacky lau <[email protected]> wrote:
> A big client will buy thousands of chips once. Are there any relation
> between big client and user manual publishing? No. So they don't think it's
> necessary to open their private property. When you are a big client, you are
> VIP, all document and source code is open to you. And if publish all
> technical documentation, competitors will know some technical secret (e.g.
> bug;) they don't want them to know.
> Open world is beautiful, but they will not actively participate if there is
> no return. Why some China soc company publish some documents and source code
> now? I think this is mainly for marketing. But no matter how, VIP priority.

Right now Allwinner is only good for tablets and STBs because
Allwinner supplies turnkey solutions. If documentation were more open
other applications could be developed. If customer can't get software
working for these other applications, they won't buy thousands of
chips. So if Allwinner wants to survive past the end of the tablet fad
they have to start developing these other markets. Otherwise when the
tablet fad is over it will be the end of Allwinner.

You also over estimate the value of "technical secrets".  What is the
point of putting a secret h.264 encode/decode unit on the chip if half
of your customers can't get it working?  Obviously Rockchip knows how
to make h.264 encode/decode since they have a similar unit on their
chip. And so does Freescale, TI, ST, etc. -- there is no big secret in
making h.264 hardware for people familiar with how to do it (hint, it
is an ISO standard).  So by keeping the documentation secret you hide
nothing significant from your competitors and much, much worse -- you
keep your own customers from using the hardware they bought.  Think
about it --- which is more important - hiding something form a
competitor that they probably already know, or getting your customers
to ship and buy more chips?

Bottom line - which one brings cash in the door - secret documentation
or getting as many customers as possible to ship?


>
> 在 2014年10月6日星期一UTC+8下午8时55分30秒,RFat写道:
>>
>> 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, [email protected]
>> 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: [email protected]
>>> CC: [email protected]; 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 [email protected].
> For more options, visit https://groups.google.com/d/optout.



-- 
Jon Smirl
[email protected]

-- 
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.

Reply via email to