Hi
After last week's SMM loader problem on all but the BSP, I noticed another
problem in the SMM setup.
The permanent smihandler is currently built as a relocatable module such
that coreboot
can place it wherever it thinks it's a good idea. (TSEG is not known at
buildtime).
These relocatable
arthur, what might we do with either the build process or startup to
avoid this problem in future? Do you think we could find a way to
catch this programmatically soon, rather than humanly too late?
On Mon, Apr 11, 2022 at 2:48 AM Arthur Heymans wrote:
>
> Hi
>
> After last week's SMM loader
Martin Roth via coreboot wrote:
> > Your concern is valid and I think a key point. CBOR may not be bad
> > over a socket, but such a complex and arbitrarily extensible format
> > is much too error prone to be a good technical choice during boot.
>
> So if the idea is to create a payload handoff
Email coreboot@coreboot.org was removed.
https://ticket.coreboot.org/my/account
User: flx
IP address: 185.104.142.213
Date: 04/12/2022 12:55 AM
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences,
Martin Roth via coreboot wrote:
> 1) Please don't use the term deprecate - use "moved to a branch"
I don't think the wording matters, my points are discoverability and
drive-by maintainance.
> If a platform is perfect and doesn't need to be updated, it doesn't
> need to be on the master
Arthur Heymans wrote:
> I think this issue might affect a lot more systems than I initially thought.
Would it make sense to backport your fix to old releases and bump
those release numbers to a .1 on the end?
//Peter
___
coreboot mailing list --
6 matches
Mail list logo