[coreboot] Help compiling image for Thinkpad T60

[cuckoohead--- via coreboot]

I'm following the instructions of the Build HOWTO section of the Coreboot Wiki 
(https://www.coreboot.org/Build_HOWTO) and I'm having some
issues.

Following the quote from the wiki "It is worth checking the Supported 
Motherboards (https://coreboot.org/status/board-status.html) page to see if
your mainboard is known to work with a particular version of coreboot. If your 
board is listed and
you want to try a known-working version, click the "upstream tree" link to find 
the commit hash and
then check it out in git:"

So I find the commit hash and run:

git checkout 87e36c442e33388493f259bfa14db460a4f02753

Which returns the output:

warning: unable to rmdir '3rdparty/intel-sec-tools': Directory not empty
warning: unable to rmdir '3rdparty/qc_blobs': Directory not empty
warning: unable to rmdir '3rdparty/stm': Directory not empty
Updating files: 100% (8604/8604), done.
M 3rdparty/amd_blobs
M 3rdparty/arm-trusted-firmware
M 3rdparty/blobs
M 3rdparty/chromeec
M 3rdparty/fsp
M 3rdparty/intel-microcode
M 3rdparty/libgfxinit
M 3rdparty/libhwbase
M 3rdparty/vboot
Note: switching to '87e36c442e33388493f259bfa14db460a4f02753'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

git switch -c 

Or undo this operation with:

git switch -

Turn off this advice by setting config variable advice.detachedHead to false

If I try to proceed with:

git submodule update --checkout

I receive the output:

fatal: remote error: upload-pack: not our ref 
0ac1af437d2cc461b94bd2cdaa195e86dd481d37
Fetched in submodule path '3rdparty/amd_blobs', but it did not contain 
0ac1af437d2cc461b94bd2cdaa195e86dd481d37. Direct fetching of that commit failed.

I'm not that familiar with git so I apologize if this is a simple 
problem. Sorry for the spam too, I missclicked the return key.
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Help compiling image for Thinkpad T60

[cuckoohead--- via coreboot]

I'm following the instructions of the Build HOWTO section of the Coreboot Wiki 
(https://www.coreboot.org/Build_HOWTO) and I'm having some
issues.

Following the quote from the wiki "It is worth checking the Supported 
Motherboards (https://coreboot.org/status/board-status.html) page to see if
your mainboard is known to work with a particular version of coreboot. If your 
board is listed and
you want to try a known-working version, click the "upstream tree" link to find 
the commit hash and
then check it out in git:"

So I find the commit hash and run:

git checkout 87e36c442e33388493f259bfa14db460a4f02753

Which returns the output:

warning: unable to rmdir '3rdparty/intel-sec-tools': Directory not empty
warning: unable to rmdir '3rdparty/qc_blobs': Directory not empty
warning: unable to rmdir '3rdparty/stm': Directory not empty
Updating files: 100% (8604/8604), done.
M 3rdparty/amd_blobs
M 3rdparty/arm-trusted-firmware
M 3rdparty/blobs
M 3rdparty/chromeec
M 3rdparty/fsp
M 3rdparty/intel-microcode
M 3rdparty/libgfxinit
M 3rdparty/libhwbase
M 3rdparty/vboot
Note: switching to '87e36c442e33388493f259bfa14db460a4f02753'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

 git switch -c 

Or undo this operation with:

 git switch -

Turn off this advice by setting config variable advice.detachedHead to false

If I try to proceed with:

git submodule update --checkout

I receive the output:
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: Status of Tianocore EDK2 on Coreboot

[Peter Stuge]

Julian Stecklina wrote:
> Is there any deeper reason why fixes don't flow back to EDK2?

I'm guessing here - I have no experience with EDK2 development - but
I suspect that it's not actually an open source project, I think it's
just source code by Intel+Microsoft+friends published on GitHub.

The traditional firmware industry isn't so good at community efforts.


//Peter
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: Status of Tianocore EDK2 on Coreboot

[Julian Stecklina]

Hi Christian,

thanks for the many pointers. This is really helpful! :)

Is there any deeper reason why fixes don't flow back to EDK2?

Julian

On Fri, 2021-04-16 at 13:58 +0200, Christian Walter wrote:
> Hi Julian,
> 
> There are a couple of Repo's you can check out:
> 
> https://github.com/tianocore/edk2
> 
> https://github.com/MrChromebox/edk2
> 
> https://github.com/9elements/edk2
> 
> https://github.com/system76/edk2
> 
> 
> We are using our own Fork (9elements) on a CFL Board in production. Also 
> System76 does use their Fork in production - so setting this up in a 
> virtualized environment shouldnt be a problem at all. To be honest, I 
> would not start with the tianocore one, use one of the forks ;)
> 
> Best,
> 
> On 4/16/21 1:44 PM, Julian Stecklina wrote:
> > On Thu, 2021-04-15 at 16:49 +, Andy Pont wrote:
> > > Julian wrote…
> > > 
> > > > Is anyone actually actively using TianoCore EDK2 on top of coreboot or
> > > > is
> > > > support experimental in general?
> > > We have platforms that are using Matt’s UEFIPayload package to boot
> > > either Linux or Windows.  The mainboards and configs aren’t in the
> > > upstream coreboot repo at present - I am just working with the company
> > > concerned to get them into a form where they will (hopefully) be
> > > accepted.
> > This is great news! We are mostly interested in running Coreboot+EDK2 in a
> > virtualized environment and knowing that it works in the real world gives a
> > confidence boost here.
> > 
> > We are not afraid of fixing the occasional issue and bitrot, but fully
> > maintaining everything is out of scope for us.
> > 
> > Julian
> > 
> > ___
> > coreboot mailing list -- coreboot@coreboot.org
> > To unsubscribe send an email to coreboot-le...@coreboot.org
> -- 
> *Christian Walter*
> *Head of Firmware Development / Cyber Security *
> 
> 
> 
> 9elements GmbH, Kortumstraße 19-21, 44787 Bochum, Germany
> Email: christian.wal...@9elements.com
> Phone: _+49 234 68 94 188 _
> Mobile: _+49 176 70845047 _
> 
> Sitz der Gesellschaft: Bochum
> Handelsregister: Amtsgericht Bochum, HRB 17519
> Geschäftsführung: Sebastian Deutsch, Eray Basar
> 
> Datenschutzhinweise nach Art. 13 DSGVO 
> ___
> coreboot mailing list -- coreboot@coreboot.org
> To unsubscribe send an email to coreboot-le...@coreboot.org


___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org