Re: [coreboot] How to properly conform with GPLv2 for Coreboot and SeaBIOS on an embedded system

[David Hendricks]

On Sat, Dec 30, 2017 at 10:05 PM, Lewis, Ian (Microstar Laboratories) <
ile...@mstarlabs.com> wrote:

> With a few minutes spent looking, it is not at all clear to me how Siemens
> handles their GPL responsibility and whether they attempt to provide
> compliance for their customers or not.
>

For their part, Siemens releases the code upstream:
https://review.coreboot.org/cgit/coreboot.git/tree/src/mainboard/siemens

As with your case the firmware for their products is basically invisible to
the customer. Nevertheless if the customer wants to examine the code or
make changes they can easily do so. Relevant license information is found
in the header of each source code file as well as the COPYING file at the
root of the coreboot directory.

Werner (cc'd) might be able to share some more details about how they
handle compliance matters.
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

[coreboot] Disabling ME >= 6.0 < 11 via the AltMeDisable bit

[Denis 'GNUtoo' Carikli]

Hi,

As I understand it:
- For ME < 6.0, the ME firmware can be removed totally, and still have
  a functional computer.
- For ME >= 6.0 (Nehalem) to ME < 11 (Broadwell), the All ME firmware
  can't be totally removed: the BUP module is required to have a
  functional computer. For such Firmware/Hardware versions the BUP does
  "Bringup (hardware initialization/configuration)"[1]
- For ME 11, the following modules are required to have a functional
  computer: RBE, BUP, kernel and syslib. For such generation, setting
  the HAP bit only tells the firmware not to load extra code (At that
  point the kernel is already loaded).

I've some questions regarding the above:
- Is there more details than "Bringup (hardware
  initialization/configuration)" for what the BUP partition does for
  the ME >= 6.0 and < 11.
- With the ME >= 6.0 and < 11, what does the AltMeDisable bit really
  do? Do we have some insights that tend to show that the execution is
  stopped, or not stopped?

References:
---
[1]https://recon.cx/2014/slides/Recon%202014%20Skochinsky.pdf

Denis.


pgphNwmmpwqJC.pgp
Description: OpenPGP digital signature
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot