It won't.
It will end up in AOSP when JBQ gets back.
Due to some human scheduling snafus on my part, this didn't get done before he went on vacation.
I simply don't know JBQ's exact method of doing git kernel pushes to AOSP, and i'm not going to possibly mess up the entire AOSP kernel tree to learn :).
Does Glass required proprietary binary blobs to be combined with the GPL source like the Nexus devices (pinning you to a narrow range of kernel versions), or is it actually open through and through?
I don't know specifically about the drivers in Glass but it's based on the pretty old TI OMAP4 platform which was in the Galaxy Nexus, and I think out of the SoC manufacturers TI is (well, was, since they stopped making OMAP) the most open by far.
edit/clarification: These won't be blobs in the kernel but they'll be IMGTec binary libraries. So in practice it's slightly less annoying for kernel hacking.
I guess I will point out that this doesn't seem to be the case. As we see from this very post the kernel sources are released, and from the earlier posts we know Glass can be unlocked with the standard Nexus style 'fastboot oem unlock', so Glass (at least through Google, who knows what other OEMs might do) will be as open as Nexus phones from what we can tell.
It wont boot without drivers for various pieces of the hardware, drivers that are developed by third parties and that are most likely closed source. Those drivers may be released at a later time as 'binary blobs'.
Googler here. It will be with AOSP soon, but there was some confusion getting that done. We did this as a temporary measure; didn't want to delay getting GPL compliant.
From the tarball COPYING file:
"the only valid version of the GPL as far as the kernel is concerned is _this_ particular version of the license (ie v2, not v2.2 or v3.x or whatever), unless explicitly otherwise stated. -Linus Torvalds"
