Q&A on ARM’s big.LITTLE

on January 24, 2014
Share open/close
URL Copied.

We’ve recently brought you an inside look at the Exynos 5 Octa and its key technologies that make mobile devices better. Among the technologies we talked about was the ARM’s big.LITTLE™ technology and today we are bringing you a video about the technology in more detail. ARM’s big.LITTLE™ Prodcut Manager, Brian Jeff and Linaro’s CTO, David Rusling got together for a live recording of the most frequently asked questions on big.LITTLE™ on Google+ Hangout.



As the video covers topics in detail, it clocks in at almost a half an hour. Below are the topics they discussed during the video. So if you have any specific questions in mind, just click on the link provided.

1. Should user level code be changed to take advantage of big.LITTLE™? (0:13)

2. When will Google support big.LITTLE™? (0:31)

3. What software needs to be written by silicon partners or ODMs to run big.LITTLE on a platform? (2:13)

4. Why didn’t ARM share a single L2 cache between the big and LITTLE clusters to save area? (5:40)

5. Can the individual cores be scaled for frequency and voltage? (8:47)

6. Does big.LITTLE save enough energy to matter in the system context, e.g. how does it compare to display power, etc? (12:21)

7. What can Linaro do for a Partner who is deploying a big.LITTLE™ SoC? (16:39)

8. Is big.LITTLE useful in the mobile space? (17:57) In enterprise and server applications? (18:30)

9. When will big.LITTLE™ be supported by Microsoft? (23:24)

10. Where can I get big.LITTLE™ software to try it out? (25:08)

This video was originally posted by ARM, Ltd. Please visit ARMFlix (http://www.youtube.com/armflix) for more ARM & Samsung Exynos-based videos.

For more information about Samsung Exynos processor, visit
http://www.samsung.com/exynos or http://twitter.com/samsungexynos


Products > Semiconductors

For any issues related to customer service, please go to Customer Support page for assistance.
For media inquiries, please click Media Contact to move to the form.