we are currently planning to host a coreboot conference in Germany with 2 days
of talks and an additional 2 days of hacking.
The date will probably either be October 19-22 or October 26-29, i.e. directly
before or after Embedded Linux Conference Europe and LinuxCon Europe.
Ticket prices haven't been decided yet and depend on the location and venue
The location will be either in Bonn or Bochum. Both Bochum and Bonn offer a
variety of interesting activities for conference participants.
Bochum is reachable by public transport from Frankfurt Airport within 120
minutes, from Dusseldorf Airport within 40 minutes and from Cologne Airport
within 80 minutes.
Bonn is reachable by public transport from Frankfurt Airport within 70
minutes, from Dusseldorf Airport within 70 minutes and from Cologne Airport
within 30 minutes.
YOUR ACTION NEEDED!
Please fill out the application and subscribe to the newsletter if you are
planning to join us!
Section CK 14 - Cyber Security in Operating Systems and Applications
Federal Office for Information Security (BSI)
Godesberger Allee 185-189
53175 Bonn, Germany
phone: +49 (0)228 9582-5939
fax: +49 (0)228 9582-5400
I'm happy to *finally* have the information and registration page online:
Yes, it's very late, but I hope that we will still be a good number
of people meeting up next weekend.
Quick feedback helps me make sure that everyone will get food.
If you are interested in attending, but unable to register at the
Community Registration Fee cost then please get in touch with me,
so that we can try to work something out.
Thank you very much, and hope to see you in Berlin on the 7:th!
Nice job all. Patrick, I'm looking forward t the next release detailing how
many files and lines were removed :-)
include, oh sad, the 440lx :-)
On Fri, Oct 30, 2015 at 1:38 PM Patrick Georgi <pgeorgi(a)google.com> wrote:
> (Halloween 2015 release - just as scary as that sounds)
> Dear coreboot community,
> today marks the release of coreboot 4.2, the second release on our
> time based release schedule.
> Since 4.1 there were 936 commits by 90 authors, increasing the code
> base by approximately 17000 lines of code. We saw 35 new contributors
> - welcome to coreboot! More than 34 developers were active as
> reviewers in that period.
> Thanks go to all contributors who helped shape this release.
> As with 4.1, the release tarballs are available at
> http://www.coreboot.org/releases/. There's also a 4.2 tag and branch
> in the git repository.
> This marks the first release that features a changelog comparing it to
> the previous release. There was some limited testing to make sure that
> the code is usable, and it boots on some devices. A structured test
> plan will only become part of the release procedure of future
> I'm grateful to Martin for assembling this release's changelog.
> This is also the first release that will be followed by the removal of
> old, unused code. There will be a policy on how to announce
> deprecation and removal of mainboard and chipset code for future
> Log of commit d5e6618a4f076610e683b174c4dd5108d960c785 to
> commit 439a527014fa0cb3e4ef60ba59e5c57c737b4444
> Changes between 4.1 and 4.2
> Build system:
> - Store a minimized coreboot config file in cbfs instead of the full config
> - Store the payload config and revision in CBFS when that info is available
> - Add -compression option for cbfs-files-y. Valid entries are now -file,
> -type, -align, and -compression
> - Change Microcode inclusion method from building .h files to pre-built
> - Update Builder tests for each commit to test utilities and run lint tools
> - Many other small makefile and build changes and fixes
> - Remove expert mode as a Kconfig option
> - Many fixes and updates to many utilities (158 total commits)
> - ifdtool: Update for skylake, handle region masks correctly
> - crossgcc: Update to gcc 5.2.0
> - kconfig: Add strict mode to fail on kconfig errors and warnings
> - vgabios: Significant fixes to remove issues in linking into coreboot code
> - Add script to parse MAINTAINERS file
> - Add Kconfig lint tool
> - Create a common library to share coreboot routines with utilities
> - Significant changes and cleanup to cbfstool (81 commits). Major changes:
> - Update cbfstool to change the internal location of FSP binaries when
> - Decompress stage files on extraction and turn them into ELF binaries
> - Header sizes are now variable, containing extended attributes
> - Add compression tags to all cbfs headers so all cbfs files can be
> - Add and align CBFS components in one pass instead of two
> - Add XIP support for X86 to relocate the romstage when it's added
> - Removed locate command as it's no longer needed
> - Add bootblock and cbfs_header file types so the master header knows about
> - Prefer FMAP data to CBFS master header if FMAP data exists
> - Add hashes to cbfs file metadata for verification of images
> - SeaBIOS: update stable release from 1.7.5 to 1.8.2
> - Libpayload had some significant changes (61 commits). Major changes:
> - Add support for fmap tables
> - Add support for SuperSpeed (3.0) USB hubs
> - Updates and bugfixes for DesignWare OTG controller (DWC2)
> - Add video_printf to print text with specified foreground & background
> - Updates to match changes to cbfs/cbfstool
> - Add cbgfx, a library to show graphics and text on a display
> - Read cbfs offset and size from sysinfo when available
> - fsp_baytrail: Support Baytrail FSP Gold 4 release
> - AMD binary PI: add support for fan control
> - Work to get AMD AGESA to compile correctly as 64-bit code
> - Add standalone (XIP) verstage support for x86 to verify romstage
> - New Mainboards:
> - apple/macbookair4_2 - Sandy/Ivy Bridge with Panther / Cougar point
> - asus/kgpe-d16 - AMD Family 10, SB700/SR5650 platform
> - emulation/spike-riscv - RISCV virtualized platform
> - google/chell - Intel Skylake chrome platform
> - google/cyan - Intel Braswell chrome platform
> - google/glados - Intel Skylake chrome platform
> - google/lars - Intel Skylake chrome platform
> - intel/kunimitsu - Intel Skylake chrome platform
> - intel/sklrvp - Intel Skylake reference platform
> - intel/strago - Intel Braswell chrome platform
> - Cleanups of many mainboards - several patches each for:
> - amd/bettong
> - getac/p470
> - google/auron, google/smaug and google/veyron_rialto
> - pcengines/apu1
> - siemens/mc_tcu3
> - Combine the google/veyron_(jerry, mighty, minnie, pinkie, shark &
> mainboards into the single google/veyron mainboard directory
> - Add EM100 'hyper term' spi console support in ramstage & smm
> - Add console support for verstage
> - armv7: use asm coded memory operations for 32/16 bit read/write
> - Many cleanups to the nvidia tegra chips (40 patches)
> - Add trap handling
> - Add virtual Memory setup
> - Remove and re-add Rangeley and Ivy Bridge / panther point FSP platforms
> - Update microcode update parser to use stock AMD microcode blobs from CBFS
> - ACPI: Align FACS to 64 byte boundary. Fixes FWTS error
> - AMD/SB700: Init devices in early boot, restore power state after power
> failure. Add IDE/SATA asl code
> - Add initial support for AMD Socket G34 processors
> - Add tick frequency to timestamp table to calculate boot times more
> - Unify X86 romstage / ramstage linking to match other platforms
> - Start preparing X86 bootblock for non-memory-mapped BIOS media
> - cpu/amd/car: Add Suspend to RAM (S3) support
> - Native VGA init fixes on several platforms
> - Significant updates to FSP 1.1 code for cleanup and cbfstool changes
> - SMMhandler: on i945..nehalem, crash if LAPIC overlaps with ASEG to
> the memory sinkhole smm hack
> - Add native text mode support for the Aspeed AST2050
> - w83795: Add support for for fan control and voltage monitoring
> - Intel GMA ACPI consolidation and improvements
> - Set up the 8254 timer before running option ROMs
> - Resource allocator: Page align memory mapped PCI resources
> - Derive fmap name from offset/size
> - Several edid fixes
> - Updates to cbfs matching changes in cbfstool
> Total commits: 16
> Log of commit 61d663e39bc96530900c3232ccea7365ab9dad0b to
> commit aab093f0824b6d26b57a1ce220ba0d577e37ad49
> - AMD Merlin Falcon: Update to CarrizoPI 184.108.40.206 (Binary PI 1.4)
> - AMD Steppe Eagle: Update to MullinsPI 1.0.0.A (Binary PI 1.1)
> - Update microcode to binary blobs. Remove old .h microcode files
> - No Changes
> Total commits: 41
> Log of commit fbf631c845c08299f0bcbae3f311c5807d34c0d6 to
> commit d6723ed12b429834c2627c009aab58f0db20ce73
> - Update the code to determine the write protect line gpio value
> - Several updates to futility and image_signing scripts
> - Update crossystem to accommodate Android mosys location
> - Support reboot requested by secdata
> - Add NV flag to default boot legacy OS
> - No Changes
> Google Germany GmbH, ABC-Str. 19, 20354 Hamburg
> Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft:
> Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle
> coreboot mailing list: coreboot(a)coreboot.org
Dear vendors, developers, users and interested parties,
on behalf of the Federal Office for Information Security (BSI) Germany I would
like to invite you to the coreboot conference and developer meeting on
October 9-11 2015 in Bonn, Germany.
This conference and developer meeting is geared towards manufacturers of
hardware (processors, chipsets, mainboards and servers/ laptops/ tablets/
desktops/ appliances) as well as developers of firmware with an interest in
coreboot and the possibilities it offers as well as (potential) coreboot
users. Both professionals and hobbyists are invited.
The Federal Office for Information Security (BSI) in Germany will host the
conference in Bonn, Germany. As the national cyber security authority, the
goal of the BSI is to promote IT security in Germany. For this reason, the
BSI has funded coreboot development in the past for security reasons.
The date of the coreboot conference is Friday October 9 to Sunday October 11,
2015. This is scheduled directly after Embedded Linux Conference Europe to
make travel arrangements easier for people attending both events.
If your main interest is forging business relationships and/or strategic
coordination and you want to skip the technical workshops, Friday (and
possibly Saturday) will be the outreach day of talks, presentations and
If your main interest is doing development, you can use the separate developer
room next to the during all three days of the conference.
Call for presentations:
We are looking for interesting talks/presentations about coreboot related
topics for the first (and possibly second) day of the conference. Please note
that those presentations are not intended to be advertisements or company
Expected duration is between 10 and 45 minutes.
Submission: Please send the title, a brief summary, the expected duration and
name/organization of the speaker to <coreboot-conference(a)bsi.bund.de> until
September 21. We will notify you of acceptance until September 28. If you
want us to make sure the slides work fine with the projector at the venue,
please submit your final slides in pdf form before Ocober 7.
Call for discussion topics and development suggestions:
We hope to stimulate discussion and foster new ideas as well as explore ways
to improve code, development and deployment. The format for this will be a
few minutes (1-5) of presenting your idea/topic followed by discussing it
with the audience for approximately 5-20 minutes. While there is no formal
deadline for submission, we'd appreciate a submission to
<coreboot-conference(a)bsi.bund.de> before October 2 to be able to list the
topic on the agenda to allow others to think about the topic in advance.
Call for profiles:
This is the chance to tell others what you're doing, what you can offer and in
what area you'd like to collaborate. If desired, we can attempt to distribute
your profile to other conference participants before the conference. Please
submit such profiles before September 30 to
Call for developers:
If you want to do development all day, every day, just come and do it. We have
power, networking and some spare hardware (please tell us in advance if you
need something on site, we might have it in our lab).
If you wonder about how to reach Bonn, there are three options available by
The closest is Cologne Airport (CGN), 30 minutes by bus to Bonn main station.
Next is Dusseldorf Airport (DUS), 1 hour by train to Bonn main station.
The airport with most international destinations is Frankfurt Airport (FRA), 1
hour by train to Bonn main station.
There’s the option to travel by train as well. Bonn is reachable by high-speed
train (ICE), and other high-speed train stations are reasonably close (30
Getting there (German only)
An English version of the directions will be available at
Accommodation is not centrally organized, but if desired we can point you to
websites listing hotel contact information and/or booking services as well as
the local tourist information office. We also have a small allotment of rooms
close to the venue reserved for conference participants, just ask us.
Spare time activities:
If there is enough interest, it might be possible to get a tour of the former
top secret bunker of the German Federal Government on Saturday evening. More
info at http://regbu.de/Fremdsprachen/GB1.html
Besides that, Bonn and Cologne have lots of tourist attractions
Food and drinks:
More info will be posted to http://coreboot.org/coreboot_conference_Bonn_2015
Date and time:
October 9-11 2015
To enable us to estimate the number of attendees (for catering etc.), please
notify us ASAP whether you will attend the conference at
<coreboot-conference(a)bsi.bund.de>. Thank you!
All information is also available at
Section C 13 - Operating System and Application Security
Federal Office for Information Security (BSI)
Godesberger Allee 185-189
53175 Bonn, Germany
phone: +49 (0)228 9582-5939
fax: +49 (0)228 9582-5400
Dear coreboot community members:
Marc, Ron, Patrick, Aaron and I have been discussing for a while about how
to make coreboot more accessible for businesses. We would like to found a
business organization (a.k.a. a coreboot consortium) that helps commercial
players out there to become a part of the coreboot community, share
marketing materials, and other efforts to promote the use of coreboot in
the market place and be successful with coreboot based solutions.
If you work for an organization that is using coreboot, developing
coreboot, or is just interested in coreboot, please help us learn about
your needs and wishes and fill out the following form: http://goo.gl/glhNh5
If you know someone who might be interested, but is not on this mailing
list, please forward this message to them.
coreboot will again have a booth at LinuxTag in Berlin, May 22-25,
in Hall 7.1c at Messe Berlin AKA "Messegelände unter dem Funkturm".
(Translation: Fairground under the radio tower.)
After LinuxTag we'll continue with a developer meeting/hackaton, May 26-27,
in the rooms of the community ISP IN-Berlin at Lehrter Straße 53, not far
from Berlin Hauptbahnhof, the central train station.
If you can join us for LinuxTag and/or for the developer meeting
please let us know your availability using the Doodle at
If you're interested in helping out at the LinuxTag booth please
email me off-list. We have a little bit more space this year, but
also many nice things to show off, and the Google guys will be doing
a workshop on Friday, May 24, about building a custom coreboot ROM
from scratch, and flashing it onto a Chromebook.
The developer meeting is free of charge thanks to the generosity of
our hosts at IN-Berlin, but please note that space is somewhat limited.
If there is overwhelming interest then priority will be given according
to general level of contributions in the community -- but don't be shy!!
If you would like to join then simply sign up at the Doodle.
For visitors who wish to book accomodation near the IN-Berlin
location here are a few suggestions in order of proximity:
* A&O Hostel and Hotel, Lehrter Str. 12, 700m down the street
* Berliner Stadtmission Christian Jugendgästehaus, Lehrter Str. 66, 950m
* Motel One, corner of Invalidenstr. and Lehrter Str., 1.2km
The central train station is in the opposite direction, ie. Motel One
is closest to the station.
S-Bahn line S5 toward Spandau departs from Hauptbahnhof track 16, the
7:th stop is Messe Süd where LinuxTag is.
NOTE: Several other S-lines depart from track 16, but only S5 Spandau
takes you to Messe Süd!
Remember to validate (insert into little red machine which timestamps)
your ticket if you travel by S-Bahn. The fine is 40 EUR and checks
especially on the east-west line are frequent-ish.
The developer meeting starts on Sunday morning and formally ends on
Monday afternoon but there may also be some informal meetings or
perhaps sightseeing excursions on Tuesday.
There are grocery stores nearby IN-Berlin, we can use the kitchen if
we want to, and they have an assortment of alcoholic and non-alcoholic
beverages as well as sweets for sale at low cost. There is however not
much in the way of restaurants nearby so I expect that we will order
lunch to be delivered to IN-Berlin but leave in the evening and hit
the city for dinner, and possibly tasty beverages.
Looking forward to meeting you in Berlin
Several coreboot project participants and followers will be in Hamburg
during this year's Chaos Communication Congress, also known as 29C3,
so let's go for dinner and a nice chat again, on the evening of
Let's meet near the CCH entrance as a starting point. There are not
really many restaurants just outside the CCH, but downtown Hamburg
is only a few hundred meters away from the venue, so I'm sure that
we will find something.
To repeat a tradition for coreboot in Hamburg we could visit Vapiano,
there is one near Axel-Springer-Platz on the other side of Gänsemarkt
seen from the CCH, about 1km on foot, but there are also plenty of
other choices along the way.
If I don't already know that you will be coming along and if you want
to make sure that we don't leave the CCH without you by mistake then
you can of course drop me an email. Just to be clear there is no
reservation, we'll just go ad-hoc to some restaurant. Feel free to
come along without sending me anything. Feel free to join us if you
are so far only curious about coreboot but have never even used it.
I'm looking forward to meeting you in Hamburg - see you there!
It is our pleasure to invite you to the coreboot booth at LinuxTag
in Berlin again this year. See http://linuxtag.org/2012/ for details.
We are located in hall 7.2b, booth 278, in the corner to the right of
the Open Source Arena stage, the same location as the last few years.
As usual we will showcase a nice system or two booting coreboot, this
time it's all about laptops!
We hope to also have some fun surprises for visitors in the booth,
but the final confirmation is not in just yet. Stop by and see if we
could make our ideas a reality in time! :)
Please be aware that if you plan to visit Messe Berlin by car, the
usual parking lot by the entrance is not available this year, since
the hall right in front of the entrance has been blown up, and the
whole area is currently a big construction site.
See you at the booth!
//Peter, Björn, and Paul
not so sure this justifies spam, but i have set up a twitter account
for coreboot (and flashrom): http://twitter.com/coreboot_org
the current plan is to setup a wordpress plugin to push headlines of new
blog posts there.
Kind regards/Mit freundlichen Grüßen, Stefan Tauner
Dear coreboot developers, stakeholders, and enthusiasts,
I'm glad to be able to announce that we moved the repository
infrastructure to git and gerrit, with jenkins as supporting facility.
This was done with the goal of improving the development workflow,
meaning less overhead for developers when managing the patch queue. This
should lead to losing fewer patch submissions.
So far we used patchwork, but it's more maintenance work than
practical given that it requires manual handling of patches that don't
match the commit diff, and of patches that went through multiple
While it improved the visibility of patches (and I'm thankful for that),
it still posed a higher than necessary barrier to patch review.
Gerrit is a code review utility developed by Google which uses the
distributed properties of git to provide a seamless path for patches
from submission to commit.
For this, git is used: Gerrit uses its ability to create and tear
down branches as necessary to push every contribution into its own
branch. This way it's already "tracked" by the version control system
without influencing the master branch.
The use of git also plays well into the desire of several coreboot
contributors to switch from svn to git.
In addition to these changes, we also moved the build bot from our own
custom build variant to a more standard Jenkins installation. In
addition to building commits after they are integrated on the master
branch ("trunk" in SVN terminology), it's also configured to build patch
submissions on gerrit as they come in. That way there's automated
feedback on a patch before spending time on it.
All this means that the coreboot development workflow changes
1. New SCM
You will need git, so install it from your usual software distribution
For patch submission a gerrit account is necessary. You can register it
on http://review.coreboot.org. With the account you can also review
patches. The ability to merge patches to mainline will be granted by
ssh public keys are used for authentication. You can register them with
gerrit in your user preferences at http://review.coreboot.org/#settings
when logged in.
Gerrit requires that the commit message contains Change-Id: lines. "make
gitconfig" inside a coreboot checkout installs a commit message handler
which takes care of this.
The committer address must match an email address that is registered
with your gerrit acccount. Again these can be configured in gerrit user
Fetching anonymously: git clone http://review.coreboot.org/p/coreboot
Fetching authenticated: git clone
2. New patch submission process
Develop "as usual" in git, and commit freely.
When you're ready to submit patches, push them with
git push origin HEAD:refs/for/master
This will tell gerrit which branch your commits are for (master) and it
will create internal branches for each commit you pushed, making them
separate changesets. If you push a number of commits at once, they're
properly linked as "dependencies", so people (and tools like gerrit and
jenkins) are aware about prerequisites.
For automating some aspects of patch submission, see the last paragraph
We will also document more of making live easier at
http://www.coreboot.org/Git as best practices are established.
3. New patch review process
The main interface to do patch reviews is the gerrit webapp at
http://review.coreboot.org. For those who tend to avoid web apps,
there's the option of controlling gerrit via ssh. Detailed information
on that will be posted at http://www.coreboot.org/Git.
There's no real workflow defined around this interface yet because it
seems to be an unpopular choice as _User_ Interface. This means, we'll
have to develop our own.
4. Mail notification
Mail notification to the mailing list is implemented from scratch. Right
now it only reports on new patch submissions and on patches merged into
the master branch. More events might/will follow in future, and we will
certainly tweak the ad-hoc messages and formatting some more.
Questions? Comments? Praise? Flames?