China 简体中文 Japan 日本语 United States English
International Office Locations
  HOME    COMMUNITY    BLOGS & FORUMS    Configurable Thoughts
Configurable Thoughts
  • About

    This blog is about everything to do with microprocessors. While we discuss architecture, tools, best practices, new innovations, performance, and system implementation, we also look at software, applications, and the larger industry trends. The processor market is a fascinating place today, and even though it has been around for more than 30 years, it is in many ways just getting started. We would love to hear from you on our blog posts, and please don't hesitate to let us know if you think we are wrong — it does happen occasionally.
  • About the Authors

    Michael Thompson

    At the age of 10 Mike begged his father to get him a computer. Never mind that at the time computers were the size of a large office and cost millions of dollars. Yes, Mike is no spring chicken and he didn’t get the computer, although his father did give him an abacus telling him that it would enable him to use the computer that he already had between his ears, which was not appreciated. Whether it was due to the trauma that resulted from using an abacus or just Mike’s love of anything electronic he has spent the last 30 years or so designing, building, and programming computers, microprocessors, and microcontrollers and developing applications that run on them. And his fascination continues with the definition of new processors and architectures in his search for the holy grail of computing: infinite performance at zero power consumption. Statistically speaking he is convinced it is just a matter of time.

    Henk Hamoen

    For Henk it all started with listening to shortwave radio stations back in the late seventies as a small kid - the sound of music and people far away, beeps of ships on the ocean transmitting their messages in Morse code. Immediately, Henk started to build radios himself, very (very) small systems at that time. Years later Henk found himself designing semiconductor ICs - video processing, modem design, set-top-boxes etc. These were even smaller systems (from a physical perspective) but with so much embedded processing power to play with inside! Today Henk is working on IP and subsystems – creating even bigger possibilities for chip designers to launch the next brilliant new TV, High-Definition audio player or health appliances.

    Allen Watson

    Allen started in the ‘semiconductor IP industry’ before it was called the ‘semiconductor IP industry’. Back then, it was about ‘megafunctions’, ‘megablocks’ or MegaMacros™ (as trademarked by the pioneering UK IP company Allen was with… no, not that UK company). The biggest of these ‘mega’ things was an 8051! Today, of course, IP blocks are much larger and much more complex. And, it’s about the software, as well as the hardware. It’s also about working with a set of partners, sometimes called an ecosystem or community. Allen has been doing that for many years and is enjoying working with old and new friends on the ARC processor ecosystem.

    Chris Caerts

    Chris has always been inquisitive. Even at a young age he started every other sentence with a question. How? Why? Why not? What if? It drove his parents nuts, so they bought him a ‘programmable calculator’ to keep him busy. The marvelous TI-59; mind you, that was before affordable PCs were around. When an older friend studying engineering bragged about how engineers know how everything works, Chris knew this was what he wanted to do. After completing his Masters in electronics and chip design, his interest quickly moved to software. He discovered the Transputer, and OCCAM, and developed a passion for operating systems, APIs, multi-core software and development tools that has never gone away. Today Chris is focused on OSs, middleware and development tools and making them better for the next generation of microprocessors. And he stills asks: how, why, why not and what if, but it doesn’t seem to bother anyone anymore.

What’s in a Name?

Posted by Allen Watson on February 1st, 2012

When we have a choice to pick a name for something, it usually reflects some meaning for us. For example, I chose my daughter’s name as Abigail because I once saw a Mike Leigh play called ‘Abigail’s Party’ (the video below is a clip from the play). But, I also chose it because the name means ‘Father’s Joy’. Similarly, my name is Allen. It is of Scottish and Irish origin and it means ’handsome’. So, now you know why my parents chose to call me Allen.

Recently, we were battling with what to call our new partner program for the DesignWare ARC processor cores. We could have just called it the ARC Partner Program or the ARC Alliance Program or the ARC Community Program. But, I really wanted the name to have meaning.

I started by thinking about what the objectives of the program are:
• To broaden embedded industry support for the ARC Architecture and cores
• To partner with leading embedded software and hardware vendors to provide compelling ARC-based solutions
• Finally, to increase the awareness of ARC-based solutions

While these are important & noble objectives, nothing jumped out at me for choosing a name. So, I then thought about what the program means for our customers.
• Develop your ARC-based embedded processor solutions faster by leveraging compatible products from leading embedded industry vendors
• Reduce your project risk by taking advantage of design solutions pre-ported and tested for the DesignWare ARC architecture
• Save on development costs and resources by using products optimized for ARC-based designs

These are all good things. Develop faster. Reduce Risk. Save costs. I could call it the ARC Faster Reduce Risk Save Cost Program or ARC FRRSC Program. But, I thought better of that.

What to do? Thinking about what the program’s objectives and meaning for customers was not getting me to a name. That’s when I thought about how we are going to do this. We will work with partners by providing them access to ARC software & hardware development tools and provide support so that that they can optimize their product for the ARC Architecture. This, in turn, will give our customers access to a broad array of industry solutions. Eureka! Did you spot the operative word? Access. We’re providing access for our partners and, in turn, providing access for our customers.

It’s the ARC Access Program!

And so it came to be. The program launches with many valued companies: Alango Technologies, Ashling Microsystems, Embecosm Ltd., Express Logic, Green Hills Software, Interniche, Lauterbach, MiSPO, QSound Labs and SoftRISC Communications. We look forward to working with more leading embedded industry vendors to provide compelling solutions for the ARC Architecture.

P.S. The actual reason I was called Allen is because it was my mother’s maiden name. I was not given a middle name, so that my full name is the combination of each of my parent’s last names. As I said, there’s always a reason why we name things the way we do!

P.P.S. Although the play was called ‘Abigail’s Party’, we never get to see Abigail or her party.

VN:D [1.9.8_1114]
Rating: 5.0/5 (1 vote cast)
What's in a Name?, 5.0 out of 5 based on 1 rating

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>