Then imagine a benchmark on the C2 that gets to actually use a properly working L2 cache. L2 cache patches put into their u-boot to set it up, but take a look at the linux kernel starting at 3.18 where all the ARM L2 cache patches go in. I'm not convinced the ARM L2 cache is setup properly or perhaps working at all. I have an issue with the C2 beyond the artificially capped clock rate. I want to overclock a beta board because itĮxposes weaknesses in the design or implementation, not because I want a box faster than anyone elses. However, I would like more transparency into the binary blobs, as for me anyway, the fun with theseīoards is making them do things they weren't designed to do (like the old PC hacking days of the 80's). I don't like the ancient kernels (not their fault). Responds, often fixing the issue and where they can't discussing why (thinking of the USB cpu usage issue among others). I have purchased many other vendors boards, typically complaints about defects or not living up to specifications fall on deaf ears. This service includes fixing the manufacturer's kernel, responding to issues, openly discussing problems, etc. We do care for CPU performance though.įor me HK provides a service for their boards that is impressive enough that I keep coming back to get more We install the board, install BOINC and then remote control the BOINC agent, without messing around much with the SBC. While I do appreciate the HK software support, our use case usually doesn't require sophisticated functions, HW, GPU or codec support, etc. When only little or no benchmarks between two A53 based boards available, the outstanding 2GHz CPU becomes a strong selling point for those primarily looking for CPU power. Other people might use their fleet of C2s for distributed rendering, compiling, building hash tables, etc. Of course we want to fully utilize each board and care mostly for the CPU performance before other features. In our team we have some members with dozens of C2s, XU4 and older boards. Different people, different use cases.Īs I wrote in my initial post, I am using my 8 C2s for distributed computing. While some users might not max out the CPU or would benefit from another 4x500MHz, there are users who do. What appears to be the upper limit, 1) to much thermal load or 2) not enough power being able to be supplied to the cores or maybe even the cache? How accurate are the rests of the clocks, ie what frequencies are the caches, ethernet, memory and USB running at? How much thermal load does mali require and what clock speeds are they running (750MHz I believe) at? Im also interested in the following information if are able to provide. Offer a larger heatsink (possibly a fan) for the device. Create a new governor / power module / policy to shutdown cpu's when not required and up frequency on remaining cpu's. Provide a driver for the amlogic crypto module Thanks for your honesty and information on this matter, im very interested in seeing what HK and AML can offerĪs it appears 2GHz is out of the question are hardkernel or Amlogic able to help with any of the following to improve performance of processing the board. 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 |