While Intel Corp may not be interested in Gallium3D at this point, there is an Intel Gallium3D driver in existence. This Intel Gallium3D driver was largely written by VMware (formerly Tungsten Graphics) and community contributors. This Gallium3D driver works fairly well for being community-maintained, but it doesn't support the full range of hardware as supported by Intel's official DRI driver. The classic driver is also well-optimized by Intel engineers so it's capable of delivering better performance too at this point.
This Intel Gallium3D driver doesn't receive as much work as the Radeon or Nouveau Gallium3D drivers, but it still receives bug-fixes and minor work from time to time. There aren't any major Linux distributions shipping with the Intel Gallium3D driver, but it's more of just a "proof of concept" or alternative choice for those building their own Mesa stack.
Interestingly, there seems to be some interest in this "i915g" driver from Google's Chromium OS / Chrome OS team. Stéphane Marchesin, who was the original founder of the Nouveau driver and led the NVIDIA reverse-engineering originally, joined Google a while ago to handle the X/graphics side of the Google web-focused operating system. This isn't news to those that follow the mailing lists or Git activity where one can see Stephane's association, but what's interesting is the official work he has going into the i915g driver.
Just yesterday there were three commits (Git web) to Mesa by Marchesin that were to the i915g driver and the work had added support for more texture and render target formats along with drawing point sprites. These commits came from his Chromium.org e-mail address and it's not the first time he's contributed to this unofficial driver but last year were also a number of i915g driver commits to Mesa master.
Further showing that there is at least some interest in Intel Gallium3D for Google's operating system, mistakenly committed to Chromium OS earlier this month was a change that made this Gallium Intel driver work. It was committed here, but then later abandoned when realizing he wasn't supposed to push this change as it belonged to the wrong tree.
Could Google pressure Intel into taking up the Gallium3D route? We shall see what comes out of either company.