: https://groups.google.com/forum/?fromgroups=#!msg/android-bu...
The repository is indeed empty -- no branches, no nothing.
SHA1 Checksum: 555661ff568a0d89de213ea0c32915cd908cc582
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.
Does this mean that you can take this kernel source, modify it and/or add extensions, and then deploy it on your google glass?
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"
Which is identical to kernel.org: https://www.kernel.org/pub/linux/kernel/COPYING
That section was discussed at https://lkml.org/lkml/2006/1/25/273 where 2006-Linus doesn't see GPLv3 ever happening.