[coreboot] Recommended workflow with Chromebook support

Folks, This question is directed at the Coreboot developers who target a Chromebook device. Do you tend to do bulk of development and testing within chromiumos coreboot tree or directly in coreboot.org tree? As we get going we are trying to decide if it makes more sense to work directly in

Re: [coreboot] Depthcharge License

On 2017-12-24 05:27, Ivan Ivanov wrote: This commit got merged and the Depthcharge now should have the requested license files at its root directory. Dear friend, please let us learn about your device once it is released, maybe some of the coreboot developers would want to get your device - to

Re: [coreboot] Depthcharge License

On 2017-12-19 09:53, David Hendricks wrote: To be fair, it appears that many source files refer to a non-existent LICENSE file. Someone on the CrOS team should probably just add the LICENSE file for depthcharge and/or contact mal@ to see how the license info is being collected these days (e.g.

Re: [coreboot] Depthcharge License

On 2017-12-15 13:39, ttu...@codeaurora.org wrote: Preparing to mirror the coreboot.org requires us to vet the various licenses, etc. There doesn't appear to be a LICENSE or COPYING file in the Depthcharge tree. My understanding is that Depthcharge is licensed GPLv2 (or later). How would I

[coreboot] Depthcharge License

Preparing to mirror the coreboot.org requires us to vet the various licenses, etc. There doesn't appear to be a LICENSE or COPYING file in the Depthcharge tree. My understanding is that Depthcharge is licensed GPLv2 (or later). How would I confirm this with an online source? Cheers,

[coreboot] chromeos-firmwareupdate

Folks, If this query more correctly belongs on ChromiumOS list, I will re-post. This utility appears to be the safe/practical way to interact with the coreboot firmware on an actual chromebook device. The factory image for kevin has this located at /usr/sbin/chromeos-firmwareupdate. I have

Re: [coreboot] How to disassembly the coreboot.rom file

I didn't copy group on original reply, my bad. On 2017-04-13 11:40, ttu...@codeaurora.org wrote: On 2017-04-13 05:07, Maxim Gusev via coreboot wrote: Hello, friends I have a couple of questions. When I run the coreboot on my motherboard it doesn't work. I have some IPs of instructions

Re: [coreboot] Group demographics

On 2017-03-24 17:42, Julius Werner wrote: * Google's recovery manifest (from linux_recovery.sh) can pull a recovery image for a specific product, I have yet to find depthcharge as a payload * Obviously I haven't pulled all of the recovery images, but have looked at ~10 * those interested in

Re: [coreboot] Group demographics

On 2017-03-24 08:23, ron minnich wrote: On Fri, Mar 24, 2017 at 8:14 AM wrote: Q.1) Are questions related to Coreboot + Payload that boots a Chromebook appropriate for this list or a ChromiumOS list? of course! First the question and then the background. Q) Are

[coreboot] Group demographics

Folks, I've been monitoring the list for ~6 months with a couple of posts. My point of interest is working with Coreboot on ARMv8 targeting a Chromebook. I have a couple of questions for this group. Q.1) Are questions related to Coreboot + Payload that boots a Chromebook appropriate for

Re: [coreboot] How come the community meeting is hosted by proprietary software?

On 2017-03-17 06:27, Peter Stuge wrote: Patrick Georgi via coreboot wrote: 2017-03-17 13:17 GMT+01:00 Dumitru Ursu : > I never tried the web interface. We did, it failed us. I wish someone would have mentioned that sooner. What problems did people have with mumble-web, and

Re: [coreboot] Suggestions on shipping ARMv8 Chromebook

On 2017-02-17 10:10, Patrick Georgi wrote: The just-released Chromebook Plus comes with an RK3399 SoC, which is ARMv8 and fully open at the AP firmware level (GPU is Mali with its usual issues, as well as Wifi firmware). Thanks for this suggestion, we are in process of purchasing. Do you or

Re: [coreboot] Understand vboot logic to select FW_B

Once spi-nor flash write issue fixed in driver, ability to select FW_B works, as Aaron indicated it should. Cheers, T.mike On 2017-02-15 15:01, ttu...@codeaurora.org wrote: On 2017-02-15 13:34, Aaron Durbin wrote: On Wed, Feb 15, 2017 at 3:20 PM, wrote: On

Re: [coreboot] coreboot community meeting minutes for February 16, 2017

On 2017-02-17 09:55, ron minnich wrote: what I've found on u-root and harvey is once we had slack, the mailing list dropped to almost zero. Key word being almost, we still use the mailing list for archival announcements. ron This is reminiscent of an upstart thread from maybe 5-6 years ago

[coreboot] Suggestions on shipping ARMv8 Chromebook

Folks, As we work on our own implementation we are kicking around purchasing an off-the-shelf ARMv8 Chromebook. Main requirement is that it has a nice clean software build in the chrome/coreboot trees. Prefer no binary blobs, but that is merely a preference. Does the community have any

Re: [coreboot] Understand vboot logic to select FW_B

On 2017-02-15 13:34, Aaron Durbin wrote: On Wed, Feb 15, 2017 at 3:20 PM, wrote: On 2017-02-15 09:45, Aaron Durbin via coreboot wrote: On Wed, Feb 15, 2017 at 11:38 AM, wrote: On 2017-02-15 07:46, Aaron Durbin via coreboot wrote: On Tue,

Re: [coreboot] Understand vboot logic to select FW_B

On 2017-02-15 09:45, Aaron Durbin via coreboot wrote: On Wed, Feb 15, 2017 at 11:38 AM, wrote: On 2017-02-15 07:46, Aaron Durbin via coreboot wrote: On Tue, Feb 14, 2017 at 8:26 PM, wrote: Folks, I'm working on coreboot on ARMv8

Re: [coreboot] Understand vboot logic to select FW_B

On 2017-02-15 07:46, Aaron Durbin via coreboot wrote: On Tue, Feb 14, 2017 at 8:26 PM, wrote: Folks, I'm working on coreboot on ARMv8 architecture and recently attempted to verify FW_B can be selected if FW_A is corrupted. In reviewing the code-path through coreboot

[coreboot] Understand vboot logic to select FW_B

Folks, I'm working on coreboot on ARMv8 architecture and recently attempted to verify FW_B can be selected if FW_A is corrupted. In reviewing the code-path through coreboot vboot wrapper and vboot_reference library I'm not understanding the logic. The logic appears to be that