No, I was speaking more about the MacBook Pro. At one point, Apple had worked with Nvidia to produce an Intel CPU+Nvidia GPU system on an Nvidia motherboard. This was the last Intel MacBook I remember having a discrete GPU only. The motherboards for the rest show an Intel CPU, an Intel GPU also located on the MB, taking up space, and whatever AMD discrete board Apple decided to put in. I was under the impression that the Intel GPU was there ONLY because Intel required OEM’s include it… even though it takes up valuable space.
You are talking about long, long, ago in a Galaxy Far far away. Pre-2010. Back when Intel still allowed 3rd party Northbridge ( memory controller, PCI , and maybe iGPU) and Southbridge. (USB, general I/O , sound , etc. ) chips to be using on their "CPU only" packages.
Around 2010 Intel started to integrate memory controllers into the CPU die (and package). Pragmatically iGPUs came on die along with those too. [ doesn't make much sense at all to decouple a GPU subsystem "far away" from the required memory controllers. ). Ever since Intel switch over to Core iX (i3, i5, i7) there have been GPUs on the same die as the CPU cores (and memory controllers). For over the last decade the only Intel packages that didn't have a GPU in the personal computer space have been those based on the workstation/server dies. ( E5 , W 2000/300 series, Xeon SP , etc.)
In the per-2010 Nvidia sold a Northbridge with a shared memory controller and iGPU built in. (e.g. Geforce 9400M ). Intel and AMD kill all that off over a decade ago.
Once Intel got to the point where most of the mainstream CPU packages they were selling went into laptops, they have had iGPUs in all their mainstream offerings (for both desktop and laptop). Just to confuse things after a while Intel would label some HEDT dekstop package based on Workstation/server dies as being Core i7 xxxX or Core i9 xxxx. Those wouldn't have an iGPU but the 630UHD that some in this thread 'complained; about are integrated GPUs (iGPUs) not discrete GPUs (dGPU) . They are integrated onto the same die as the CPU cores and memory controller.
For example the. Core i 'Sandy Bridge' systems from 2010
Sandy Bridge (SNB) Client Configuration, formerly Gesher, is Intel's successor to Westmere, a 32 nm process microarchitecture for mainstream workstations, desktops, and mobile devices. Sandy Bridge is the 'Tock' phase as part of Intel's Tick-Tock model which added a significant number of...
en.wikichip.org
That box in the middle of the diagram is a logical description of the die on the "CPU" package. It has more than just CPU cores. The PCH ( platform controller hub) is handles the more general i/O USB/SATA/sound/etc. "IMC" integrated memory controller.
Same article an annotated die shot
Modern Intel mobile dies have Thunderbolt controllers built into the die also. The folks looking for ultimate CPU core counts and hyper modular GPUs grumble at the 'wasted' space for the iGPU. Toss the display controller and GPU and the GPU I/O and could perhaps fit 6 CPU cores on the same die. Intel has resisted that for more than several years.
In the laptop space it doesn't make much sense.
For last 5-8 years , on Intel mainstream 'CPU' dies there has been as much die space allocated to "uncore" (non x86 Core functionality) as to the 'CPU' cores . The 'CPU package' is really not only a CPU package anymore.
Ah, so for right now, these are ONLY intended to be discrete. Is that discrete/board only or did they announce a mountable version for laptops?
GPU packages are solder mounted on Add-in cards just as much as on main logic boards in laptops. Generally in modern times the "mobile" version is a desktop package just run at slower clock speeds (and maybe slower memory clocks also) to save power consumption. They aren't different dies, but may have different numbers assigned to them. ( Nvidia has tabled some. x070 desktops as x080 mobile versions. ) . There is also overhead if the add-in board enables complex overclocking, but that is complexity outside the base GPU package also.
Intel Arc chips have some features where they can distribute workload over both the Intel iGPU and the Arc dGPU. For example run the game on the dGPU but convert the display frames to an H.265 stream on the iGPU. There is some copying overhead but frees up some bandwidth for each also.