benoit | 10 Feb 22:00 2016
Picon

Can not have IRQ from ethernet device connected to the PCIe #4 in legacy mode

Hi all,

I am facing a legacy IRQ under OS.
I am currently using Coreboot + FSP on baytrail.
My OS is running with IRQ in legacy using PIRQ described in
coreboot/src/mainboard/intel/bayleybay_fsp/irqroute.h .
Under the OS USB, SATA, SMBus are working well using legacy interrupt.
Nevertheless I have an ethernet device connected on the PCIe root #4 and
no IRQs are received.

I tried to change the IRQ in the interrupt line register without success.

I can compare also with a Phoenix BIOS, and with the same OS binary the
ethernet is working.

I check out also the ilb registers + 0x4d0 and 0x4d1 registers (ECL).
Everything is correctly initalized.

Do I need to activate/deactivate something in the PCIe root #4 to
forward legacy interrupt to the 8259 PIC ?

Many thanks in advance
Benoit

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Google Summer of Code 2016

Hi all,

so Google just announced[0] that they're running their Summer of Code
program again.
I'm preparing to be the project admin this year, but to make this real
we'll need contributors that are willing to step up as mentors. I need
to know the number of candidates by Feb 19th, and we're told by end of
February if we participate in the program this year.

If so, students will apply in March and we'll try to find mentors for
them (ideally two per student).

We expect mentors to help students get comfortable in the community
and to support them with their project.
The "active" time for students (and thus also mentors) begins late
April with the "community bonding period" and ends late August with
the end of the "coding" phase of the program. Mentors should be
available for their students in that time frame, although one reason
for planning for two mentors per students is to allow for vacation and
the like.

If you're still interested in mentoring, please tell me so I can
update the number of mentor candidates (which I need to state in the
project's application to GSoC).

If you have ideas that are possible to work through with ~3 months of
effort by a new contributor, please add them to our project ideas wiki
page[1] (that I still need to clean up a bit).

Thanks,
(Continue reading)

Denis 'GNUtoo' Carikli | 8 Feb 23:19 2016

Removed boards list.

Hi,

When boards are removed, they are also automatically removed from the
supported boards page[1] in the wiki.

The unfortunate downside is that, assuming that coreboot worked fine on
such boards in the past (and may still do), they don't show up in any
list.

A place where to put the list of such boards already exist in the
wiki[2].

Would it be possible to get such page updated (for instance by the
commit author) when the commit has been pushed to master?

A pointer to the commit would also be very appreciated, like I did in
"Graveyard (v4, - v4.2)" status.

The use case I had in mind was to make it easier to check if a given
board was supported, and how (by pointing to its commit).

References:
-----------
[1]https://www.coreboot.org/Supported_Motherboards
[2]https://www.coreboot.org/Graveyard

Denis.
--

-- 
(Continue reading)

Christopher Grossarth | 5 Feb 20:00 2016
Picon

Lenovo Thinkpad Yoga 11e (Windows Version)

I would like to build coreboot for the Thinkpad Yoga 11e (Model 20DAS02N00). It is the Windows version of the hardware, with a 2.5" HDD, ethernet port, and removable RAM chips (currently 2x4GB).

I do not know the best procedure for this; should I attempt to edit the GLIMMER board config to more closely match the differences in the hardwares, or start with a RAMBI config and build off that?

I have succesfully built and flashed libreboot for the Macbook 2,1, but libreboot is limited to a few models and the documentation is vague for building for new boards.

Any help will be greatly appreciated.

Best,

-nobodyweird
--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

ASUS KGPE-D16 Automated Test Failure

The ASUS KGPE-D16 fails verification as of commit 4af905ac95685500e71fb32cf5cec430d1a75447

The following tests failed:
BOOT_FAILURE

Commits since last successful test:
4af905a skylake boards: disable ACPI PM Timer
6c1bf27 intel/skylake: disable ACPI PM Timer to enable XTAL OSC shutdown
50c3ba2 intel/skylake: unconditionally set SPI controller BAR
4121f9e google/chromeos/vboot2: honor boot region device size
f52fb2f google/lars: perform early init for CAR *stage

<10 commits skipped>

87c9fae chromeos/vboot: provide support for x86 memory init verification
43e6d6a 3rdparty/vboot: update to current master
9dca83c intel/skylake: Display ME firmware status before os boot
e2cea4f google/chromeec: Add temporary storage interface
eb31685 google/chromeec: Update EC command header

See attached log for details

This message was automatically generated from Raptor Engineering's ASUS KGPE-D16 test stand
Want to test on your own equipment?  Check out https://www.raptorengineeringinc.com/content/REACTS/intro.html

Raptor Engineering also offers coreboot consulting services!  Please visit
https://www.raptorengineeringinc.com for more information

Please contact Timothy Pearson at Raptor Engineering <tpearson <at> raptorengineeringinc.com> regarding
any issues stemming from this notification
BZh91AY&SY| <at> -
--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

RFC: coding style: "standard" defines

Hi all,

during the review of some commits that are in the process of being
upstreamed from Chrome OS, people noticed that chipset drivers like to
define their own TRUE/FALSE defines (sometimes prefixed to), and I
have seen a bunch of #define BIT{0-31} ..., too, because that seems to
be the house rules in some firmware communities.

I think we should seek uniformity here: decide on some style,
recommend it, clean up the tree to match, and help people stay
consistent through lint tests. What I don't know however is what that
style should look like.

So, two topics:

1. TRUE/FALSE
Do we want such defines? If so, TRUE/FALSE, or true/false, or
True/False, or ...?

2. BIT16 vs BIT(16) vs (1 << 16) vs 0x10000
I don't think it makes sense to go for a single one of these (0x3ff is
certainly more readable than BIT11 | BIT10 | BIT9 | BIT8 | BIT7 | BIT8
| BIT5 | BIT4 | BIT3 | BIT2 | BIT1 | BIT 0), but I doubt we need both
BIT16 and BIT(16).

Patrick
-- 
Google Germany GmbH, ABC-Str. 19, 20354 Hamburg
Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: Hamburg
Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

ASUS KGPE-D16 Automated Test Failure

The ASUS KGPE-D16 fails verification as of commit e3f47eada383defcc31b41cc4931c3cf3234c37d

The following tests failed:
BOOT_FAILURE

Commits since last successful test:
e3f47ea vendorcode/amd/agesa/f1{4,2,0} Sync Include directory
c389635 vendorcode/amd/agesa/f15?tn: Strip false/redudant AMD ver tag
11a262c util/kconfig:xconf(QT): Update QT version of xconf
420caaf include/device: Move inline functions from pci_def.h to pci.h

See attached log for details

This message was automatically generated from Raptor Engineering's ASUS KGPE-D16 test stand
Want to test on your own equipment?  Check out https://www.raptorengineeringinc.com/content/REACTS/intro.html

Raptor Engineering also offers coreboot consulting services!  Please visit
https://www.raptorengineeringinc.com for more information

Please contact Timothy Pearson at Raptor Engineering <tpearson <at> raptorengineeringinc.com> regarding
any issues stemming from this notification
Attachment (1454470983-3-automaster.log.bz2): application/octet-stream, 49 KiB
--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
김유석 | 2 Feb 08:40 2016
Picon

bootfail on my Mohon Peak CRB.

Dear sir.

My ENV is see below.

  EVB : Intel rangeley Mohon Peak CRB


This time, I was download the coreboot from git.
  
  poplinux <at> raw work $ > git clone http://review.coreboot.org/coreboot.git ./
  poplinux <at> raw work $ > cd coreboot
  poplinux <at> raw coreboot $ > git submodule update --init --checkout
 
Next, run make menuconfig and set-up to mohon peak CRB and save & exit

  Mainboard
       Mainboard vendor (Intel)  --->
       Mainboard model (Mohon Peak CRB)  --->
   [ ] Configure defaults for the Intel FSP package 
       ROM chip size (2048 KB (2 MB))  ---> 
   (0x00200000) Size of CBFS filesystem in ROM  
   ()  fmap description file in fmd format

Next, I'm try to build core boot.

  poplinux <at> raw coreboot $ > make
    GEN        generated/bootblock.ld
    CP         bootblock/arch/x86/bootblock.ld
    LINK       cbfs/fallback/bootblock.debug
    OBJCOPY    cbfs/fallback/bootblock.elf
    OBJCOPY    bootblock.raw.bin
    Checking out SeaBIOS revision 01a84bea2d28a19d2405c1ecac4bdef17683cc0c
Switched to branch 'master'

  Performing operation on 'COREBOOT' region...
  Name                           Offset     Type         Size
  cbfs master header             0x0        cbfs header  32
  fallback/romstage              0x80       stage        22684
  cpu_microcode_blob.bin         0x5980     microcode    0
  config                         0x5a00     raw          127
  revision                       0x5ac0     raw          570
  cmos_layout.bin                0x5d40     cmos_layout  1316
  fallback/dsdt.aml              0x62c0     raw          7952
  payload_config                 0x8240     raw          1574
  payload_revision               0x88c0     raw          237
  (empty)                        0x8a00     null         29848
  mrc.cache                      0xfec0     mrc_cache    65536
  fallback/ramstage              0x1ff00    stage        46922
  fallback/payload               0x2b6c0    payload      61122
  (empty)                        0x3a5c0    null         1856216
  bootblock                      0x1ff8c0   bootblock    1528

Finally, I'm got a coreboot image.


  poplinux <at> raw build $ > ls build/coreboot.rom
  build/coreboot.rom
  poplinux <at> raw build $ > ./build/cbfstool build/coreboot.rom print
  Performing operation on 'COREBOOT' region...
  Name                           Offset     Type         Size
  cbfs master header             0x0        cbfs header  32
  fallback/romstage              0x80       stage        22684
  cpu_microcode_blob.bin         0x5980     microcode    0
  config                         0x5a00     raw          127
  revision                       0x5ac0     raw          570
  cmos_layout.bin                0x5d40     cmos_layout  1316
  fallback/dsdt.aml              0x62c0     raw          7952
  payload_config                 0x8240     raw          1574
  payload_revision               0x88c0     raw          237
  (empty)                        0x8a00     null         29848
  mrc.cache                      0xfec0     mrc_cache    65536
  fallback/ramstage              0x1ff00    stage        46922
  fallback/payload               0x2b6c0    payload      61122
  (empty)                        0x3a5c0    null         1856216
  bootblock                      0x1ff8c0   bootblock    1528


And I'm write image to my EVB using ALL-100 Gang-writer.
spi flash's write start address is set 0x00000000. write it success.

And I'm attach the flash memory to my EVB.

And power-up the my EVB. But can't see any message on my monitor and serial port both.


Why did not display any message?
And could you support correct configuration file for my EVB?

Thank you.






--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

ASUS KGPE-D16 Automated Test Failure

The ASUS KGPE-D16 fails verification as of commit 68e3f6dd371ced6963802295e1e176dca5729d2f

The following tests failed:
BOOT_FAILURE

Commits since last successful test:
68e3f6d util/release: extend release script

See attached log for details

This message was automatically generated from Raptor Engineering's ASUS KGPE-D16 test stand
Want to test on your own equipment?  Check out https://www.raptorengineeringinc.com/content/REACTS/intro.html

Raptor Engineering also offers coreboot consulting services!  Please visit
https://www.raptorengineeringinc.com for more information

Please contact Timothy Pearson at Raptor Engineering <tpearson <at> raptorengineeringinc.com> regarding
any issues stemming from this notification
Attachment (1454315580-3-automaster.log.bz2): application/octet-stream, 51 KiB
--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
Alexander Couzens | 31 Jan 20:15 2016
Picon
Gravatar

berlin coreboot user group meeting 17.02.2016 18:00

hey,

the next coreboot user group meeting is on 17.02. at 1800 as usual at
club discordia / cccb.

everybody is welcome. I'll take some flasher with me, but it's still a
good idea to send me an email so everything is prepared for your
coreboot installation ;)

best,
lynxis
-- 
Alexander Couzens

mail: lynxis <at> fe80.eu
jabber: lynxis <at> fe80.eu
mobile: +4915123277221
gpg: 390D CF78 8BF9 AA50 4F8F  F1E2 C29E 9DA6 A0DF 8604
--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
WordPress | 29 Jan 23:06 2016

New on blogs.coreboot.org: Announcing coreboot 4.3

A new post titled "Announcing coreboot 4.3" has been published on the coreboot blog. Find the full post at http://blogs.coreboot.org/blog/2016/01/29/announcing-coreboot-4-3/

Dear coreboot community,

today marks the release of coreboot 4.3, the third release on our time based release schedule.
Since the last release, 1030 commits by 114 authors added a net total of 17500 lines to the source code. Thank you to all who contributed!

The release tarballs are available at http://www.coreboot.org/releases/. There’s also a 4.3 tag and branch in the git repository.

Besides the usual addition of new mainboards (14) and chipsets (various), a big theme of the development since 4.2 was cleaning up the code: 20 mainboards were removed that aren’t on the market for years (and even hard to get on Ebay). For several parts of the tree, we established tighter controls, making errors out of what were warnings (and cleaning up the code to match) and provided better tests for various aspects of the tree, and in general tried to establish a more consistent structure across the code base.

Besides that, we had various improvements across the tree, each important when using the hardware, but to numerous for individual shout outs. Martin compiled a list that’s best posted verbatim. Thanks Martin!

Log of commit 529fd81f640fa514ea4c443dd561086e7c582a64 to commit 1bf5e6409678d04fd15f9625460078853118521c for a total of 1030 commits:

Mainboards

Added 14 mainboards

– asus/kfsn4-dre_k8: Native init Dual AMD K8 CPUs & Nvidia CK804 southbridge
– esd/atom15: Bay Trail SOC mainboard using Intel’s FSP
– gigabyte/ga-g41m-es2l: Intel Core 2 / Native init x4x NB / I82801GX SB
– google/guado: Intel Broadwell chromebox (Asus Chromebox CN62)
– google/oak: Mediatek MT8173 SoC chromebook
– google/tidus: Intel Broadwell chromebox (Lenovo ThinkCentre Chromebox)
– google/veyron_emile: Rockchip RK3288 SoC board
– intel/d510mo: Native init Intel Pineview with Intel I82801GX southbridge
– intel/littleplains: Intel Atom c2000 (Rangeley) SoC board
– intel/stargo2: Intel Ivy Bridge / Cave Creek usint Intel’s FSP
– lenovo/r400: Intel Core 2 / Native init GM45 NB / Intel I82801IX SB
– lenovo/t500: Intel Core 2 / Native init GM45 NB / Intel I82801IX SB
– purism/librem13: Intel Broadwell Laptop using Intel MRC
– sunw/ultra40m2: Native init Dual AMD K8 Processors & Nvidia MCP55 SB

Removed 20 mainboards

– arima/hdama
– digitallogic/adl855pc
– ibm/e325, e326
– intel/sklrvp
– iwill/dk8s2, dk8x
– newisys/khepri
– tyan/s2735, s2850, s2875, s2880, s2881 & s2882
– tyan/s2885, s2891, s2892, s2895, s4880 & s4882

Improvements to mainboards

– amd/bettong: fixes to Interrupts, Memory config, S4, EMMC, UARTS
– asus/kgpe-d16: IOMMU and memory fixes, Add CMOS options, Enable GART
– intel/strago: GPIO, DDR, & SD config, FSP updates, Clock fixes
– ACPI fixes across various platforms
– Many individual fixes to other mainboards

Continued updates for the Intel Skylake platform

– google/chell, glados, & lars: FSP & Memory updates, Add Fan & NHLT support
– intel/kunimitsu: FSP & GPIO updates, Add Fan & NHLT (audio) support

Build system

– Update build to use FMAP based firmware layout with multiple cbfs sections
– Enable Kconfig strict mode – Kconfig warnings are no longer allowed.
– Enable ACPI warnings are errors in IASL – warnings are no longer allowed.
– Tighten checking on toolchains and give feedback to users if there are issues
– Updates to get the ADA compiler to work correctly for coreboot
– Various improvements to Makefiles and build scripts
– Cleanup of CBFS file handling

Utilities

– cleanups and improvements to many of the utilities
– cbfstool: Many fixes and extensions to integrate with FMAP
– Add amdfwtool to combine AMD firmware blobs instead of using shell scripts.
– Toolchain updates: new versions of GMP & MPFR. Add ADA.
– Updates for building on NetBSD & OS X

Payloads

– SeaBIOS: Update stable release to 1.9.0
– coreinfo: fix date, hide cursor, use crosscompiler to build
– libpayload: updates for cbfs, XHCI and DesignWare HCD controllers

ARM

– Added 1 soc: mediatek/mt8173
– Various fixes for ARM64 platforms

X86

– Added 2 northbridges: intel/pineview & x4x
– Removed 1 northbridge: intel/i440lx
– Added 1 southbridge: intel/fsp_i89xx
– Removed 2 southbridge(s): intel/esb6300 & i82801cx
– Rename amd/model_10xxx to family_10h-family_15h.
– ACPI: fix warnings, Add functions for IVRS, DMAR I/O-APIC and HPET entries
– Work in many areas fixing issues compiling in 64-bit
– Numerous other fixes across the tree

Areas with significant work on updates and fixes

– cpu/amd/model_fxx
– intel/fsp1_x: Fix timestanps & postcodes, add native CAR & microcode
– nb/amd/amdfam10: Add S3, voltage & ACPI, speed fixes & MANY other changes
– nb/amd/amdmct: Add S3, mem voltage, Fix performance & MANY other changes
– nb/intel/sandybridge: Add IOMMU & ACPI DMAR support, Memory cleanup
– soc/intel/braswell: FSP & ACPI updates, GPIO & clock Fixes
– soc/intel/fsp_baytrail: GPIO, microcode and Interrupt updates.
– soc/intel/skylake: FSP, Power/Thermal & GPIO Updates, Add NHLT support
– sb/amd/sb700: Add ACPI & CMOS Setting support, SATA & clock Fixes

MIPS

– Imgtec Pistachio: Memory, PLL & I2C fixes, add reset

SuperIO

– Expand functionality for ite/it8718f & nuvoton/nct5572d superio devices

Added 3 SIOs

– intel/i8900
– winbond/w83667hg-a & wpcd376i

Removed 6 SIOs

– fintek/f71889
– ite/it8661f
– nsc/pc8374 & pc97307
– nuvoton/nct6776
– smsc/fdc37m60x

Lib

– Several updates for reading EDID tables

MISC

– Commonlib: continued updates for cbfs changes
– Work on getting license headers on all coreboot files
– Drop the third paragraph of GPL copyright header across all of coreboot

Submodules

3rdparty/blobs: Update to CarrizoPI 1.1.0.1 (Binary PI 1.5)

coreboot statistics

Total commits: 1030
Total authors: 114
New authors: 46
Total Reviewers: 41
Total lines added: 88255
Total lines removed: -70735
Total delta: 17520

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Gmane