[coreboot] [coreboot - Feature #213] Have the bug tracker report activity to the mailing list

[Patrick Georgi]

Issue #213 has been updated by Patrick Georgi.

Related links updated

Removed IRC as a target given the chaos we have around chat channels right now 
with libera.chat and matrix decoupling.
Meanwhile, mailing list receives ticket updates


Feature #213: Have the bug tracker report activity to the mailing list
https://ticket.coreboot.org/issues/213#change-1639

* Author: Patrick Georgi
* Status: Resolved
* Priority: Normal
* Assignee: Patrick Georgi
* Category: infrastructure
* Start date: 2019-06-05

This helps make the tracker more visible and therefore useful



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
https://ticket.coreboot.org/my/account
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] [coreboot - Feature #213] (Resolved) Have the bug tracker report activity to the mailing list

[Patrick Georgi]

Issue #213 has been updated by Patrick Georgi.

Subject changed from Have the bug tracker report activity to IRC and the 
mailing list to Have the bug tracker report activity to the mailing list
Status changed from New to Resolved
Related links updated


Feature #213: Have the bug tracker report activity to the mailing list
https://ticket.coreboot.org/issues/213#change-1638

* Author: Patrick Georgi
* Status: Resolved
* Priority: Normal
* Assignee: Patrick Georgi
* Category: infrastructure
* Start date: 2019-06-05
* Related links: Removed IRC as a target given the chaos we have around chat 
channels right now with libera.chat and matrix decoupling.

This helps make the tracker more visible and therefore useful



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
https://ticket.coreboot.org/my/account
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: [RFC] Pre-Memory Sign-of-Life using Intel uGOP

[Martin Roth via coreboot]

Hi Jeremy,

Thanks for posting this. I know that you're planning on doing a presentation 
about this in this week's leadership meeting and look forward to that. 
https://coreboot.org/calendar.html

A few questions:
1) How does the uGOP driver work with libgfxinit? Does using uGOP mean that the 
full GOP driver then needs to be used, or can the system transition back to 
libgfxinit after memory is initialized.

2) When is the Graphics Programmer Reference Manuals going to be published so 
that the support can be added? Is this planned for next month, next year, or 
not currently planned, but hoped for?

3) Is there a reason that the uGOP driver can't be open sourced, at least once 
the Graphics Programmer Reference Manuals are released?

4) When you talk about the differences in time between the uGOP driver and 
libgfxinit, is that strictly due to when they are called, or is there some 
further difference that the uGOP driver is able to accomplish that libgfxinit 
wouldn't ever be able to do?

5) Is there a reason that Intel is unwilling to add (or help add) the required 
code to libgfxinit, an open source solution that according to your notes should 
be comparable to the uGOP binary solution? Would Intel be willing to help once 
the reference manuals are released, or is any cooperation between intel and the 
community on libgfxinit just not able to happen?

6) I assume that the uGOP driver is completely optional, and is only needed to 
show early signs of life. Is that correct, or could the uGOP driver become 
mandatory at some point?


Please understand that any unhappiness about this plan is not directed at you 
personally (or *should* not be), but just the idea of adding yet another binary 
blob to the coreboot boot flow. I've been in this same spot and understand the 
frustration of just trying to get your work done, while the community is 
unhappy about the direction of the work being done.

Thanks very much.
Martin

Aug 14, 2023, 14:53 by jeremy.composte...@intel.com:

>
> Dear coreboot developers,
>
>
> With Raptor Lake, we introduced the Pre-Memory Sign-of-Life feature which 
> displays an on-screen message while firmware components such as coreboot, 
> Firmware Support Package Memory (FSP-M) or, CSME perform long time operations 
> during pre-memory stages.
>
>
> We propose to take advantage of a proprietary driver Intel already supports, 
> validates and includes in FSP silicon: the Intel Graphics PEIM (Pre-EFI 
> Initialization Module) driver also known as the GOP (Graphical Output 
> Protocol) driver.
>
>
> This driver is designed to run in post-memory initialization stages. 
> Therefore, we derived a new version capable of running in pre-memory stages 
> which we called µGOP. This version is specifically designed to perform 
> graphics legacy VGA initialization.
>
>
> We intend to keep providing such a binary base solution on the long run as it 
> addresses our software convergence goals and is compatible with early 
> platform development stage constraints. > libgfxinit 
> >  supports can always be added later 
> by the open-source community once the Graphics Programmer Reference Manuals 
> are published.
>
>
> Below, we present the work we performed to run this µGOP driver from coreboot 
> romstage. It allows to initialize graphics with a very similar flow compared 
> to > libgfxinit >  use.
>
>
> Our goal is to start collecting feedback. We will release all the patches on 
> coreboot.org under the > ugop >  
> topic soon.
>
> 1.>  µGOP driver interface
>
> The uGOP PEIM provides the following PEIM-to-PEIM protocol under the > 
> 31a4622d-0e21-40a2-80db-c44208fce1b5>  GUID.
>
> #define>  > PEI_PREMEM_GRAPHICS_PPI_GUID>  \{ \  0x31a4622d, 0x0e21, 0x40a2, 
> 0x80, 0xdb, 0xc4, 0x42, 0x08, 0xfc, 0xe1, 0xb5 \};
>
> The protocol is composed of three fields.
>
> struct>  {  > UINT32> > Version> ;  > 
> PREMEM_PEI_GRAPHICS_INIT>   > PreMemGraphicsPpiInit> ;  > 
> PREMEM_PEI_GRAPHICS_EXIT>   > PreMemGraphicsPpiExit> ;} > 
> PEI_MICRO_GRAPHICS_PPI> ;
> The current > Version>  is > 0x0001> . Where the upper 16 bits represent 
> the major (1) and the lower 16 bits represent the minor number.
>
> PreMemGraphicsPpiInit()
>
> typedef> EFI_STATUS> (> EFIAPI>  *> PREMEM_PEI_GRAPHICS_INIT> ) (  IN  > 
> VOID>   *> Vbt> );
>
> The > PreMemGraphicsPpiInit()>  should be supplied with a pointer to the 
> Video BIOS Table.
>
> PreMemGraphicsPpiExit()>  does not take any parameters. This function must be 
> called to disable VGA graphics configuration once not necessary anymore. Not 
> performing this operation may lead to undesirable behaviour when other 
> graphics stack starts (GOP in FSP-S or Operating System driver).
> 2.>  Integration
>
> As we intend to run µGOP driver in romstage, we want to keep the required 
> coreboot code as small and efficient as possible.