|
| 1 | +Before disabling any content in relation to this takedown notice, GitHub |
| 2 | +- contacted the owners of some or all of the affected repositories to give them an opportunity to [make changes](https://docs.github.com/en/github/site-policy/dmca-takedown-policy#a-how-does-this-actually-work). |
| 3 | +- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice). |
| 4 | + |
| 5 | +To learn about when and why GitHub may process some notices this way, please visit our [README](https://github.com/github/dmca/blob/master/README.md#anatomy-of-a-takedown-notice). |
| 6 | + |
| 7 | +--- |
| 8 | + |
| 9 | +**Are you the copyright holder or authorized to act on the copyright owner's behalf?** |
| 10 | + |
| 11 | +Yes, I am authorized to act on the copyright owner's behalf. |
| 12 | + |
| 13 | +**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?** |
| 14 | + |
| 15 | +YES, |
| 16 | + |
| 17 | +**Please provide the Zendesk ticket number of your previously submitted notice. Zendesk ticket numbers are 7 digit ID numbers located in the subject line or body of your confirmation email.** |
| 18 | + |
| 19 | +1600437 |
| 20 | + |
| 21 | +**Does your claim involve content on GitHub or npm.js?** |
| 22 | + |
| 23 | +GitHub |
| 24 | + |
| 25 | +**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.** |
| 26 | + |
| 27 | +I am an mumber of Beken Corporation, and CEVA, Inc is the copyright owner and Beken Corporation authorized to act on its behalf. |
| 28 | + |
| 29 | +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed. If possible, include a URL to where it is posted online.** |
| 30 | + |
| 31 | +The specific source code (the “Code”), as identified below, is licensed under strict confidentiality terms by Beken from our Licensor, CEVA,Inc., via its wholly owned subsidiary named **RivieraWaves**; our license terms with that Licensor forbid source code distribution and hence the identified Code should not be distributed under the Alios Open Source project. I have confirmed that no-one, or anyone else, has a license from CEVA/RivieraWaves for such distribution. Beken has been authorised by CEVA to pursue this takedown notice on their behalf. |
| 32 | + |
| 33 | +**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.** |
| 34 | + |
| 35 | + Some additional links below which similarly require removal: |
| 36 | +https://github.com/lupyuen/AliOS-Things/tree/master/platform/mcu/bk7231u |
| 37 | +https://github.com/yinglangli/AliOS-Things/tree/master/platform/mcu/bk7231u |
| 38 | +https://github.com/yinglangli/AliOS-Things/tree/rel_3.0.0/platform/mcu/bk7231u |
| 39 | +https://github.com/doodle732/AliOS-Things/tree/master/platform/mcu/bk7231u |
| 40 | +https://github.com/l1d000/dave/tree/master/platform/mcu/bk7231u |
| 41 | + |
| 42 | +**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our Complaints about Anti-Circumvention Technology if you are unsure.** |
| 43 | + |
| 44 | +No |
| 45 | + |
| 46 | +**Have you searched for any forks of the allegedly infringing files or repositories? Each fork is a distinct repository and must be identified separately if you believe it is infringing and wish to have it taken down.** |
| 47 | + |
| 48 | +No |
| 49 | + |
| 50 | +**What would be the best solution for the alleged infringement?** |
| 51 | + |
| 52 | +Reported content must be removed. |
| 53 | + |
| 54 | +#### **Do you have the alleged infringer’s contact information? If so, please provide it.** |
| 55 | + |
| 56 | +NO |
| 57 | + |
| 58 | +#### I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law. |
| 59 | + |
| 60 | +#### I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed. |
| 61 | + |
| 62 | +#### I have taken fair use into consideration. |
| 63 | + |
| 64 | +#### I have read and understand GitHub's Guide to Submitting a DMCA Takedown Notice. |
| 65 | + |
| 66 | +#### **So that we can get back to you, please provide either your telephone number or physical address.** |
| 67 | + |
| 68 | +Address: [private] |
| 69 | + |
| 70 | +#### **Please type your full legal name below to sign this request.** |
| 71 | + |
| 72 | +[private] |
0 commit comments