![]() ![]() Please accept my sincere apologies for the mistake and kindly understand our situation. But we need to check what we can do first. So we will change the C2 specification in our home page next week as per the test result.Īnd we must consider some compensation for C2 users. I fully agree most people don't like this approach.Īnyway, we know well 1.65Ghz or 1.75Ghz is still very far from the 2Ghz. But we need further stability test too.Īnd yes. If we disable two cores, the SoC can run up to 1.75Ghz probably. Once we will have a test result, we will report it on this thread with update package for further sampling test in early next week. We will run the burnA53 on Ubuntu and the Stress app on Android with 10 set of C2 boards in this weekend (for 48 hours stability test) to make sure it. We've been modifying/testing the B元x code to find a maximum feasible/stable clocks like 1.53Ghz, 1.58Ghz, 1.61Ghz, 1.65Ghz, 1.68Ghz, 1.71Ghz, etc for a couple of weeks.īut 1.65Ghz seems to be the maximum one due to some power and heat issues. But we should detect it earlier in our internal development stage. ![]() The kernel clock frequency 1.75 and 2Ghz do not exist in the B元x blobs. Odroid wrote:Please don't waste your valuable time.Īll the Coretex-A53 based Amlogic SoCs have the same issue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |