Re:Google Glass kernel GPL source
by DannyBee on Saturday April 27, 2013 @06:36PM
(#5619298)
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 :).
Re:Google Glass kernel GPL source
by avar on Saturday April 27, 2013 @04:21PM
(#5618926)
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?
Re:Google Glass kernel GPL source
by ibrahima on Saturday April 27, 2013 @04:45PM
(#5618981)
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.
Re:Google Glass kernel GPL source
by edderly on Saturday April 27, 2013 @04:49PM
(#5618990)
They'll be IMGTec blobs for the SGX GPU then
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.
Re:Google Glass kernel GPL source
by myko on Sunday April 28, 2013 @07:24AM
(#5620881)
Ah, I see.
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.
Re:Google Glass kernel GPL source
by joenathan on Saturday April 27, 2013 @11:41PM
(#5620106)
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'.
Re:Google Glass kernel GPL source
by slb on Saturday April 27, 2013 @03:00PM
(#5618725)
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.
Re:Google Glass kernel GPL source
by Maxious on Sunday April 28, 2013 @05:06AM
(#5620682)
The fact that Linux is licensed as GPLv2?
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"
[1] : 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.