coreboot May 2015

coreboot@coreboot.org

46 participants
117 discussions

Start a nNew thread

New post published at blog.coreboot.org on May 19, 2015 at 4:00 pm
by WordPress 19 May '15

19 May '15

1 0

Re: [coreboot] AGESA PI for Olivehill+
by Kyösti Mälkki 19 May '15

19 May '15

On pe, 2015-05-08 at 09:02 +0000, Wolfgang Kamp - datakamp wrote: > Hello Kyösti, hello Wim, > > with AGESA source there is a file buildOpts.c in the mainboard directory. In this file you can overwrite seed values and they will be passed to AGESA build. > With binary Pi this file is absent. How is it possible to pass values to binary PI? > My AMD support comes from Aschheim-Dornach, Germany. > > Regards, > Wolfgang Wolfgang, with the PI source you are in a better position to develop than any of us in the community contributors. I hope you would push your AMD FAEs to get the API fixed, if you indeed are currently unable to make FT3b work with on-board memory, with the pre-built binaryPI files AMD AES pushes to coreboot 3rdparty / blobs. If you do not do that, You will need to rebase your local changes and rebuild PI part of your firmware image part every time AMD updates their MullinsPI package. I am complaining about the current state of things here as well: http://review.coreboot.org/#/c/9386/ Just beware that what I consider as the official documentation, taken from AMD AES website about PI and coreboot, still states the following in FAQ.462: "Note that the customer MAY NOT ship product with the nonscrubbed PI, as no such rights are provided in the NDA or otherwise. The customer must convert to the IP-scrubbed PI for production." I have tried to have AMD AES to fix/revisit/confirm this statement for 6 months now, since it has not been updated after all the binaryPI invention our partners in crime came up with. I have contacted AMD AES both directly and via their EMEA FAE, but they have pretty much zero response rate nowadays towards coreboot community. Kind Regards, Kyösti Mälkki

4 4

New post published at blog.coreboot.org on May 19, 2015 at 6:45 am
by WordPress 18 May '15

18 May '15

1 0

Error building Coreboot for MinnowBoard Max in Debian
by black015＠crimson.ua.edu 18 May '15

18 May '15

Hello members of the community This is my first time writing to the email list to ask for some help or insights about my problems building Coreboot. I apologize if I make some mistakes while attempting to communicate. My problem: I am trying to build Coreboot for my MinnowBoard Max following the instructions found in this book: Embedded Firmware Solutions: Development Best Practices for the Internet of Things. While executing “make crossgcc-i386” within the coreboot folder, the make throws this error: configure:3602: /home/juan/fsp_coreboot/coreboot/util/crossgcc/build-i386-elf-gcc/./gcc/xgcc -B/home/juan/fsp_coreboot/coreboot/util/crossgcc/build-i386-elf-gcc/./gcc/ -B/home/juan/fsp_coreboot/coreboot/util/crossgcc/xgcc/i386-elf/bin/ -B/home/juan/fsp_coreboot/coreboot/util/crossgcc/xgcc/i386-elf/lib/ -isystem /home/juan/fsp_coreboot/coreboot/util/crossgcc/xgcc/i386-elf/include -isystem /home/juan/fsp_coreboot/coreboot/util/crossgcc/xgcc/i386-elf/sys-include -c -O2 conftest.c >&5 cc1: internal compiler error: Illegal instruction 0x8844bf crash_signal ../../gcc-4.9.2/gcc/toplev.c:337 0x6ef7f8 ggc_min_expand_heuristic ../../gcc-4.9.2/gcc/ggc-common.c:840 0x6f02a8 init_ggc_heuristics() ../../gcc-4.9.2/gcc/ggc-common.c:899 0x885984 general_init ../../gcc-4.9.2/gcc/toplev.c:1176 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <http://gcc.gnu.org/bugs.html> for instructions. configure:3606: $? = 1 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "GNU C Runtime Library" | #define PACKAGE_TARNAME "libgcc" | #define PACKAGE_VERSION "1.0" | #define PACKAGE_STRING "GNU C Runtime Library 1.0" | #define PACKAGE_BUGREPORT "" | #define PACKAGE_URL "http://www.gnu.org/software/libgcc/" | /* end confdefs.h. */ | | int | main () | { | | ; | return 0; | } configure:3620: error: in `/home/juan/fsp_coreboot/coreboot/util/crossgcc/build-i386-elf-gcc/i386-elf/libgcc': configure:3623: error: cannot compute suffix of object files: cannot compile See `config.log' for more details. In any case, I am attaching the full “config.log” for you to review - if possible at all. I am running Debian 7.6 inside VirtualBox in an AMD A8-4500M Machine (64-bit) Thank you beforehand for any help or insights you may be able to provide. Juan Sent from Windows Mail

3 2

New post published at blog.coreboot.org on May 19, 2015 at 3:53 am
by WordPress 18 May '15

18 May '15

1 0

ASUS KFSN4-DRE Automated Test Failure
by Raptor Engineering Automated Coreboot Test Stand 18 May '15

18 May '15

The ASUS KFSN4-DRE fails verification as of commit 7267ccbae861d6acf7edfa256b758e2836e21945 The following tests failed: CBMEM_OBJECT_TABLE_TRUNCATED Commits since last successful test: 7267ccb libpayload: add mediatek timer driver 589e63e drivers/gic: reprogram the GIC CPU interface to bypass IRQ b7d0ffd arm64: psci: add cpu_suspend support 2e04259 cbfstool: Fix shadowed global index 2f7e56f x230/smihandler: Kill non-functional brightness code. <122 commits skipped> 2436bda cpu: get rid of socket source code 99cc1aa Mediawiki editing warning e9b7e25 util/xcompile/xcompile: Allow to override `HOSTCC` variable 939dc84 crossgcc: Re-download the archive if it is incomplete 6548ae9 cbfstool/Makefile*: Use `LDFLAGS` instead of `LINKFLAGS` See attached log for details This message was automatically generated from Raptor Engineering's ASUS KFSN4-DRE test stand Raptor Engineering offers coreboot consulting services! Please visit https://www.raptorengineeringinc.com for more information Please contact Timothy Pearson at Raptor Engineering <tpearson(a)raptorengineeringinc.com> regarding any issues stemming from this notification

1 0

ASUS KFSN4-DRE Automated Test Failure
by Raptor Engineering Automated Coreboot Test Stand 17 May '15

17 May '15

The ASUS KFSN4-DRE fails verification as of commit bb03aaa7b861e08aed2f35bd46cc6ec13be96b4d The following tests failed: CBMEM_OBJECT_TABLE_TRUNCATED Commits since last successful test: bb03aaa lenovo/x200: Enable wacom digitizer support for x200t 99bc2ec i945: Disable check for 2-dimm support. 3026e47 Remove defines APMC_FINALIZE. 5b667df util/inteltool: add Broadwell-U support 7780c4f rk3288: remove unused structs and declarations <116 commits skipped> 2436bda cpu: get rid of socket source code 99cc1aa Mediawiki editing warning e9b7e25 util/xcompile/xcompile: Allow to override `HOSTCC` variable 939dc84 crossgcc: Re-download the archive if it is incomplete 6548ae9 cbfstool/Makefile*: Use `LDFLAGS` instead of `LINKFLAGS` See attached log for details This message was automatically generated from Raptor Engineering's ASUS KFSN4-DRE test stand Raptor Engineering offers coreboot consulting services! Please visit https://www.raptorengineeringinc.com for more information Please contact Timothy Pearson at Raptor Engineering <tpearson(a)raptorengineeringinc.com> regarding any issues stemming from this notification

2 1

ASUS KFSN4-DRE Automated Test Failure
by Raptor Engineering Automated Coreboot Test Stand 16 May '15

16 May '15

The ASUS KFSN4-DRE fails verification as of commit 5b667df135dc4736f87d0650cc64b2c052bc9b73 The following tests failed: CBMEM_OBJECT_TABLE_TRUNCATED Commits since last successful test: 5b667df util/inteltool: add Broadwell-U support 7780c4f rk3288: remove unused structs and declarations 675a6d9 gigabyte/ga-b75m-d3: Fix SMBios version entry 633e827 x230: Fix ricoh driver. 9d45d69 ibexpeak: Merge common NVS init <113 commits skipped> 2436bda cpu: get rid of socket source code 99cc1aa Mediawiki editing warning e9b7e25 util/xcompile/xcompile: Allow to override `HOSTCC` variable 939dc84 crossgcc: Re-download the archive if it is incomplete 6548ae9 cbfstool/Makefile*: Use `LDFLAGS` instead of `LINKFLAGS` See attached log for details This message was automatically generated from Raptor Engineering's ASUS KFSN4-DRE test stand Raptor Engineering offers coreboot consulting services! Please visit https://www.raptorengineeringinc.com for more information Please contact Timothy Pearson at Raptor Engineering <tpearson(a)raptorengineeringinc.com> regarding any issues stemming from this notification

1 0

Re: [coreboot] coreboot fails to build in master tree
by Timothy Pearson 15 May '15

15 May '15

On 05/08/2015 08:20 PM, David Hendricks wrote: > Hi Timothy, > We were unable to replicate the failure you're seeing, however it did > appear that there may be an issue with the builder's environment. There > were also some patches that appeared to be committed in the wrong order, > thus causing a missing header error, but there were no merge conflicts > and after all the patches were merged things were fine. Sol uploaded a > dummy patch and the coreboot-gerrit builder had no trouble with it. > > Do you have more details about the environment in which you're seeing > this failure? That's interesting. Good to know it's isolated at least instead of breaking all builds. Example full build logs are available here: ASUS KFSN4-DRe: https://www.raptorengineeringinc.com/coreboot/autotest/logs/1431127557-0-10… QEMU x86_64 Q35: https://www.raptorengineeringinc.com/coreboot/autotest/logs/1431127541-1-10… The builders are up to date Debian Jessie systems. -- Timothy Pearson Raptor Engineering +1 (415) 727-8645 http://www.raptorengineeringinc.com

2 1

How to verify the real name of a commit author?
by Paul Menzel 15 May '15

15 May '15

Dear coreboot folks, change set #10208 [1] is currently blocked as there are doubts if that is the real name. > Signed-off-by: Pi Van Den Cirkel <opdecirkel(a)gmail.com> The development guidelines of coreboot contain the following sentence [2]. > You have to use your real name in the Signed-off-by line and in any > copyright notices you add. Is that just so that Gerrit works or does that have different reasons? The identities of the authors of other commits were never verified. So in dubio pro reo and we assume that is the correct name? Thanks, Paul [1] http://review.coreboot.org/10208 [2] http://www.coreboot.org/Development_Guidelines#Sign-off_Procedure

1 0

← Newer
1
2
3
4
5
6
7
...
12
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot May 2015