Array ( [content] => [params] => Array ( [0] => /forum/index.php?threads/intel-says-it%E2%80%99s-on-course-to-regain-chip-production-leadership.17167/page-2 ) [addOns] => Array ( [DL6/MLTP] => 13 [Hampel/TimeZoneDebug] => 1000070 [SV/ChangePostDate] => 2010200 [SemiWiki/Newsletter] => 1000010 [SemiWiki/WPMenu] => 1000010 [SemiWiki/XPressExtend] => 1000010 [ThemeHouse/XLink] => 1000970 [ThemeHouse/XPress] => 1010570 [XF] => 2021270 [XFI] => 1050270 ) [wordpress] => /var/www/html )
I think the dubious quality of Cliff's humor just eluded you.Don’t many 2D and 2.5D mcm designs not have a parent die they stack onto? Unless the parent die is just the first die that is placed on the package.
Why do we even call them chiplets? As far as I know IBM just called each one a die that was part of an MCM design.
Is there a naming convention standardization body or committee?It is a marketing term just like IoT. There is even a Chiplet Summit so marketing works:
![]()
Chiplets Make Huge Chips Happen
Chiplet Summit Chiplets Make Huge Chips Happen January 24-26, 2024 San Jose, California Conference & Exhibition This is going to be HUGE! Sponsor Signup Chiplet Summit Is the #1 Place to Exhibit Position Your Company as a Leader in an Emerging Technology. Lay Claim to Your Share of a Projected...chipletsummit.com
I'm surprised www.chiplet.com is still available.
Not for marketing terms. Even when industry standards bodies name things, many people often choose to use terms they make up. For example, cabled Ethernet does not have a switch specification. Ethernet "switches", as the industry calls them, are actually called "bridges" in IEEE 802.1 WG specifications. Ethernet links are correspondingly called "segments", and what the industry calls switches "bridge" between segments. (The Ethernet specs still support CSMA/CD buses.) All of this legacy and ancient terminology does not please marketing people much, so they call Ethernet components whatever they want.Is there a naming convention standardization body or committee?
That's because there isn't any marketing necessary for any of that esoteric technology. No one outside of semiconductor of computer system geeks care one bit about any of those terms. Intel tried to market SMT, and got all wrapped around the axle trying to explain the difference between a CPU hardware thread (SMT) and a CPU core.Yeah it seems weird, given semi folks don't use other marketing names to refer to all other implementations of said technology. For example trigate (finfet), Hyperthreading (SMT), Infinity cache (L3 cache on a GPU), InFo (fan out), X-cube (3D-stacking), RibbonFet or MBCFET (HNS).
In this case how is chiplet any different? To the end consumer it literally doesn't matter how many dies their device has nor how they are connected.That's because there isn't any marketing necessary for any of that esoteric technology. No one outside of semiconductor of computer system geeks care one bit about any of those terms. Intel tried to market SMT, and got all wrapped around the axle trying to explain the difference between a CPU hardware thread (SMT) and a CPU core.
Because chiplet technology is being marketed within the industry, not to consumers. In client CPUs, SMT was being marketed to consumers.In this case how is chiplet any different? To the end consumer it literally doesn't matter how many dies their device has nor how they are connected.
So why do industry folks accept this industry marketing term, and not others. I don’t think that every fab’s extra DCTO opportunities will just be called finflex. Nobody will ever call HNS MBCFET or ribbonFET. None of these terms are targeted at consumers either. My only guess is people thought that “disaggregated die”, “the x die in our soc”, or “x componet of our mcm design” isn’t as fast as “our x chiplet”. Whereas something like finFET is just as fast as trigate.That's because there isn't any marketing necessary for any of that esoteric technology. No one outside of semiconductor of computer system geeks care one bit about any of those terms.
Except today the term is also (mainly?) used for chips side-by side, either on a silicon interposer or organic substrate...Chiplets are the child die that flipchips to the parent die
I can only guess. I have noticed over the many years I was in the business that some folks get a kick out of defining their own terms and having the industry use them. Also, some companies really don't like other companies, and refuse to use that company's terminology.So why do industry folks accept this industry marketing term, and not others.
Thanks that also explains why articles about Ethernet are so confusing to read!Not for marketing terms. Even when industry standards bodies name things, many people often choose to use terms they make up. For example, cabled Ethernet does not have a switch specification. Ethernet "switches", as the industry calls them, are actually called "bridges" in IEEE 802.1 WG specifications. Ethernet links are correspondingly called "segments", and what the industry calls switches "bridge" between segments. (The Ethernet specs still support CSMA/CD buses.) All of this legacy and ancient terminology does not please marketing people much, so they call Ethernet components whatever they want.
IEEE Standards Association
Ethernet local area network operation is specified for selected speeds of operation from 1 Mb/s to 400 Gb/s using a common media access control (MAC) specification and management information base (MIB). The Carrier Sense Multiple Access with Collision Detection (CSMA/CD) MAC protocol specifies...standards.ieee.org
In a way, a Congress-like entity did write a lot of it. While Intel wrote the first version of the spec, like they did with PCI, PCIe, UCIe, and NVMe. Intel likes to get the industry behind them by forming consortiums, and based on the model they created for PCI. There's a board of directors, which consists of representatives from the industry leaders negotiated by Intel, and they approve working group directions, proposed specifications, etc. Then there are voting member companies, and there can be many tens of these. Personnel from the voting members can become part of the specification working groups, and within working groups decisions are made by voting, and it's on a "one company, one vote" basis. This structure creates a highly political environment, where companies negotiate with other companies in a you-vote-for-mine-and-I'll-vote-for-yours arrangement. So you end up with a feature-heavy specification, where the features are often based on work one company has done internally, and may have already filed invention disclosures. Or sometimes even have a design and test silicon for. The patents aren't a problem per se, because all of these consortiums force companies to license their spec-related IP on a reasonable and non-discriminatory (RND) basis. But this political stuff leads to fat specs with sometimes bloated and odd features.900 page spec... are you kidding me? Did Congress write it?
That's not why I retired. I just got old and mentally feeble.Now I know why you retired.