NetLogic Microsystems
semiconductor company
NetLogic Microsystems, Inc. was a fabless semiconductor company that developed high performance products for data center, enterprise, wireless and wireline infrastructure networks. The company was founded in 1995 by Norman Godinho and Varad Srinivasan, became a public company on the NASDAQ exchange (ticker symbol: NETL) under the leadership of CEO Ronald Jankov in July 2004 and was acquired by Broadcom Corporation for $3.7 billion in February 2012.
Products
NetLogic’s product portfolio included knowledge-based processors, multi-core processors, content processors, network search engines, high-speed 10 and 40 Gigabit Ethernet PHYs, wireless base station digital front-end PHYs and low-power embedded processors. Its global customer base included Alcatel-Lucent, Cisco Systems, Dell, Ericsson, Google, Hewlett-Packard, Huawei Technologies, Juniper Networks and Nokia-Siemens.
History
It was in October 2007 that NetLogic Microsystems, Inc. signed a definitive agreement to acquire the privately held Aeluros, Inc., which created interface technologies and semiconductor products. In December 2010 NetLogic began using an implementation system developed by Magma Design Automation Inc, which created chip design software.
In 2011, NetLogic acquired Optichron for $22 million. From its IPO in 2004 through 2011, NetLogic grew at an annual rate of 39%, which was four to five times the average growth rate of semiconductor companies during that period.
The public source identifies “NetLogic Microsystems” as semiconductor company. This brief keeps that definition visible, then builds a research path around NetLogic, Microsystems and semiconductor.
Why this record matters
A short description can identify a subject without explaining its stakes. For “NetLogic Microsystems”, the useful work is to connect “semiconductor company” to the records capable of establishing context and consequence.
The record creator and administrative purpose are central evidence, because official documentation reflects both action and institutional priorities. The source revision retrieved here is dated Aug 25, 2026. The linked authority identifier is Q16964955. 2 of 2 selected statements include explicit references; 1 carry qualifiers and 0 use preferred rank. The first chronological checks are 1995, 2004, 2012 and 2007.
Later summaries often reconcile disputed chronology or motive more neatly than the contemporary record permits. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “NetLogic Microsystems”, its source revision and the description used here.
- Expand the search: follow NetLogic Microsystems primary sources, NetLogic Microsystems archive and NetLogic research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “NetLogic Microsystems”?
- What chronology connects this entry to wider political or social change?
- Which voices are present, absent or mediated by the institution?
Search terms from this dossier
This entry incorporates text from “NetLogic Microsystems” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.