On 03/25/2014 02:00 AM, ron minnich wrote:
I keep wanting to drop out of this discussion but there are some things I just can't let go by,
On Mon, Mar 24, 2014 at 4:20 PM, Paul Menzel <
Additionally I heard claims, that the GPLv2 license is violated as it is currently impossible to rebuild the exact same image that is shipped with the devices as it is not even clear what commit was used to build the image and to my knowledge the requests on the list and in the IRC channel were not answered.
Dude, the commit is IN THE IMAGE. At least on the images I work with. As in: ro bios version | Google_Link.2695.1.133
from chrome:system on my link. I also just checked my falco and the hash is right there too from cbmem -c. I don't build all platforms; have you found some where this is not the case? Might you consider fixing it?
Hi Ron
I made these claims about old samsung/lumpy units late in 2012, back then the repositories at Chromium git were not even open to public.
I do not have collection of Chromebooks either, so you can consider all this discussion as unreliable second-hand knowledge, should you wish to do so. Here are my notes about recent discussion on #coreboot.
Hardware in question is: C710-2834, google/parrot
hexdump -C shipped_parrot.rom | tail
007fff60 00 00 47 4f 4f 47 4c 45 00 50 61 72 72 6f 74 00 |..GOOGLE.Parrot.| 007fff70 9f 00 00 00 9e 00 00 00 97 00 00 00 00 00 10 00 |................| 007fff80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
cbmem -c
coreboot- Mon Apr 29 15:07:52 PDT 2013 starting...
That is, it appears the revision information seems to be intentionally wiped from the string logged in CBMEM console there. We did recover it from CBFS config -file:
revision 6ed0cbf6248d5b4311778d8a5d6e4fc674755f55
Regards, Kyösti