CINXE.COM
coreboot – coreboot
<!DOCTYPE html> <html lang="en-US" xmlns:og="http://opengraphprotocol.org/schema/" xmlns:fb="http://www.facebook.com/2008/fbml" itemscope itemtype="http://schema.org/Article" class="no-js"> <head> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <link rel="profile" href="http://gmpg.org/xfn/11"> <link rel="pingback" href="https://blogs.coreboot.org/xmlrpc.php"> <!--[if lt IE 9]> <script src="https://blogs.coreboot.org/wp-content/themes/twentyfifteen/js/html5.js"></script> <![endif]--> <script>(function(){document.documentElement.className='js'})();</script> <script>(function(html){html.className = html.className.replace(/\bno-js\b/,'js')})(document.documentElement);</script> <title>coreboot – coreboot</title> <meta name='robots' content='max-image-preview:large' /> <style>img:is([sizes="auto" i], [sizes^="auto," i]) { contain-intrinsic-size: 3000px 1500px }</style> <link rel='dns-prefetch' href='//blogs.coreboot.org' /> <link rel="alternate" type="application/rss+xml" title="coreboot » Feed" href="https://blogs.coreboot.org/feed/" /> <link rel="alternate" type="application/rss+xml" title="coreboot » Comments Feed" href="https://blogs.coreboot.org/comments/feed/" /> <link rel="alternate" type="application/rss+xml" title="coreboot » coreboot Category Feed" href="https://blogs.coreboot.org/blog/category/coreboot/feed/" /> <link rel='stylesheet' id='wp-block-library-css' href='https://blogs.coreboot.org/wp-includes/css/dist/block-library/style.min.css?ver=6.7.1' media='all' /> <style id='wp-block-library-theme-inline-css'> .wp-block-audio :where(figcaption){color:#555;font-size:13px;text-align:center}.is-dark-theme .wp-block-audio :where(figcaption){color:#ffffffa6}.wp-block-audio{margin:0 0 1em}.wp-block-code{border:1px solid #ccc;border-radius:4px;font-family:Menlo,Consolas,monaco,monospace;padding:.8em 1em}.wp-block-embed :where(figcaption){color:#555;font-size:13px;text-align:center}.is-dark-theme .wp-block-embed :where(figcaption){color:#ffffffa6}.wp-block-embed{margin:0 0 1em}.blocks-gallery-caption{color:#555;font-size:13px;text-align:center}.is-dark-theme .blocks-gallery-caption{color:#ffffffa6}:root :where(.wp-block-image figcaption){color:#555;font-size:13px;text-align:center}.is-dark-theme :root :where(.wp-block-image figcaption){color:#ffffffa6}.wp-block-image{margin:0 0 1em}.wp-block-pullquote{border-bottom:4px solid;border-top:4px solid;color:currentColor;margin-bottom:1.75em}.wp-block-pullquote cite,.wp-block-pullquote footer,.wp-block-pullquote__citation{color:currentColor;font-size:.8125em;font-style:normal;text-transform:uppercase}.wp-block-quote{border-left:.25em solid;margin:0 0 1.75em;padding-left:1em}.wp-block-quote cite,.wp-block-quote footer{color:currentColor;font-size:.8125em;font-style:normal;position:relative}.wp-block-quote:where(.has-text-align-right){border-left:none;border-right:.25em solid;padding-left:0;padding-right:1em}.wp-block-quote:where(.has-text-align-center){border:none;padding-left:0}.wp-block-quote.is-large,.wp-block-quote.is-style-large,.wp-block-quote:where(.is-style-plain){border:none}.wp-block-search .wp-block-search__label{font-weight:700}.wp-block-search__button{border:1px solid #ccc;padding:.375em .625em}:where(.wp-block-group.has-background){padding:1.25em 2.375em}.wp-block-separator.has-css-opacity{opacity:.4}.wp-block-separator{border:none;border-bottom:2px solid;margin-left:auto;margin-right:auto}.wp-block-separator.has-alpha-channel-opacity{opacity:1}.wp-block-separator:not(.is-style-wide):not(.is-style-dots){width:100px}.wp-block-separator.has-background:not(.is-style-dots){border-bottom:none;height:1px}.wp-block-separator.has-background:not(.is-style-wide):not(.is-style-dots){height:2px}.wp-block-table{margin:0 0 1em}.wp-block-table td,.wp-block-table th{word-break:normal}.wp-block-table :where(figcaption){color:#555;font-size:13px;text-align:center}.is-dark-theme .wp-block-table :where(figcaption){color:#ffffffa6}.wp-block-video :where(figcaption){color:#555;font-size:13px;text-align:center}.is-dark-theme .wp-block-video :where(figcaption){color:#ffffffa6}.wp-block-video{margin:0 0 1em}:root :where(.wp-block-template-part.has-background){margin-bottom:0;margin-top:0;padding:1.25em 2.375em} </style> <style id='classic-theme-styles-inline-css'> /*! This file is auto-generated */ .wp-block-button__link{color:#fff;background-color:#32373c;border-radius:9999px;box-shadow:none;text-decoration:none;padding:calc(.667em + 2px) calc(1.333em + 2px);font-size:1.125em}.wp-block-file__button{background:#32373c;color:#fff;text-decoration:none} </style> <style id='global-styles-inline-css'> :root{--wp--preset--aspect-ratio--square: 1;--wp--preset--aspect-ratio--4-3: 4/3;--wp--preset--aspect-ratio--3-4: 3/4;--wp--preset--aspect-ratio--3-2: 3/2;--wp--preset--aspect-ratio--2-3: 2/3;--wp--preset--aspect-ratio--16-9: 16/9;--wp--preset--aspect-ratio--9-16: 9/16;--wp--preset--color--black: #000000;--wp--preset--color--cyan-bluish-gray: #abb8c3;--wp--preset--color--white: #fff;--wp--preset--color--pale-pink: #f78da7;--wp--preset--color--vivid-red: #cf2e2e;--wp--preset--color--luminous-vivid-orange: #ff6900;--wp--preset--color--luminous-vivid-amber: #fcb900;--wp--preset--color--light-green-cyan: #7bdcb5;--wp--preset--color--vivid-green-cyan: #00d084;--wp--preset--color--pale-cyan-blue: #8ed1fc;--wp--preset--color--vivid-cyan-blue: #0693e3;--wp--preset--color--vivid-purple: #9b51e0;--wp--preset--color--dark-gray: #111;--wp--preset--color--light-gray: #f1f1f1;--wp--preset--color--yellow: #f4ca16;--wp--preset--color--dark-brown: #352712;--wp--preset--color--medium-pink: #e53b51;--wp--preset--color--light-pink: #ffe5d1;--wp--preset--color--dark-purple: #2e2256;--wp--preset--color--purple: #674970;--wp--preset--color--blue-gray: #22313f;--wp--preset--color--bright-blue: #55c3dc;--wp--preset--color--light-blue: #e9f2f9;--wp--preset--gradient--vivid-cyan-blue-to-vivid-purple: linear-gradient(135deg,rgba(6,147,227,1) 0%,rgb(155,81,224) 100%);--wp--preset--gradient--light-green-cyan-to-vivid-green-cyan: linear-gradient(135deg,rgb(122,220,180) 0%,rgb(0,208,130) 100%);--wp--preset--gradient--luminous-vivid-amber-to-luminous-vivid-orange: linear-gradient(135deg,rgba(252,185,0,1) 0%,rgba(255,105,0,1) 100%);--wp--preset--gradient--luminous-vivid-orange-to-vivid-red: linear-gradient(135deg,rgba(255,105,0,1) 0%,rgb(207,46,46) 100%);--wp--preset--gradient--very-light-gray-to-cyan-bluish-gray: linear-gradient(135deg,rgb(238,238,238) 0%,rgb(169,184,195) 100%);--wp--preset--gradient--cool-to-warm-spectrum: linear-gradient(135deg,rgb(74,234,220) 0%,rgb(151,120,209) 20%,rgb(207,42,186) 40%,rgb(238,44,130) 60%,rgb(251,105,98) 80%,rgb(254,248,76) 100%);--wp--preset--gradient--blush-light-purple: linear-gradient(135deg,rgb(255,206,236) 0%,rgb(152,150,240) 100%);--wp--preset--gradient--blush-bordeaux: linear-gradient(135deg,rgb(254,205,165) 0%,rgb(254,45,45) 50%,rgb(107,0,62) 100%);--wp--preset--gradient--luminous-dusk: linear-gradient(135deg,rgb(255,203,112) 0%,rgb(199,81,192) 50%,rgb(65,88,208) 100%);--wp--preset--gradient--pale-ocean: linear-gradient(135deg,rgb(255,245,203) 0%,rgb(182,227,212) 50%,rgb(51,167,181) 100%);--wp--preset--gradient--electric-grass: linear-gradient(135deg,rgb(202,248,128) 0%,rgb(113,206,126) 100%);--wp--preset--gradient--midnight: linear-gradient(135deg,rgb(2,3,129) 0%,rgb(40,116,252) 100%);--wp--preset--gradient--dark-gray-gradient-gradient: linear-gradient(90deg, rgba(17,17,17,1) 0%, rgba(42,42,42,1) 100%);--wp--preset--gradient--light-gray-gradient: linear-gradient(90deg, rgba(241,241,241,1) 0%, rgba(215,215,215,1) 100%);--wp--preset--gradient--white-gradient: linear-gradient(90deg, rgba(255,255,255,1) 0%, rgba(230,230,230,1) 100%);--wp--preset--gradient--yellow-gradient: linear-gradient(90deg, rgba(244,202,22,1) 0%, rgba(205,168,10,1) 100%);--wp--preset--gradient--dark-brown-gradient: linear-gradient(90deg, rgba(53,39,18,1) 0%, rgba(91,67,31,1) 100%);--wp--preset--gradient--medium-pink-gradient: linear-gradient(90deg, rgba(229,59,81,1) 0%, rgba(209,28,51,1) 100%);--wp--preset--gradient--light-pink-gradient: linear-gradient(90deg, rgba(255,229,209,1) 0%, rgba(255,200,158,1) 100%);--wp--preset--gradient--dark-purple-gradient: linear-gradient(90deg, rgba(46,34,86,1) 0%, rgba(66,48,123,1) 100%);--wp--preset--gradient--purple-gradient: linear-gradient(90deg, rgba(103,73,112,1) 0%, rgba(131,93,143,1) 100%);--wp--preset--gradient--blue-gray-gradient: linear-gradient(90deg, rgba(34,49,63,1) 0%, rgba(52,75,96,1) 100%);--wp--preset--gradient--bright-blue-gradient: linear-gradient(90deg, rgba(85,195,220,1) 0%, rgba(43,180,211,1) 100%);--wp--preset--gradient--light-blue-gradient: linear-gradient(90deg, rgba(233,242,249,1) 0%, rgba(193,218,238,1) 100%);--wp--preset--font-size--small: 13px;--wp--preset--font-size--medium: 20px;--wp--preset--font-size--large: 36px;--wp--preset--font-size--x-large: 42px;--wp--preset--spacing--20: 0.44rem;--wp--preset--spacing--30: 0.67rem;--wp--preset--spacing--40: 1rem;--wp--preset--spacing--50: 1.5rem;--wp--preset--spacing--60: 2.25rem;--wp--preset--spacing--70: 3.38rem;--wp--preset--spacing--80: 5.06rem;--wp--preset--shadow--natural: 6px 6px 9px rgba(0, 0, 0, 0.2);--wp--preset--shadow--deep: 12px 12px 50px rgba(0, 0, 0, 0.4);--wp--preset--shadow--sharp: 6px 6px 0px rgba(0, 0, 0, 0.2);--wp--preset--shadow--outlined: 6px 6px 0px -3px rgba(255, 255, 255, 1), 6px 6px rgba(0, 0, 0, 1);--wp--preset--shadow--crisp: 6px 6px 0px rgba(0, 0, 0, 1);}:where(.is-layout-flex){gap: 0.5em;}:where(.is-layout-grid){gap: 0.5em;}body .is-layout-flex{display: flex;}.is-layout-flex{flex-wrap: wrap;align-items: center;}.is-layout-flex > :is(*, div){margin: 0;}body .is-layout-grid{display: grid;}.is-layout-grid > :is(*, div){margin: 0;}:where(.wp-block-columns.is-layout-flex){gap: 2em;}:where(.wp-block-columns.is-layout-grid){gap: 2em;}:where(.wp-block-post-template.is-layout-flex){gap: 1.25em;}:where(.wp-block-post-template.is-layout-grid){gap: 1.25em;}.has-black-color{color: var(--wp--preset--color--black) !important;}.has-cyan-bluish-gray-color{color: var(--wp--preset--color--cyan-bluish-gray) !important;}.has-white-color{color: var(--wp--preset--color--white) !important;}.has-pale-pink-color{color: var(--wp--preset--color--pale-pink) !important;}.has-vivid-red-color{color: var(--wp--preset--color--vivid-red) !important;}.has-luminous-vivid-orange-color{color: var(--wp--preset--color--luminous-vivid-orange) !important;}.has-luminous-vivid-amber-color{color: var(--wp--preset--color--luminous-vivid-amber) !important;}.has-light-green-cyan-color{color: var(--wp--preset--color--light-green-cyan) !important;}.has-vivid-green-cyan-color{color: var(--wp--preset--color--vivid-green-cyan) !important;}.has-pale-cyan-blue-color{color: var(--wp--preset--color--pale-cyan-blue) !important;}.has-vivid-cyan-blue-color{color: var(--wp--preset--color--vivid-cyan-blue) !important;}.has-vivid-purple-color{color: var(--wp--preset--color--vivid-purple) !important;}.has-black-background-color{background-color: var(--wp--preset--color--black) !important;}.has-cyan-bluish-gray-background-color{background-color: var(--wp--preset--color--cyan-bluish-gray) !important;}.has-white-background-color{background-color: var(--wp--preset--color--white) !important;}.has-pale-pink-background-color{background-color: var(--wp--preset--color--pale-pink) !important;}.has-vivid-red-background-color{background-color: var(--wp--preset--color--vivid-red) !important;}.has-luminous-vivid-orange-background-color{background-color: var(--wp--preset--color--luminous-vivid-orange) !important;}.has-luminous-vivid-amber-background-color{background-color: var(--wp--preset--color--luminous-vivid-amber) !important;}.has-light-green-cyan-background-color{background-color: var(--wp--preset--color--light-green-cyan) !important;}.has-vivid-green-cyan-background-color{background-color: var(--wp--preset--color--vivid-green-cyan) !important;}.has-pale-cyan-blue-background-color{background-color: var(--wp--preset--color--pale-cyan-blue) !important;}.has-vivid-cyan-blue-background-color{background-color: var(--wp--preset--color--vivid-cyan-blue) !important;}.has-vivid-purple-background-color{background-color: var(--wp--preset--color--vivid-purple) !important;}.has-black-border-color{border-color: var(--wp--preset--color--black) !important;}.has-cyan-bluish-gray-border-color{border-color: var(--wp--preset--color--cyan-bluish-gray) !important;}.has-white-border-color{border-color: var(--wp--preset--color--white) !important;}.has-pale-pink-border-color{border-color: var(--wp--preset--color--pale-pink) !important;}.has-vivid-red-border-color{border-color: var(--wp--preset--color--vivid-red) !important;}.has-luminous-vivid-orange-border-color{border-color: var(--wp--preset--color--luminous-vivid-orange) !important;}.has-luminous-vivid-amber-border-color{border-color: var(--wp--preset--color--luminous-vivid-amber) !important;}.has-light-green-cyan-border-color{border-color: var(--wp--preset--color--light-green-cyan) !important;}.has-vivid-green-cyan-border-color{border-color: var(--wp--preset--color--vivid-green-cyan) !important;}.has-pale-cyan-blue-border-color{border-color: var(--wp--preset--color--pale-cyan-blue) !important;}.has-vivid-cyan-blue-border-color{border-color: var(--wp--preset--color--vivid-cyan-blue) !important;}.has-vivid-purple-border-color{border-color: var(--wp--preset--color--vivid-purple) !important;}.has-vivid-cyan-blue-to-vivid-purple-gradient-background{background: var(--wp--preset--gradient--vivid-cyan-blue-to-vivid-purple) !important;}.has-light-green-cyan-to-vivid-green-cyan-gradient-background{background: var(--wp--preset--gradient--light-green-cyan-to-vivid-green-cyan) !important;}.has-luminous-vivid-amber-to-luminous-vivid-orange-gradient-background{background: var(--wp--preset--gradient--luminous-vivid-amber-to-luminous-vivid-orange) !important;}.has-luminous-vivid-orange-to-vivid-red-gradient-background{background: var(--wp--preset--gradient--luminous-vivid-orange-to-vivid-red) !important;}.has-very-light-gray-to-cyan-bluish-gray-gradient-background{background: var(--wp--preset--gradient--very-light-gray-to-cyan-bluish-gray) !important;}.has-cool-to-warm-spectrum-gradient-background{background: var(--wp--preset--gradient--cool-to-warm-spectrum) !important;}.has-blush-light-purple-gradient-background{background: var(--wp--preset--gradient--blush-light-purple) !important;}.has-blush-bordeaux-gradient-background{background: var(--wp--preset--gradient--blush-bordeaux) !important;}.has-luminous-dusk-gradient-background{background: var(--wp--preset--gradient--luminous-dusk) !important;}.has-pale-ocean-gradient-background{background: var(--wp--preset--gradient--pale-ocean) !important;}.has-electric-grass-gradient-background{background: var(--wp--preset--gradient--electric-grass) !important;}.has-midnight-gradient-background{background: var(--wp--preset--gradient--midnight) !important;}.has-small-font-size{font-size: var(--wp--preset--font-size--small) !important;}.has-medium-font-size{font-size: var(--wp--preset--font-size--medium) !important;}.has-large-font-size{font-size: var(--wp--preset--font-size--large) !important;}.has-x-large-font-size{font-size: var(--wp--preset--font-size--x-large) !important;} :where(.wp-block-post-template.is-layout-flex){gap: 1.25em;}:where(.wp-block-post-template.is-layout-grid){gap: 1.25em;} :where(.wp-block-columns.is-layout-flex){gap: 2em;}:where(.wp-block-columns.is-layout-grid){gap: 2em;} :root :where(.wp-block-pullquote){font-size: 1.5em;line-height: 1.6;} </style> <link rel='stylesheet' id='twentyfifteen-fonts-css' href='https://blogs.coreboot.org/wp-content/themes/twentyfifteen/assets/fonts/noto-sans-plus-noto-serif-plus-inconsolata.css?ver=20230328' media='all' /> <link rel='stylesheet' id='genericons-css' href='https://blogs.coreboot.org/wp-content/themes/twentyfifteen/genericons/genericons.css?ver=20201026' media='all' /> <link rel='stylesheet' id='twentyfifteen-style-css' href='https://blogs.coreboot.org/wp-content/themes/twentyfifteen-child/style.css?ver=20240716' media='all' /> <link rel='stylesheet' id='twentyfifteen-block-style-css' href='https://blogs.coreboot.org/wp-content/themes/twentyfifteen/css/blocks.css?ver=20240609' media='all' /> <script src="https://blogs.coreboot.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.1" id="jquery-core-js"></script> <script src="https://blogs.coreboot.org/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1" id="jquery-migrate-js"></script> <script id="twentyfifteen-script-js-extra"> var screenReaderText = {"expand":"<span class=\"screen-reader-text\">expand child menu<\/span>","collapse":"<span class=\"screen-reader-text\">collapse child menu<\/span>"}; </script> <script src="https://blogs.coreboot.org/wp-content/themes/twentyfifteen/js/functions.js?ver=20221101" id="twentyfifteen-script-js" defer data-wp-strategy="defer"></script> <link rel="https://api.w.org/" href="https://blogs.coreboot.org/wp-json/" /><link rel="alternate" title="JSON" type="application/json" href="https://blogs.coreboot.org/wp-json/wp/v2/categories/4" /><link rel="EditURI" type="application/rsd+xml" title="RSD" href="https://blogs.coreboot.org/xmlrpc.php?rsd" /> <meta name="generator" content="WordPress 6.7.1" /> <!-- Facebook Open Graph metatags added by WordPress plugin - Network Publisher. Get it at: http://wordpress.org/extend/plugins/network-publisher/ --> <meta property="og:site_name" content="coreboot" /> <meta property="og:title" content="coreboot" /> <meta property="og:url" content="https://blogs.coreboot.org" /> <meta property="og:description" content="News from coreboot world" /> <meta property="og:type" content="website" /> <meta property="og:locale" content="en_us" /> <!-- End Facebook Open Graph metatags--> <!-- Google Plus metatags added by WordPress plugin - Network Publisher. Get it at: http://wordpress.org/extend/plugins/network-publisher/ --> <meta itemprop="name" content="coreboot" /> <meta itemprop="description" content="News from coreboot world" /> <meta itemprop="type" content="Article" /> <!-- End Google Plus metatags--> </head> <body class="archive category category-coreboot category-4 wp-embed-responsive"> <div id="page" class="hfeed site"> <a class="skip-link screen-reader-text" href="#content">Skip to content</a> <div id="sidebar" class="sidebar"> <header id="masthead" class="site-header" role="banner"> <div class="site-branding"> <p class="site-title"><a href="https://blogs.coreboot.org/" rel="home"><img src="https://blogs.coreboot.org/files/2014/10/Coreboot_full_web.png" alt="coreboot" /></a></p> <p class="site-description">News from coreboot world</p> <button class="secondary-toggle">Menu and widgets</button> </div><!-- .site-branding --> </header><!-- .site-header --> <div id="secondary" class="secondary"> <div id="widget-area" class="widget-area" role="complementary"> <aside id="search-3" class="widget widget_search"><form role="search" method="get" class="search-form" action="https://blogs.coreboot.org/"> <label> <span class="screen-reader-text">Search for:</span> <input type="search" class="search-field" placeholder="Search …" value="" name="s" /> </label> <input type="submit" class="search-submit screen-reader-text" value="Search" /> </form></aside> <aside id="recent-posts-3" class="widget widget_recent_entries"> <h2 class="widget-title">Recent Posts</h2><nav aria-label="Recent Posts"> <ul> <li> <a href="https://blogs.coreboot.org/blog/2024/10/29/response-to-blog-post-from-malibal/">Response to blog post from MALIBAL</a> </li> <li> <a href="https://blogs.coreboot.org/blog/2024/09/02/coreboot-24-08-release/">coreboot 24.08 release</a> </li> <li> <a href="https://blogs.coreboot.org/blog/2024/05/23/coreboot-24-05-release/">coreboot 24.05 release</a> </li> <li> <a href="https://blogs.coreboot.org/blog/2024/03/01/coreboot-24-02-and-24-02-1-released/">coreboot 24.02 and 24.02.1 released!</a> </li> <li> <a href="https://blogs.coreboot.org/blog/2023/11/28/coreboot-4-22-4-22-01-have-been-released/">coreboot 4.22 & 4.22.01 have been released</a> </li> </ul> </nav></aside><aside id="linkcat-2" class="widget widget_links"><h2 class="widget-title">Blogroll</h2> <ul class='xoxo blogroll'> <li><a href="https://9esec.io/blog/" title="Security meets usability">9elements Cyber Security</a></li> <li><a href="https://blog.3mdeb.com/tags/coreboot/" title="Recent content in coreboot on Thoughts dereferenced from the scratchpad noise.">coreboot on Thoughts dereferenced from the scratchpad noise.</a></li> <li><a href="http://firmwaresecurity.com/" title="a blog focused on hardware/firmware security news/info for BIOS, UEFI, and Coreboot, on Linux, Android, FreeBSD, Chrome, and other OSes.">FIRMWARESECURITY</a></li> <li><a href="http://biosengineer.blogspot.com/">Harrison Hsieh's BIOS blog</a></li> <li><a href="https://libreboot.org/news" title="News for libreboot.org">News for libreboot.org</a></li> <li><a href="https://blog.osfw.foundation/">Open Source Firmware Foundation</a></li> <li><a href="http://bioshacking.blogspot.com/">The BIOS Blog</a></li> <li><a href="http://uefi.blogspot.com/">UEFI BLOG by Tim Lewis</a></li> <li><a href="http://vzimmer.blogspot.com/">Vincent Zimmer's blog</a></li> </ul> </aside> <aside id="tag_cloud-2" class="widget widget_tag_cloud"><h2 class="widget-title">Tags</h2><nav aria-label="Tags"><div class="tagcloud"><ul class='wp-tag-cloud' role='list'> <li><a href="https://blogs.coreboot.org/blog/tag/amd/" class="tag-cloud-link tag-link-15 tag-link-position-1" style="font-size: 8pt;" aria-label="AMD (1 item)">AMD</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/arm/" class="tag-cloud-link tag-link-4196 tag-link-position-2" style="font-size: 13.167785234899pt;" aria-label="ARM (6 items)">ARM</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/asan/" class="tag-cloud-link tag-link-4223 tag-link-position-3" style="font-size: 11.758389261745pt;" aria-label="ASan (4 items)">ASan</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/bios/" class="tag-cloud-link tag-link-4195 tag-link-position-4" style="font-size: 14.107382550336pt;" aria-label="BIOS (8 items)">BIOS</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/coreboot/" class="tag-cloud-link tag-link-4191 tag-link-position-5" style="font-size: 16.456375838926pt;" aria-label="coreboot (15 items)">coreboot</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/coreboot-release/" class="tag-cloud-link tag-link-4230 tag-link-position-6" style="font-size: 8pt;" aria-label="coreboot release (1 item)">coreboot release</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/ec/" class="tag-cloud-link tag-link-4182 tag-link-position-7" style="font-size: 13.167785234899pt;" aria-label="ec (6 items)">ec</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/filo/" class="tag-cloud-link tag-link-4190 tag-link-position-8" style="font-size: 8pt;" aria-label="FILO (1 item)">FILO</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/flashrom/" class="tag-cloud-link tag-link-4189 tag-link-position-9" style="font-size: 15.986577181208pt;" aria-label="flashrom (13 items)">flashrom</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/git/" class="tag-cloud-link tag-link-128 tag-link-position-10" style="font-size: 9.6912751677852pt;" aria-label="git (2 items)">git</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/gsoc/" class="tag-cloud-link tag-link-4194 tag-link-position-11" style="font-size: 22pt;" aria-label="GSoC (60 items)">GSoC</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/gsoc-2013/" class="tag-cloud-link tag-link-4176 tag-link-position-12" style="font-size: 12.510067114094pt;" aria-label="GSoC 2013 (5 items)">GSoC 2013</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/gsoc2015/" class="tag-cloud-link tag-link-4180 tag-link-position-13" style="font-size: 13.167785234899pt;" aria-label="GSoC2015 (6 items)">GSoC2015</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/gsoc-2015/" class="tag-cloud-link tag-link-4178 tag-link-position-14" style="font-size: 8pt;" aria-label="GSOC 2015 (1 item)">GSOC 2015</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/gsoc-2016/" class="tag-cloud-link tag-link-4198 tag-link-position-15" style="font-size: 15.610738255034pt;" aria-label="GSoC 2016 (12 items)">GSoC 2016</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/gsoc-2019/" class="tag-cloud-link tag-link-4220 tag-link-position-16" style="font-size: 17.771812080537pt;" aria-label="GSoC 2019 (21 items)">GSoC 2019</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/gsoc-2020/" class="tag-cloud-link tag-link-4222 tag-link-position-17" style="font-size: 11.758389261745pt;" aria-label="GSoC 2020 (4 items)">GSoC 2020</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/gsoc-2022/" class="tag-cloud-link tag-link-4232 tag-link-position-18" style="font-size: 8pt;" aria-label="GSoC 2022 (1 item)">GSoC 2022</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/gsoc-update/" class="tag-cloud-link tag-link-4171 tag-link-position-19" style="font-size: 13.167785234899pt;" aria-label="GSoC Update (6 items)">GSoC Update</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/h8s/" class="tag-cloud-link tag-link-4181 tag-link-position-20" style="font-size: 13.167785234899pt;" aria-label="h8s (6 items)">h8s</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/kasan/" class="tag-cloud-link tag-link-4221 tag-link-position-21" style="font-size: 8pt;" aria-label="KASAN (1 item)">KASAN</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/libgfxinit/" class="tag-cloud-link tag-link-4224 tag-link-position-22" style="font-size: 8pt;" aria-label="libgfxinit (1 item)">libgfxinit</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/network-console/" class="tag-cloud-link tag-link-278 tag-link-position-23" style="font-size: 8pt;" aria-label="network console (1 item)">network console</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/openembedded/" class="tag-cloud-link tag-link-4173 tag-link-position-24" style="font-size: 8pt;" aria-label="openembedded (1 item)">openembedded</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/payload/" class="tag-cloud-link tag-link-4175 tag-link-position-25" style="font-size: 8pt;" aria-label="payload (1 item)">payload</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/pmh4/" class="tag-cloud-link tag-link-4184 tag-link-position-26" style="font-size: 8pt;" aria-label="pmh4 (1 item)">pmh4</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/pmh7/" class="tag-cloud-link tag-link-4185 tag-link-position-27" style="font-size: 8pt;" aria-label="pmh7 (1 item)">pmh7</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/rayer-spipgm/" class="tag-cloud-link tag-link-4167 tag-link-position-28" style="font-size: 8pt;" aria-label="RayeR SPIPGM (1 item)">RayeR SPIPGM</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/reproducible/" class="tag-cloud-link tag-link-4183 tag-link-position-29" style="font-size: 8pt;" aria-label="reproducible (1 item)">reproducible</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/risc-v/" class="tag-cloud-link tag-link-4199 tag-link-position-30" style="font-size: 13.637583892617pt;" aria-label="RISC-V (7 items)">RISC-V</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/serialice/" class="tag-cloud-link tag-link-4200 tag-link-position-31" style="font-size: 9.6912751677852pt;" aria-label="SerialICE (2 items)">SerialICE</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/spice/" class="tag-cloud-link tag-link-4174 tag-link-position-32" style="font-size: 8pt;" aria-label="spice (1 item)">spice</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/subversion/" class="tag-cloud-link tag-link-4170 tag-link-position-33" style="font-size: 8pt;" aria-label="subversion (1 item)">subversion</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/svn/" class="tag-cloud-link tag-link-4169 tag-link-position-34" style="font-size: 8pt;" aria-label="svn (1 item)">svn</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/thinker/" class="tag-cloud-link tag-link-4186 tag-link-position-35" style="font-size: 8pt;" aria-label="thinker (1 item)">thinker</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/u-boot/" class="tag-cloud-link tag-link-4172 tag-link-position-36" style="font-size: 8pt;" aria-label="U-boot (1 item)">U-boot</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/uefi/" class="tag-cloud-link tag-link-4188 tag-link-position-37" style="font-size: 9.6912751677852pt;" aria-label="UEFI (2 items)">UEFI</a></li> <li><a href="https://blogs.coreboot.org/blog/tag/usb/" class="tag-cloud-link tag-link-16 tag-link-position-38" style="font-size: 8pt;" aria-label="USB (1 item)">USB</a></li> </ul> </div> </nav></aside> </div><!-- .widget-area --> </div><!-- .secondary --> </div><!-- .sidebar --> <div id="content" class="site-content"> <section id="primary" class="content-area"> <main id="main" class="site-main"> <header class="page-header"> <h1 class="page-title">Category: <span>coreboot</span></h1> </header><!-- .page-header --> <article id="post-12650" class="post-12650 post type-post status-publish format-standard hentry category-coreboot"> <header class="entry-header"> <h2 class="entry-title"><a href="https://blogs.coreboot.org/blog/2024/10/29/response-to-blog-post-from-malibal/" rel="bookmark">Response to blog post from MALIBAL</a></h2> </header><!-- .entry-header --> <div class="entry-content"> <p>Recently there was a blog post by MALIBAL, a disgruntled laptop vendor who attempted to port coreboot to their rebranded white label laptop. The cause of the kerfuffle they describe is that they failed in their own attempt to port coreboot to their laptop, then approached a few of our consultants and community members claiming the code was “80+%” complete and that they just needed help with “debugging.”</p> <p>Each attempt was terminated in the evaluation phase, however, as the consultants and vendor disagreed on the amount of remaining effort and the supplied hardware had problems (flash read/write problems, UART access barely possible) which could not be resolved easily. Additionally, this person’s attitude and communication style was, to put it mildly, very off-putting.</p> <p>We won’t do a point-by-point rebuttal of their screed since others have already done so in various other forums. However, it is important to emphasize that aside from NDAs which are common for new product development, <strong>no contracts or statements of work were signed and no money changed hands</strong>. Any suggestion from this vendor’s blog that a coreboot consultant failed to deliver on work they were hired or paid to do is false and defamatory.</p> <p><a href="https://coreboot.org/consulting.html">Our consultants</a> have a strong track record of delivering for their customers on a variety of platforms including embedded systems, laptops and desktops, networking equipment, and servers. They’re also very friendly and will be happy to help scope out your next product needing simple, fast, and secure firmware.</p> <p>Update: 9elements Cybersecurity has posted their side of the story here: <a href="https://9esec.io/blog/response-to-recent-malibal-blog-post-regarding-9elements/">https://9esec.io/blog/response-to-recent-malibal-blog-post-regarding-9elements/</a></p> </div><!-- .entry-content --> <footer class="entry-footer"> <span class="posted-on"><span class="screen-reader-text">Posted on </span><a href="https://blogs.coreboot.org/blog/2024/10/29/response-to-blog-post-from-malibal/" rel="bookmark"><time class="entry-date published" datetime="2024-10-29T17:30:18+00:00">October 29, 2024</time><time class="updated" datetime="2024-10-30T22:13:26+00:00">October 30, 2024</time></a></span><span class="byline"><span class="author vcard"><span class="screen-reader-text">Author </span><a class="url fn n" href="https://blogs.coreboot.org/blog/author/dhendrix/">dhendrix</a></span></span><span class="cat-links"><span class="screen-reader-text">Categories </span><a href="https://blogs.coreboot.org/blog/category/coreboot/" rel="category tag">coreboot</a></span> </footer><!-- .entry-footer --> </article><!-- #post-12650 --> <article id="post-12226" class="post-12226 post type-post status-publish format-standard hentry category-coreboot"> <header class="entry-header"> <h2 class="entry-title"><a href="https://blogs.coreboot.org/blog/2024/09/02/coreboot-24-08-release/" rel="bookmark">coreboot 24.08 release</a></h2> </header><!-- .entry-header --> <div class="entry-content"> <p>We are pleased to announce the release of coreboot 24.08, another significant milestone in our ongoing commitment to delivering open-source firmware solutions. This release includes over 900 commits, contributed by more than 130 dedicated individuals from our global community. The updates in 24.08 bring various enhancements, optimizations, and new features that further improve the reliability and performance of coreboot across supported platforms.</p> <p>We extend our sincere thanks to the patch authors, reviewers, and everyone involved in the coreboot community for their hard work and dedication. Your contributions continue to advance and refine coreboot with each release. As always, thank you for your support and collaboration in driving the future of open-source firmware.</p> <p>The next coreboot release, 24.11 is planned for mid-November.</p> <p>You can find the release on the coreboot downloads site:<br /><a href="https://coreboot.org/downloads.html">https://coreboot.org/downloads.html</a></p> <h2 class="wp-block-heading" id="significant-or-interesting-changes">Significant or interesting changes</h2> <h3 class="wp-block-heading" id="introduce-region_create-functions">Introduce region_create() functions</h3> <p>We introduce two new functions to create region objects. They allow us to check for integer overflows (<code>region_create_untrusted()</code>) or assert their absence (<code>region_create()</code>).</p> <p>This fixes potential overflows in <code>region_overlap()</code> checks in SMI handlers, where we would wrongfully report MMIO as <em>not</em> overlapping SMRAM.</p> <p>Also, two cases of <code>strtol()</code> in <code>parse_region()</code> (cbfstool), where the results were implicitly converted to <code>size_t</code>, are replaced with the unsigned <code>strtoul()</code>.</p> <p>FIT payload support is left out, as it doesn’t use the region API (only the struct).</p> <p>Ticket: <a href="https://ticket.coreboot.org/issues/522">https://ticket.coreboot.org/issues/522</a><br />Review: <a href="https://review.coreboot.org/79905">https://review.coreboot.org/79905</a></p> <h3 class="wp-block-heading" id="libdevice_tree-add-some-fdt-helper-functions">lib/device_tree: Add some FDT helper functions</h3> <p>This adds some helper functions for FDT (Flattened Device Tree) , since more and more mainboards seem to need FDT nowadays. For example our QEMU boards need it in order to know how much RAM is available. Also all RISC-V boards in our tree need FDT.</p> <p>This also adds some tests in order to test said functions.</p> <p>Review: <a href="https://review.coreboot.org/c/coreboot/+/81081">https://review.coreboot.org/c/coreboot/+/81081</a></p> <h3 class="wp-block-heading" id="device_tree-add-function-to-get-top-of-memory-from-a-fdt-blob">device_tree: Add function to get top of memory from a FDT blob</h3> <p>coreboot needs to figure out top of memory to place CBMEM data. On some non-x86 QEMU virtual machines, this is achieved by probing the RAM space to find where the VM starts discarding data since it’s not backed by actual RAM. This behavior seems to have changed on the QEMU side since then, VMs using the “virt” model have started raising exceptions/errors instead of silently discarding data (likely [1] for example) which has previously broken coreboot on these emulation boards.</p> <p>The qemu-aarch64 and qemu-riscv mainboards are intended for the “virt” models and had this issue, which was mostly fixed by using exception handlers in the RAM detection process [2][3]. But on 32-bit RISC-V we fail to initialize CBMEM if we have 2048 MiB or more of RAM, and on 64-bit RISC-V we had to limit probing to 16383 MiB because it can run into MMIO regions otherwise.</p> <p>The qemu-armv7 mainboard code is intended for the “vexpress-a9” model VM which doesn’t appear to suffer from this issue. Still, the issue can be observed on the ARMv7 “virt” model via a port based on qemu-aarch64.</p> <p>QEMU docs for ARM and RISC-V “virt” models [4][5] recommend reading the device tree blob it provides for device information (incl. RAM size). Implement functions that parse the device tree blob to find described memory regions and calculate the top of memory in order to use it in mainboard code as an alternative to probing RAM space. ARM64 code initializes CBMEM in romstage where malloc isn’t available, so take care to do parsing without unflattening the blob and make the code available in romstage as well.</p> <p>[1] <a href="https://lore.kernel.org/qemu-devel/1504626814-23124-1-git-send-email-peter.maydell@linaro.org/T/#u">https://lore.kernel.org/qemu-devel/1504626814-23124-1-git-send-email-peter.maydell@linaro.org/T/#u</a><br />[2] <a href="https://review.coreboot.org/c/coreboot/+/34774">https://review.coreboot.org/c/coreboot/+/34774</a><br />[3] <a href="https://review.coreboot.org/c/coreboot/+/36486">https://review.coreboot.org/c/coreboot/+/36486</a><br />[4] <a href="https://qemu-project.gitlab.io/qemu/system/arm/virt.html">https://qemu-project.gitlab.io/qemu/system/arm/virt.html</a><br />[5] <a href="https://qemu-project.gitlab.io/qemu/system/riscv/virt.html">https://qemu-project.gitlab.io/qemu/system/riscv/virt.html</a></p> <p>Review: <a href="https://review.coreboot.org/c/coreboot/+/80322">https://review.coreboot.org/c/coreboot/+/80322</a></p> <h3 class="wp-block-heading" id="driverswifi-support-bluetooth-regulator-domain-settings">drivers/wifi: Support Bluetooth Regulator Domain Settings</h3> <p>The ‘Bluetooth Increased Power Mode – SAR Limitation’ feature provides ability to utilize increased device Transmit power capability for Bluetooth applications in coordination with Wi-Fi adhering to product SAR (Specific Absorption Rate) limit when Bluetooth and Wi-Fi run together.</p> <p>This commit introduces a `bluetooth_companion’ field to the generic Wi-Fi drivers chip data. This field can be set in the board design device tree to supply the bluetooth device for which the BRDS function must be created.</p> <p>The implementation follows document 559910 Intel Connectivity Platforms BIOS Guideline revision 8.3 specification.</p> <p>Review: <a href="https://review.coreboot.org/c/coreboot/+/83200">https://review.coreboot.org/c/coreboot/+/83200</a></p> <h3 class="wp-block-heading" id="acpigen_ps2_keybd-support-do-not-disturb--accessibility-keys">acpigen_ps2_keybd: Support Do Not Disturb & Accessibility Keys</h3> <p>These commits add support for a Do Not Disturb key and an Accessibility key.</p> <p>HUTRR94 added support for a new usage titled “System Do Not Disturb” which toggles a system-wide Do Not Disturb setting.</p> <p>HUTRR116 added support for a new usage titled “System Accessibility Binding” which toggles a system-wide bound accessibility UI or command.</p> <p>HUTRR94: <a href="https://www.usb.org/sites/default/files/hutrr94_-_system_do_not_disturb.pdf">https://www.usb.org/sites/default/files/hutrr94_-_system_do_not_disturb.pdf</a><br />HUTRR116: <a href="https://www.usb.org/sites/default/files/hutrr116-systemaccessbilitybinding_2.pdf">https://www.usb.org/sites/default/files/hutrr116-systemaccessbilitybinding_2.pdf</a></p> <p>Review: <a href="https://review.coreboot.org/c/coreboot/+/82997">https://review.coreboot.org/c/coreboot/+/82997</a><br />Review: <a href="https://review.coreboot.org/c/coreboot/+/82996">https://review.coreboot.org/c/coreboot/+/82996</a></p> <h3 class="wp-block-heading" id="superioitecommon-add-common-driver-for-gpio-and-led-configuration">superio/ite/common: Add common driver for GPIO and LED configuration</h3> <p>Add a generic driver to configure GPIOs and LEDs on common ITE SuperIOs. The driver supports most ITE SuperIOs, except Embedded Controllers. The driver allows configuring every GPIO property with pin granularity.</p> <p>Verified against datasheets of all ITE SIOs currently supported by coreboot, except IT8721F (assumed to be the same as IT8720F), IT8623E and IT8629E.</p> <p>Review: <a href="https://review.coreboot.org/c/coreboot/+/83355">https://review.coreboot.org/c/coreboot/+/83355</a></p> <h3 class="wp-block-heading" id="utilcbfstool-fix-linux_trampolinec-generation">util/cbfstool: Fix linux_trampoline.c generation</h3> <p>linux_trampoline.c generation is broken with latest crossgcc-i386 toolchain. Fix the issue to enable the building.</p> <pre class="wp-block-code"><code>../cbfstool/linux_trampoline.S: Assembler messages: ../cbfstool/linux_trampoline.S:100: Error: no instruction mnemonic suffix given and no register operands; can't size instruction <builtin>: recipe for target '../cbfstool/linux_trampoline.o' failed </code></pre> <p>Review: <a href="https://review.coreboot.org/c/coreboot/+/82704">https://review.coreboot.org/c/coreboot/+/82704</a></p> <h3 class="wp-block-heading" id="add-leanefi-payload">Add LeanEFI payload</h3> <p>This adds another external payload to coreboot. The payload has been heavily based on u-boots UEFI implementation.</p> <p>The LeanEFI payload is basically a translator from coreboot to UEFI. It takes the coreboot tables and transforms them into UEFI interfaces. Although it can potentially load any efi application that can handle the minimized interface that LeanEFI provides, it has only been tested with LinuxBoot (v6.3.5) as a payload. It has been optimized to support only those interfaces that Linux requires to start.</p> <p>Among other LeanEFI does not support:</p> <ul class="wp-block-list"> <li>efi capsule update (also efi system resource table)</li> <li>efi variables</li> <li>efi text input protocol (it can only output)</li> <li>most boot services. mostly memory services are left (e.g. alloc/free)</li> <li>all runtime services (although there is still a very small runtime footprint that is planned to be removed in the near future)</li> <li>TCG2/TPM (although that is mostly because of laziness) The README.md currently provides more details on why.</li> </ul> <p>The payload currently only supports arm64 and has only been tested on emulation/simulator targets. The original motivation was to get ACPI on arm64 published to the OS without using EDK2. It is however also possible to supply the LeanEFI with a FDT that is published to the OS. At that point one would however probably use coreboot only instead of this shim layer on top. It would be way nicer to have Linux support something other than UEFI to propagate the ACPI tables, but it requires getting the Linux maintainer/community on board. So for now this shim layer circumvents that.</p> <p>LBBR Test:</p> <ol class="wp-block-list"> <li>dump FDT from QEMU like mentioned in aarch64 coreboot doc</li> <li>compile u-root however you like (aarch64)</li> <li>compile Linux (embed u-root initramfs via Kconfig)</li> <li>copy Linux kernel to payloads/leanefi/Image</li> <li>copy following coreboot defconfig to configs/defconfig:</li> </ol> <pre class="wp-block-code"><code>CONFIG_BOARD_EMULATION_QEMU_AARCH64=y CONFIG_PAYLOAD_NONE=n CONFIG_PAYLOAD_LEANEFI=y CONFIG_LEANEFI_PAYLOAD=y CONFIG_LEANEFI_PAYLOAD_PATH="[path-to-linux]/arch/arm64/boot/Image" CONFIG_LEANEFI_FDT=y CONFIG_LEANEFI_FDT_PATH="[path-to-dumped-DTB]" </code></pre> <ol start="6" class="wp-block-list"> <li>compile coreboot:<br /><code>make defconfig</code><br /><code>make -j$(nproc)</code></li> <li>run qemu like mentioned in coreboot doc (no FIT)</li> <li>say hello to u-root and optionally kexec into the next kernel</li> </ol> <p>Review: <a href="https://review.coreboot.org/c/coreboot/+/78913">https://review.coreboot.org/c/coreboot/+/78913</a></p> <h2 class="wp-block-heading" id="additional-coreboot-changes">Additional coreboot changes</h2> <ul class="wp-block-list"> <li>Dropped ChromeEC as a submodule.</li> <li>Numerous updates to autoport tool, including Haswell support.</li> <li>Upgrade to Wuffs 0.4.0-alpha.8</li> <li>Add x86_64 (64-bit) support to LibPayload</li> <li>Add hda-decoder utility that dumps decoded HDA default configuration registers</li> <li>Add SBMIOS tables for arm64 platforms</li> <li>cpu/x86/lapic: Always have LAPIC enabled</li> <li>arch/arm64: Support calling a trusted monitor</li> <li>drivers/wifi: Support Wi-Fi 7 11be Enablement</li> <li>drivers/wifi: Support Radio Frequency Interference Mitigation</li> </ul> <h2 class="wp-block-heading" id="changes-to-external-resources">Changes to external resources</h2> <h3 class="wp-block-heading" id="toolchain-updates">Toolchain updates</h3> <ul class="wp-block-list"> <li>Upgrade CMake from 3.28.3 to 3.29.3</li> <li>Upgrade nasm from 2.16.01 to 2.16.03</li> <li>Upgrade LLVM from 17.0.6 to 18.1.6</li> <li>Upgrade GCC from 13.2 to 14.1.0</li> </ul> <h3 class="wp-block-heading" id="git-submodule-pointers">Git submodule pointers</h3> <ul class="wp-block-list"> <li>/3rdparty/amd_blobs: Update from commit ae5fc7d277 to 26c572974b (2 commits)</li> <li>/3rdparty/arm-trusted-firmware: Update from commit 48f1bc9f52 to c5b8de86c8 (430 commits)</li> <li>/3rdparty/fsp: Update from commit cc6399e8c7 to 800c85770b (23 commits)</li> <li>/3rdparty/intel-microcode: Update from commit 41af345005 to 5278dfcf98 (2 commits)</li> <li>/3rdparty/libgfxinit: Update from commit a4be8a21b0 to 17cfc92f40 (5 commits)</li> <li>/3rdparty/vboot: Update from commit 09fcd2184f to f1f70f46dc (69 commits)</li> </ul> <h2 class="wp-block-heading" id="platform-updates">Platform Updates</h2> <h3 class="wp-block-heading" id="new-mainboards">New mainboards:</h3> <ul class="wp-block-list"> <li>Acer Q45T-AM</li> <li>AOOSTAR WTR R1</li> <li>ASROCK Fatal1ty Z87 Professional</li> <li>ASROCK Z87E-ITX</li> <li>ASROCK Z87M OC Formula</li> <li>ASROCK Z97E-ITX/ac</li> <li>CWWK CW-ADL-4L-V1.0</li> <li>Dell Inc. Latitude E6430</li> <li>Dell Inc. Latitude E7240</li> <li>Dell Inc. XPS 8300</li> <li>Emulation QEMU sbsa</li> <li>GIGABYTE GA-H61M-S2P-R3</li> <li>Google Awasuki</li> <li>Google Brox TI PDC</li> <li>Google Domika</li> <li>Google Fatcat</li> <li>Google Jubilant</li> <li>Google Orisa</li> <li>Google Rauru</li> <li>Google Rex 64</li> <li>Google Teliks</li> <li>Google Tereid</li> <li>HP EliteBook 8560w</li> <li>Intel Avenue City CRB</li> <li>Intel Beechnut City CRB</li> <li>Protectli VP6630/VP6650/VP6670</li> <li>Star Labs Star Labs Lite Mk V (N200)</li> <li>System76 addw4</li> <li>System76 darp10</li> <li>System76 darp10-b</li> <li>System76 oryp12</li> </ul> <h3 class="wp-block-heading" id="updated-socs--socket-definitions">Updated SoCs & socket definitions</h3> <ul class="wp-block-list"> <li>Added src/cpu/intel/socket_LGA1700</li> <li>Added src/cpu/intel/socket_LGA3647_1</li> <li>Added src/cpu/intel/socket_LGA4189</li> <li>Added src/cpu/intel/socket_LGA4677</li> <li>Added src/soc/intel/pantherlake</li> <li>Added src/soc/mediatek/mt8196</li> </ul> <h2 class="wp-block-heading" id="statistics-from-the-2405-to-the-2408-release">Statistics from the 24.05 to the 24.08 release</h2> <ul class="wp-block-list"> <li>Total Commits: 897</li> <li>Average Commits per day: 8.81</li> <li>Total lines added: 107580</li> <li>Average lines added per commit: 119.93</li> <li>Number of patches adding more than 100 lines: 101</li> <li>Average lines added per small commit: 37.57</li> <li>Total lines removed: 18893</li> <li>Average lines removed per commit: 21.06</li> <li>Total difference between added and removed: 88687</li> <li>Total authors: 136</li> <li>New authors: 33</li> </ul> <h2 class="wp-block-heading" id="significant-known-and-open-issues">Significant Known and Open Issues</h2> <h3 class="wp-block-heading" id="coreboot-wide-or-architecture-wide-issues">coreboot-wide or architecture-wide issues</h3> <ul class="wp-block-list"> <li>519 – make gconfig – could not find glade file</li> <li>518 – make xconfig – g++: fatal error: no input files</li> </ul> <h3 class="wp-block-heading" id="payload-specific-issues">Payload-specific issues</h3> <ul class="wp-block-list"> <li>552 – X201 not booting with edk2 payload</li> <li>549 – SeaBIOS Windows 10/11 BSOD “ACPI BIOS ERROR” (Thinkpad W530)</li> <li>499 – EDK boot fails with RESOURCE_ALLOCATION_TOP_DOWN enabled</li> <li>496 – Missing malloc check in libpayload</li> <li>484 – No USB keyboard support with secondary payloads</li> <li>414 – X9SAE-V: No USB keyboard init on SeaBIOS using Radeon RX 6800XT</li> </ul> <h3 class="wp-block-heading" id="platform-specific-issues">Platform-specific issues</h3> <ul class="wp-block-list"> <li>548 – Lenovo X201 Fails To Recognize Upgraded WiFi Card</li> <li>538 – x230: Dock Causes Internal Display to “Permanently” Malfunction</li> <li>535 – T420: Power light stays off after reboot</li> <li>528 – Building qemu-i440fx with CONFIG_CBFS_VERIFICATION fails</li> <li>524 – X2APIC Options cause Linux to crash on emulation/qemu-i440fx</li> <li>517 – lenovo x230 boot stuck with connected external monitor</li> <li>509 – SD Card hotplug not working on Apollo Lake</li> <li>507 – Windows GPU driver fails on Google guybrush & skyrim boards</li> <li>506 – APL/GML don’t boot OS when CPU microcode included “from tree”</li> <li>505 – Harcuvar CRB – 15 of 16 cores present in the operating system</li> <li>499 – T440p – EDK2 fails with RESOURCE_ALLOCATION_TOP_DOWN enabled</li> <li>495 – Stoney Chromebooks not booting PSPSecureOS</li> <li>478 – X200 booting Linux takes a long time with TSC</li> <li>474 – X200s crashes after graphic init with 8GB RAM</li> <li>457 – Haswell (t440p): CAR mem region conflicts with CBFS_SIZE > 8mb</li> <li>453 – Intel HDMI / DP Audio not present in Windows after libgfxinit</li> <li>449 – ThinkPad T440p fail to start, continuous beeping & LED blinking</li> <li>448 – Thinkpad T440P ACPI Battery Value Issues</li> <li>446 – Optiplex 9010 No Post</li> <li>439 – Lenovo X201 Turbo Boost not working (stuck on 2,4GHz)</li> <li>427 – x200: Two battery charging issues</li> <li>412 – x230 reboots on suspend</li> <li>393 – T500 restarts rather than waking up from suspend</li> <li>350 – I225 PCIe device not detected on Harcuvar</li> </ul> <h2 class="wp-block-heading" id="coreboot-links-and-contact-information">coreboot Links and Contact Information</h2> <ul class="wp-block-list"> <li>Main Web site: <a href="https://www.coreboot.org/">https://www.coreboot.org</a></li> <li>Downloads: <a href="https://coreboot.org/downloads.html">https://coreboot.org/downloads.html</a></li> <li>Source control: <a href="https://review.coreboot.org/">https://review.coreboot.org</a></li> <li>Documentation: <a href="https://doc.coreboot.org/">https://doc.coreboot.org</a></li> <li>Issue tracker: <a href="https://ticket.coreboot.org/projects/coreboot">https://ticket.coreboot.org/projects/coreboot</a></li> <li>Donations: <a href="https://coreboot.org/donate.html">https://coreboot.org/donate.html</a></li> </ul> </div><!-- .entry-content --> <footer class="entry-footer"> <span class="posted-on"><span class="screen-reader-text">Posted on </span><a href="https://blogs.coreboot.org/blog/2024/09/02/coreboot-24-08-release/" rel="bookmark"><time class="entry-date published" datetime="2024-09-02T20:48:33+00:00">September 2, 2024</time><time class="updated" datetime="2024-09-02T20:48:35+00:00">September 2, 2024</time></a></span><span class="byline"><span class="author vcard"><span class="screen-reader-text">Author </span><a class="url fn n" href="https://blogs.coreboot.org/blog/author/martinroth/">Martin Roth</a></span></span><span class="cat-links"><span class="screen-reader-text">Categories </span><a href="https://blogs.coreboot.org/blog/category/coreboot/" rel="category tag">coreboot</a></span> </footer><!-- .entry-footer --> </article><!-- #post-12226 --> <article id="post-10652" class="post-10652 post type-post status-publish format-standard hentry category-coreboot"> <header class="entry-header"> <h2 class="entry-title"><a href="https://blogs.coreboot.org/blog/2024/05/23/coreboot-24-05-release/" rel="bookmark">coreboot 24.05 release</a></h2> </header><!-- .entry-header --> <div class="entry-content"> <p>The coreboot project is pleased to announce the release of coreboot version 24.05. This update represents three months of hard work and commitment from our community. With over 20 new members and contributions from more than a hundred fifty other people in coding, reviewing patches, and other areas, this release showcases the strength of our collaborative efforts.</p> <p>With this release, coreboot has expanded its support, adding 25 new platforms or variants and 2 new processors, further demonstrating our dedication to offering flexible and adaptable firmware solutions. From laptops and servers to embedded devices, coreboot 24.05 is designed to enhance a variety of hardware platforms with its strong features.</p> <p>We are grateful to all the contributors who have made this release possible. Your expertise and collaborative efforts continue to propel the coreboot project forward. We value the participation of everyone in the community, from long-time developers to those new to the project, and encourage you to explore the new opportunities that coreboot 24.05 offers.</p> <p>Our next release will be 24.08, scheduled for mid-August.</p> <p>You can find the release on the coreboot downloads site:<br /><a href="https://coreboot.org/downloads.html">https://coreboot.org/downloads.html</a></p> <h2 class="wp-block-heading" id="significant-or-interesting-changes">Significant or interesting changes</h2> <h3 class="wp-block-heading" id="mark-64-bit-support-as-stable">Mark 64-bit support as stable</h3> <p>A significant amount of work has gone into fully supporting 64-bit coreboot builds. There are still additional pieces that are happening, but with SMM holding page tables itself, we can consider SMM support stable and safe enough for general use.</p> <h3 class="wp-block-heading" id="securitytpm-support-compiling-in-multiple-tpm-drivers">security/tpm: support compiling in multiple TPM drivers</h3> <p>Previously, boards could only be built with code supporting TPM 1.x or TPM 2.x specifications. This has been updated with code allowing both to be built in simultaneously, allowing the system to query the TPM. For systems with soldered-down TPMs or firmware TPM solutions, it’s still possible to specify a single TPM version so that the code for the other version isn’t included.</p> <p>// Add entries for future releases here.<br />const releaseList = [<br />{ version: ‘24.05’, date: ’14. May 2024′ },<br />{ version: ‘24.02.01’, date: ’29. February 2024′ },<br />{ version: ‘4.22.01’,date: ’24. November 2023′ },</p> <p>Previously, boards could only be built with code supporting TPM 1.x or TPM 2.x specifications. This has been updated with code allowing both to be built in simultaneously, allowing the system to query the TPM. For systems with soldered-down TPMs or firmware TPM solutions, it’s still possible to specify a single TPM version so that the code for the other version isn’t included.</p> <h3 class="wp-block-heading" id="archarm64-add-el1el2el3-support-for-arm64">arch/arm64: Add EL1/EL2/EL3 support for arm64</h3> <p>Previously, arch/arm64 required coreboot to run on EL3 due to EL3 register access. This might be an issue when, for example, one boots into TF-A first and drops into EL2 for coreboot afterwards.</p> <p>This patch aims at making arch/arm64 more versatile by removing the current EL3 constraint and allowing arm64 coreboot to run on EL1, EL2 and EL3.</p> <p>The strategy is to add a Kconfig option (ARM64_CURRENT_EL) which allows us to specify coreboot’s EL upon entry. Based on that, we access the appropriate ELx registers. So, for example, when running coreboot on EL1, we would not access vbar_el3 or vbar_el2 but instead vbar_el1. This way, we don’t generate faults when accessing higher-EL registers.</p> <h2 class="wp-block-heading" id="additional-coreboot-changes">Additional coreboot changes</h2> <ul class="wp-block-list"> <li>util/smmstoretool: support processing ROMs</li> <li>cpu/x86: Link page tables in stage if possible</li> <li>lib/lzmadecode: Allow for 8 byte reads on 64bit to speed up decompression</li> <li>mb/lenovo/*: Set VR12 PSI to fix crash</li> <li>Numerous fixes for clang support</li> <li>Ongoing code cleanup</li> <li>Docs: Replace Recommonmark with MyST Parser. For changes, see the commit message in <a href="https://review.coreboot.org/73158">https://review.coreboot.org/73158</a></li> </ul> <h2 class="wp-block-heading" id="changes-to-external-resources">Changes to external resources</h2> <h3 class="wp-block-heading" id="toolchain-updates">Toolchain updates</h3> <ul class="wp-block-list"> <li>util/kconfig: Uprev to Linux 6.8’s kconfig</li> <li>crossgcc: Upgrade CMake from 3.27.7 to version 3.28.3</li> <li>util/crossgcc: Update LLVM from 16.0.6 to 17.0.6</li> <li>crossgcc: Upgrade binutils from 2.41 to 2.42</li> <li>util/crossgcc/buildgcc: Use Intel mirror for ACPICA</li> </ul> <h3 class="wp-block-heading" id="git-submodule-pointers">Git submodule pointers</h3> <ul class="wp-block-list"> <li>amd_blobs: Update from commit id 64cdd7c8ef to ae5fc7d277 (1 commits)</li> <li>arm-trusted-firmware: Update from commit id 17bef2248d to 48f1bc9f52 (517 commits)</li> <li>cmocka: Update from commit id 8931845c35 to 8be3737209 (32 commits)</li> <li>fsp: Update from commit id 507ef01cce to cc6399e8c7 (14 commits)</li> <li>intel-microcode: Update from commit id ece0d294a2 to 41af345005 (1 commit)</li> <li>vboot: Update from commit id 3d37d2aafe to 09fcd2184f (27 commits)</li> </ul> <h4 class="wp-block-heading" id="external-payloads">External payloads</h4> <ul class="wp-block-list"> <li>payloads/U-Boot: Upgrade from U-Boot v2023.07 to v2024.4</li> <li>payloads/edk2: Add Kconfig options for LAPIC timer & UFS support</li> <li>payloads/Kconfig: Add flat binary as payload option</li> </ul> <h2 class="wp-block-heading" id="platform-updates">Platform Updates</h2> <h3 class="wp-block-heading" id="added-mainboards">Added mainboards:</h3> <ul class="wp-block-list"> <li>AMD BirmanPlus for Glinda SoC</li> <li>AMD BirmanPlus for Phoenix SoC</li> <li>ASROCK Z97 Extreme6</li> <li>Dell OptiPlex 7020/9020 MT</li> <li>Dell OptiPlex 7020/9020 SFF</li> <li>Framework Azalea (Framework 13 AMD 7040)</li> <li>Google Brox EC ISH</li> <li>Google Bujia</li> <li>Google Glassway</li> <li>Google Greenbayupoc</li> <li>Google Kyogre</li> <li>Google Lotso</li> <li>Google Nova</li> <li>Google Pujjoga</li> <li>Google Riven</li> <li>Google Skitty</li> <li>Google Squirtle</li> <li>Google Sundance</li> <li>Google Tivviks</li> <li>Google Trulo</li> <li>Google Veluza</li> <li>Google Wugtrio</li> <li>Google Yavista</li> <li>HP Pro 3500 Series</li> <li>Lenovo ThinkCentre M700 / M900 Tiny</li> <li>Lenovo ThinkCentre M710s</li> <li>Raptor Computing Systems Talos II</li> <li>SiFive HiFive Unmatched</li> </ul> <h3 class="wp-block-heading" id="removed-mainboards">Removed Mainboards</h3> <ul class="wp-block-list"> <li>Intel Alderlake-M RVP</li> <li>Intel Alderlake-M RVP with Chrome EC</li> </ul> <h3 class="wp-block-heading" id="updated-socs">Updated SoCs</h3> <ul class="wp-block-list"> <li>Added src/soc/ibm/power9</li> <li>Added src/soc/sifive/fu740</li> </ul> <h2 class="wp-block-heading" id="statistics-from-the-2402-to-the-2405-release">Statistics from the 24.02 to the 24.05 release</h2> <ul class="wp-block-list"> <li>Total Commits: 722</li> <li>Average Commits per day: 8.55</li> <li>Total lines added: 302523</li> <li>Average lines added per commit: 419.01</li> <li>Number of patches adding more than 100 lines: 57</li> <li>Average lines added per small commit: 37.80</li> <li>Total lines removed: 16089</li> <li>Average lines removed per commit: 22.28</li> <li>Total difference between added and removed: 286434</li> <li>Total authors: 131</li> <li>New authors: 23</li> </ul> <h2 class="wp-block-heading" id="significant-known-and-open-issues">Significant Known and Open Issues</h2> <h2 class="wp-block-heading" id="coreboot-wide-or-architecture-wide-issues">coreboot-wide or architecture-wide issues</h2> <ul class="wp-block-list"> <li>522 – ‘region_overlap()’ issues due to an integer overflow.</li> <li>519 – make gconfig – could not find glade file </li> <li>518 – make xconfig – g++: fatal error: no input files </li> </ul> <h2 class="wp-block-heading" id="payload-specific-issues">Payload-specific issues</h2> <ul class="wp-block-list"> <li>499 – edk2 boot fails with RESOURCE_ALLOCATION_TOP_DOWN enabled</li> <li>496 – Missing malloc check in libpayload</li> <li>484 – No USB keyboard support with secondary payloads</li> <li>414 – X9SAE-V: No USB keyboard init on SeaBIOS using Radeon RX 6800XT</li> </ul> <h2 class="wp-block-heading" id="platform-specific-issues">Platform-specific issues</h2> <ul class="wp-block-list"> <li>524 – X2APIC Options cause Linux to crash on emulation/qemu-i440fx</li> <li>517 – lenovo x230 boot stuck with connected external monitor</li> <li>509 – SD Card hotplug not working on Apollo Lake</li> <li>507 – Windows GPU driver fails on Google guybrush & skyrim boards</li> <li>506 – APL/GML don’t boot OS when CPU microcode included “from tree”</li> <li>505 – Harcuvar CRB – 15 of 16 cores present in the operating system</li> <li>499 – T440p – EDK2 fails with RESOURCE_ALLOCATION_TOP_DOWN enabled</li> <li>495 – Stoney Chromebooks not booting PSPSecureOS</li> <li>478 – X200 booting Linux takes a long time with TSC</li> <li>474 – X200s crashes after graphic init with 8GB RAM</li> <li>457 – Haswell (t440p): CAR mem region conflicts with CBFS_SIZE > 8mb</li> <li>453 – Intel HDMI / DP Audio not present in Windows after libgfxinit</li> <li>449 – ThinkPad T440p fail to start, continuous beeping & LED blinking</li> <li>448 – Thinkpad T440P ACPI Battery Value Issues</li> <li>446 – Optiplex 9010 No Post</li> <li>439 – Lenovo X201 Turbo Boost not working (stuck on 2,4GHz)</li> <li>427 – x200: Two battery charging issues</li> <li>412 – x230 reboots on suspend</li> <li>393 – T500 restarts rather than waking up from suspend</li> <li>350 – I225 PCIe device not detected on Harcuvar</li> </ul> <h2 class="wp-block-heading" id="coreboot-links-and-contact-information">coreboot Links and Contact Information</h2> <ul class="wp-block-list"> <li>Main Website: <a href="https://www.coreboot.org/">https://www.coreboot.org</a></li> <li>Downloads: <a href="https://coreboot.org/downloads.html">https://coreboot.org/downloads.html</a></li> <li>Source control: <a href="https://review.coreboot.org/">https://review.coreboot.org</a></li> <li>Documentation: <a href="https://doc.coreboot.org/">https://doc.coreboot.org</a></li> <li>Issue tracker: <a href="https://ticket.coreboot.org/projects/coreboot">https://ticket.coreboot.org/projects/coreboot</a></li> <li>Donations: <a href="https://coreboot.org/donate.html">https://coreboot.org/donate.html</a></li> </ul> </div><!-- .entry-content --> <footer class="entry-footer"> <span class="posted-on"><span class="screen-reader-text">Posted on </span><a href="https://blogs.coreboot.org/blog/2024/05/23/coreboot-24-05-release/" rel="bookmark"><time class="entry-date published" datetime="2024-05-23T15:41:36+00:00">May 23, 2024</time><time class="updated" datetime="2024-05-23T15:41:38+00:00">May 23, 2024</time></a></span><span class="byline"><span class="author vcard"><span class="screen-reader-text">Author </span><a class="url fn n" href="https://blogs.coreboot.org/blog/author/martinroth/">Martin Roth</a></span></span><span class="cat-links"><span class="screen-reader-text">Categories </span><a href="https://blogs.coreboot.org/blog/category/coreboot/" rel="category tag">coreboot</a></span> </footer><!-- .entry-footer --> </article><!-- #post-10652 --> <article id="post-8945" class="post-8945 post type-post status-publish format-standard hentry category-coreboot"> <header class="entry-header"> <h2 class="entry-title"><a href="https://blogs.coreboot.org/blog/2024/03/01/coreboot-24-02-and-24-02-1-released/" rel="bookmark">coreboot 24.02 and 24.02.1 released!</a></h2> </header><!-- .entry-header --> <div class="entry-content"> <p>The coreboot project is happy to announce our release for February 2024. Over the past three months, our contributors have focused on refining the coreboot codebase, generally prioritizing cleanup and quality enhancements. We extend our gratitude to all the contributors who have dedicated their time and expertise. Thank you for your invaluable contributions to this vital phase of maintenance and optimization.</p> <p>The next release is scheduled for mid-May.</p> <p><strong>Release number format update</strong></p> <p>The previous release was the last to use the incrementing 4.xx release name scheme. For this and future releases, coreboot has switched to a Year.Month.Sub-version naming scheme. As such, the next release, scheduled for May of 2024 will be numbered 24.05, with the sub-version of 00 implied. If we need to do a fix or incremental release, we’ll append the values .01, .02 and so on to the initial release value.</p> <p><strong>The master branch is being deleted</strong></p> <p>The coreboot project changed from master to main roughly 6 months ago, and has been keeping the two branches in sync since then to ease the transition. As of this release, we are getting rid of the master branch completely. Please make sure any scripts you’re using that reference the ‘master’ branch have been switched to ‘main’.</p> <h2 class="wp-block-heading">Release 24.02.1</h2> <p><strong>lib/rtc: Fix off-by-one error in February day count in leap year</strong></p> <p>The month argument passed to rtc\_month\_days is 0-based, not 1-based. This results in the RTC being reverted to the build date constantly on 29th February 2024. </p> <h2 class="wp-block-heading">Significant or interesting changes</h2> <p><strong>acpi: Add Arm IO Remapping Table structures</strong></p> <p>Input Output Remapping Table (IORT) represents the IO topology of an Arm based system.</p> <p>Document number: ARM DEN 0049E.e, Sep 2022</p> <p><strong>acpi: Add PPTT support</strong></p> <p>This patch adds code to generate Processor Properties Topology Tables (PPTT) compliant to the ACPI 6.4 specification.</p> <ul class="wp-block-list"> <li>The ‘acpi_get_pptt_topology’ hook is mandatory once ACPI_PPTT is selected. Its purpose is to return a pointer to a topology tree, which describes the relationship between CPUs and caches. The hook can be provided by, for example, mainboard code.</li> </ul> <p>Background: We are currently working on mainboard code for qemu-sbsa and Neoverse N2. Both require a valid PPTT table. Patch was tested against the qemu-sbsa board.</p> <p><strong>acpi: Add support for WDAT table</strong></p> <p>This commit lays the groundwork for implementing the ACPI WDAT (Watchdog Action Table) table specification. The WDAT is a special ACPI table introduced by Microsoft that describes the watchdog for the OS.</p> <p>Platforms that need to implement the WDAT table must describe the hardware watchdog management operations as described in the specification. See “Links to ACPI-Related Documents” (http://uefi.org/acpi) under the heading “Watchdog Action Table”.</p> <p><strong>lib/jpeg: Replace decoder with Wuffs’ implementation</strong></p> <p>To quote its repo[0]: Wuffs is a memory-safe programming language (and a standard library written in that language) for Wrangling Untrusted File Formats Safely. Wrangling includes parsing, decoding and encoding.</p> <p>It compiles its library, written in its own language, to a C/C++ source file that can then be used independently without needing support for the language. That library is now imported to src/vendorcode/wuffs/.</p> <p>This change modifies our linters to ignore that directory because it’s supposed to contain the wuffs compiler’s result verbatim.</p> <p>Nigel Tao provided an initial wrapper around wuffs’ jpeg decoder that implements our JPEG API. I further changed it a bit regarding data placement, dropped stuff from our API that wasn’t ever used, or isn’t used anymore, and generally made it fit coreboot a bit better. Features are Nigel’s, bugs are mine.</p> <p>This commit also adapts our jpeg fuzz test to work with the modified API. After limiting it to deal only with approximately screen sized inputs, it fuzzed for 25 hours CPU time without a single hang or crash. This is a notable improvement over running the test with our old decoder which crashes within a minute.</p> <p>Finally, I tried the new parser with a pretty-much-random JPEG file I got from the internet, and it just showed it (once the resolution matched), which is also a notable improvement over the old decoder which is very particular about the subset of JPEG it supports.</p> <p>In terms of code size, a QEmu build’s ramstage increases from 128060 bytes decompressed (64121 bytes after LZMA) to 172304 bytes decompressed (82734 bytes after LZMA).</p> <p>[0] https://github.com/google/wuffs</p> <h2 class="wp-block-heading">Additional coreboot changes</h2> <ul class="wp-block-list"> <li>Rename Makefiles from .inc to .mk to better identify them</li> <li>SPI: Add GD25LQ255E and IS25WP256D chip support</li> <li>device: Add support for multiple PCI segment groups</li> <li>device: Drop unused multiple downstream link support</li> <li>device: Rename bus and link_list to upstream and downstream</li> <li>Updated devicetree files for modern Intel platforms to use chipset.cb</li> <li>Updated xeon-sp to use the coreboot allocator</li> </ul> <h2 class="wp-block-heading">Changes to external resources</h2> <p><strong>Toolchain updates</strong></p> <ul class="wp-block-list"> <li>Add buildgcc support for Apple M1/M2 devices</li> <li>Upgrade GCC from 11.4.0 to 13.2.0</li> <li>Update CMake from 3.26.4 to 3.27.7</li> <li>Uprev to Kconfig from Linux 6.7</li> </ul> <p><strong>Git submodule pointers</strong></p> <ul class="wp-block-list"> <li>3rdparty/amd_blobs: Update from commit id e4519efca7 to 64cdd7c8ef (5 commits)</li> <li>3rdparty/arm-trusted-firmware: Update from commit id 88b2d81345 to 17bef2248d (701 commits)</li> <li>3rdparty/fsp: Update from commit id 481ea7cf0b to 507ef01cce (16 commits)</li> <li>3rdparty/intel-microcode: Update from commit id 6788bb07eb to ece0d294a2 (1 commit)</li> <li>3rdparty/vboot: Update from commit id 24cb127a5e to 3d37d2aafe (121 commits)</li> </ul> <p><strong>External payloads</strong></p> <ul class="wp-block-list"> <li>payload/grub2: Update from 2.06 to 2.12</li> <li>payload/seabios: Update from 1.16.2 to 1.16.3</li> </ul> <h2 class="wp-block-heading">Platform Updates</h2> <p><strong>Added mainboards</strong></p> <ul class="wp-block-list"> <li>Google: Dita</li> <li>Google: Xol</li> <li>Lenovo: ThinkPad X230 eDP Mod (2K/FHD)</li> </ul> <p><strong>Removed mainboards</strong></p> <ul class="wp-block-list"> <li>Google -> Primus4ES</li> </ul> <h2 class="wp-block-heading">Statistics from the 4.22 to the 24.02 release</h2> <ul class="wp-block-list"> <li>Total Commits: 815</li> <li>Average Commits per day: 8.63</li> <li>Total lines added: 105433</li> <li>Average lines added per commit: 129.37</li> <li>Number of patches adding more than 100 lines: 47</li> <li>Average lines added per small commit: 41.34</li> <li>Total lines removed: 16534</li> <li>Average lines removed per commit: 20.29</li> <li>Total difference between added and removed: 88899</li> <li>Total authors: 111</li> <li>New authors: 19</li> </ul> <h2 class="wp-block-heading">Significant Known and Open Issues</h2> <ul class="wp-block-list"> <li>AMD chromebooks will not work with the signed PSP_verstage images and the version of verstage used in coreboot 24.02.</li> </ul> <h2 class="wp-block-heading"><strong>Issues from the coreboot bugtracker: ticket.coreboot.org</strong></h2> <h3 class="wp-block-heading"><strong>coreboot-wide or architecture-wide issues</strong></h3> <figure class="wp-block-table"><table><tbody><tr><td>#</td><td>Subject</td></tr><tr><td>522</td><td> ‘region_overlap()’ issues due to an integer overflow.</td></tr><tr><td>519</td><td>make gconfig – could not find glade file</td></tr><tr><td>518</td><td>make xconfig – g++: fatal error: no input files</td></tr></tbody></table></figure> <h3 class="wp-block-heading"><strong>Payload-specific issues</strong></h3> <figure class="wp-block-table"><table><tbody><tr><td>#</td><td>Subject</td></tr><tr><td>499</td><td>edk2 boot fails with RESOURCE_ALLOCATION_TOP_DOWN enabled</td></tr><tr><td>496</td><td>Missing malloc check in libpayload</td></tr><tr><td>484</td><td>No USB keyboard support with secondary payloads</td></tr><tr><td>414</td><td>X9SAE-V: No USB keyboard init on SeaBIOS using Radeon RX 6800XT</td></tr></tbody></table></figure> <h3 class="wp-block-heading"><strong>Platform-specific issues</strong></h3> <figure class="wp-block-table"><table><tbody><tr><td>#</td><td>Subject</td></tr><tr><td>517</td><td>lenovo x230 boot stuck with connected external monitor</td></tr><tr><td>509</td><td>SD Card hotplug not working on Apollo Lake</td></tr><tr><td>507</td><td>Windows GPU driver fails on Google guybrush & skyrim boards</td></tr><tr><td>506</td><td>APL/GML don’t boot OS when CPU microcode included “from tree”</td></tr><tr><td>505</td><td>Harcuvar CRB – 15 of 16 cores present in the operating system</td></tr><tr><td>499</td><td>T440p – EDK2 fails with RESOURCE_ALLOCATION_TOP_DOWN enabled</td></tr><tr><td>495</td><td>Stoney Chromebooks not booting PSPSecureOS</td></tr><tr><td>478</td><td>X200 booting Linux takes a long time with TSC</td></tr><tr><td>474</td><td>X200s crashes after graphic init with 8GB RAM</td></tr><tr><td>457</td><td>Haswell (t440p): CAR mem region conflicts with CBFS_SIZE > 8mb</td></tr><tr><td>453</td><td>Intel HDMI / DP Audio not present in Windows after libgfxinit</td></tr><tr><td>449</td><td>ThinkPad T440p fail to start, continuous beeping & LED blinking</td></tr><tr><td>448</td><td>Thinkpad T440P ACPI Battery Value Issues</td></tr><tr><td>446</td><td>Optiplex 9010 No Post</td></tr><tr><td>439</td><td>Lenovo X201 Turbo Boost not working (stuck on 2,4GHz)</td></tr><tr><td>427</td><td>x200: Two battery charging issues</td></tr><tr><td>412</td><td>x230 reboots on suspend</td></tr><tr><td>393</td><td>T500 restarts rather than waking up from suspend</td></tr><tr><td>350</td><td>I225 PCIe device not detected on Harcuvar</td></tr></tbody></table></figure> <h2 class="wp-block-heading">coreboot Links and Contact Information</h2> <ul class="wp-block-list"> <li>Main Web site: <a href="https://www.coreboot.org">https://www.coreboot.org</a></li> <li>Downloads: <a href="https://coreboot.org/downloads.html">https://coreboot.org/downloads.html</a></li> <li>Source control: <a href="https://review.coreboot.org">https://review.coreboot.org</a></li> <li>Documentation: <a href="https://doc.coreboot.org">https://doc.coreboot.org</a></li> <li>Issue tracker: <a href="https://ticket.coreboot.org/projects/coreboot">https://ticket.coreboot.org/projects/coreboot</a></li> <li>Donations: <a href="https://coreboot.org/donate.html">https://coreboot.org/donate.html</a></li> </ul> </div><!-- .entry-content --> <footer class="entry-footer"> <span class="posted-on"><span class="screen-reader-text">Posted on </span><a href="https://blogs.coreboot.org/blog/2024/03/01/coreboot-24-02-and-24-02-1-released/" rel="bookmark"><time class="entry-date published" datetime="2024-03-01T12:13:37+00:00">March 1, 2024</time><time class="updated" datetime="2024-03-01T12:13:39+00:00">March 1, 2024</time></a></span><span class="byline"><span class="author vcard"><span class="screen-reader-text">Author </span><a class="url fn n" href="https://blogs.coreboot.org/blog/author/felixsinger/">Felix Singer</a></span></span><span class="cat-links"><span class="screen-reader-text">Categories </span><a href="https://blogs.coreboot.org/blog/category/coreboot/" rel="category tag">coreboot</a></span> </footer><!-- .entry-footer --> </article><!-- #post-8945 --> <article id="post-8534" class="post-8534 post type-post status-publish format-standard hentry category-coreboot"> <header class="entry-header"> <h2 class="entry-title"><a href="https://blogs.coreboot.org/blog/2023/11/28/coreboot-4-22-4-22-01-have-been-released/" rel="bookmark">coreboot 4.22 & 4.22.01 have been released</a></h2> </header><!-- .entry-header --> <div class="entry-content"> <p>The next release is planned for the 19th of February, 2024</p> <p>These notes cover the latest updates and improvements to coreboot over the past three months. A big thank you to the returning contributors as well as the 14 individuals who committed code for the first time. We greatly appreciate everyone’s dedication and expertise. As with past releases, this one reflects a commitment to open source innovation, security enhancements, and expanding hardware support.</p> <h3 class="wp-block-heading">4.22.01 release</h3> <p>The week between tagging a release and announcing it publicly is used to test the tagged version and make sure everything is working as we expect. This is done instead of freezing the tree and doing release candidates before the release.</p> <p>For the 4.22 release cycle we found an uninitialized variable error on the sandybridge/ivybridge platforms and rolled that into the 4.22.01 release package.</p> <h3 class="wp-block-heading">coreboot version naming update</h3> <p>This release is the last release to use the incrementing 4.xx release name scheme. For future releases, coreboot is switching to a Year.Month.Sub-version naming scheme. As such, the next release, scheduled for February of 2024 will be numbered 24.02, with the sub-version of 00 implied. If we need to do a fix or future release of the 24.02 release, we’ll append the values .01, .02 and so on to the initial release value.</p> <h3 class="wp-block-heading">coreboot default branch update</h3> <p>Immediately after the 4.21 release, the coreboot project changed the default git branch from ‘master’ to ‘main’. For the first couple of months after the change, The master branch was synced with the main branch several times a day, allowing people time to update any scripts. As of 2023-11-01, the sync rate has slowed to once a week. This will continue until the next release, at which time the master branch will be removed.</p> <h2 class="wp-block-heading">Significant or interesting changes</h2> <h3 class="wp-block-heading">x86: support .data section for pre-memory stages</h3> <p>x86 pre-memory stages did not support the <code>.data</code> section and as a result developers were required to include runtime initialization code instead of relying on C global variable definitions.</p> <p>Other platforms do not have that limitation. Hence, resolving it helps to align code and reduce compilation-based restrictions (cf. the use of <code>ENV_HAS_DATA_SECTION</code> compilation flag in various places of coreboot code).</p> <p>There were three types of binary to consider:</p> <ol class="wp-block-list"> <li>eXecute-In-Place pre-memory stages</li> <li><code>bootblock</code> stage is a bit different as it uses Cache-As-Ram but the memory mapping and its entry code different</li> <li>pre-memory stages loaded in and executed from Cache-As-RAM (cf. <code>CONFIG_NO_XIP_EARLY_STAGES</code>).</li> </ol> <p>eXecute-In-Place pre-memory stages (#1) rely on a new ELF segment as the code segment Virtual Memory Address and Load Memory Address are identical but the data needs to be linked in cache-As-RAM (VMA) to be stored right after the code (LMA).</p> <p><code>bootblock</code> (#2) also uses this new segment to store the data right after the code and it loads it to Cache-As-RAM at runtime. However, the code involved is different.</p> <p>Not eXecute-In-Place pre-memory stages (#3) did not need any special work other than enabling a .data section as the code and data VMA / LMA translation vector is the same.</p> <p>Related important commits:</p> <ul class="wp-block-list"> <li>c9cae530e5 (“cbfstool: Make add-stage support multiple ignore sections”)</li> <li>79f2e1fc8b (“cbfstool: Make add-stage support multiple loadable segments”)</li> <li>b7832de026 (“x86: Add .data section support for pre-memory stages”)</li> </ul> <h3 class="wp-block-heading">x86: Support CBFS cache for pre-memory stages and ramstage</h3> <p>The CBFS cache scratchpad offers a generic way to decompress CBFS files through the cbfs_map() function without having to reserve a per-file specific memory region.</p> <p>CBFS cache x86 support has been added to pre-memory stages and ramstage.</p> <ol class="wp-block-list"> <li><strong>pre-memory stages</strong>: The new <code>PRERAM_CBFS_CACHE_SIZE</code> Kconfig can be used to set the pre-memory stages CBFS cache size. A cache size of zero disables the CBFS cache feature for all pre-memory stages. The default value is 16 KiB which seems a reasonable minimal value enough to satisfy basic needs such as the decompression of a small configuration file. This setting can be adjusted depending on the platform’s needs and capabilities. Note that we have set this size to zero for all the platforms without enough space in Cache-As-RAM to accommodate the default size.</li> <li><strong>ramstage</strong>: The new <code>RAMSTAGE_CBFS_CACHE_SIZE</code> Kconfig can be used to set the ramstage CBFS cache size. A cache size of zero disables the CBFS cache feature for ramstage. Similarly to pre-memory stages support, the default size is 16 KiB. As we want to support the S3 suspend/resume use case, the CBFS cache memory cannot be released to the operating system and therefore cannot be an unreserved memory region. The ramstage CBFS cache scratchpad is defined as a simple C static buffer as it allows us to keep the simple and robust design of the static initialization of the <code>cbfs_cache</code> global variable (cf. src/lib/cbfs.c). However, since some AMD SoCs (cf. <code>SOC_AMD_COMMON_BLOCK_NONCAR</code> Kconfig) already define a <code>_cbfs_cache</code> region we also introduced a <code>POSTRAM_CBFS_CACHE_IN_BSS</code> Kconfig to gate the use of a static buffer as the CBFS cache scratchpad.</li> </ol> <h3 class="wp-block-heading">Allow romstage to be combined into the bootblock</h3> <p>Having a separate romstage is only desirable:</p> <ul class="wp-block-list"> <li>with advanced setups like vboot or normal/fallback</li> <li>boot medium is slow at startup (some ARM SOCs)</li> <li>bootblock is limited in size (Intel APL 32K)</li> </ul> <p>When this is not the case there is no need for the extra complexity that romstage brings. Including the romstage sources inside the bootblock substantially reduces the total code footprint. Often the resulting code is 10-20k smaller.</p> <p>This is controlled via a Kconfig option.</p> <h3 class="wp-block-heading">soc/intel/cmn/gfx: Add API to report presence of external display</h3> <p>This implements an API to report the presence of an external display on Intel silicon. The API uses information from the transcoder and framebuffer to determine if an external display is connected.</p> <p>For example, if the transcoder is attached to any DDI ports other than DDI-A (eDP), and the framebuffer is initialized, then it is likely that an external display is present.</p> <p>This information can be used by payloads to determine whether or not to power on the display, even if eDP is not initialized.</p> <h3 class="wp-block-heading">device/pci_rom: Set VBIOS checksum when filling VFCT table</h3> <p>AMD’s Windows display drivers validate the checksum of the VBIOS data in the VFCT table (which gets modified by the FSP GOP driver), so ensure it is set correctly after copying the VBIOS into the table if the FSP GOP driver was run. Without the correct checksum, the Windows GPU drivers will fail to load with a code 43 error in Device Manager.</p> <h2 class="wp-block-heading">Additional coreboot changes</h2> <ul class="wp-block-list"> <li>Move all ‘select’ statements from Kconfig.name files to Kconfig</li> <li>acpigen now generates variable-length PkgLength fields instead of a fixed 3-byte size to improve compatibility and to bring it in line with IASL</li> <li>Work to allow Windows to run on more Chromebooks</li> <li>General cleanup and reformatting</li> <li>Add initial AMD openSIL implementation</li> <li>Add ACPI table generation for ARM64</li> <li>Stop resetting CMOS during s3 resume even if marked as invalid</li> <li>Comply with ACPI specification by making _STR Unicode strings</li> <li>Fix SMM get_save_state calculation, which was broken when STM was enabled</li> <li>SNB+MRC boards: Migrate MRC settings to devicetree</li> <li>Work on chipset devicetrees for all platforms</li> </ul> <h2 class="wp-block-heading">Changes to external resources</h2> <h3 class="wp-block-heading">Toolchain updates</h3> <ul class="wp-block-list"> <li>Upgrade GMP from 6.2.1 to 6.3.0</li> <li>Upgrade binutils from 2.40 to 2.41</li> <li>Upgrade MPFR from 4.2.0 to 4.2.1</li> </ul> <h3 class="wp-block-heading">Git submodule pointers</h3> <ul class="wp-block-list"> <li>amd_blobs: Update from commit id 6a1e1457af to e4519efca7 (16 commits)</li> <li>arm-trusted-firmware: Update from commit id 37366af8d4 to 88b2d81345 (214 commits)</li> <li>fsp: Update from commit id 3beceb01f9 to 481ea7cf0b (15 commits)</li> <li>intel-microcode: Update from commit id 6f36ebde45 to 6788bb07eb (1 commit)</li> <li>vboot: Update from commit id 0c11187c75 to 24cb127a5e (24 commits)</li> <li>genoa_poc/opensil: New submodule updated to 0411c75e17 (41 commits)</li> </ul> <h3 class="wp-block-heading">External payloads</h3> <ul class="wp-block-list"> <li>U-Boot: Use github mirror and the latest version</li> <li>edk2: Update default branch for MrChromebox repo to 2023-09</li> </ul> <h2 class="wp-block-heading">Platform Updates</h2> <h3 class="wp-block-heading">Added 17 mainboards</h3> <ul class="wp-block-list"> <li>AMD Onyx</li> <li>Google: Anraggar</li> <li>Google: Brox</li> <li>Google: Chinchou</li> <li>Google: Ciri</li> <li>Google: Deku</li> <li>Google: Deku4ES</li> <li>Google: Dexi</li> <li>Google: Dochi</li> <li>Google: Nokris</li> <li>Google: Quandiso</li> <li>Google: Rex4ES EC ISH</li> <li>Intel: Meteorlake-P RVP with Chrome EC for non-Prod Silicon</li> <li>Purism Librem 11</li> <li>Purism Librem L1UM v2</li> <li>Siemens FA EHL</li> <li>Supermicro X11SSW-F</li> </ul> <h3 class="wp-block-heading">Added 1 SoC</h3> <ul class="wp-block-list"> <li>src/soc/amd/genoa</li> </ul> <h2 class="wp-block-heading">Statistics from the 4.21 to the 4.22 release</h2> <ul class="wp-block-list"> <li>Total Commits: 977</li> <li>Average Commits per day: 10.98</li> <li>Total lines added: 62993</li> <li>Average lines added per commit: 64.48</li> <li>Number of patches adding more than 100 lines: 60</li> <li>Average lines added per small commit: 37.55</li> <li>Total lines removed: 30042</li> <li>Average lines removed per commit: 30.75</li> <li>Total difference between added and removed: 32951</li> <li>Total authors: 135</li> <li>New authors: 14</li> </ul> <h2 class="wp-block-heading">Significant Known and Open Issues</h2> <p>Issues from the coreboot bugtracker: https://ticket.coreboot.org/</p> <h3 class="wp-block-heading">Payload-specific issues</h3> <figure class="wp-block-table"><table><thead><tr><th>Bug #</th><th>Subject</th></tr></thead><tbody><tr><td>499</td><td>edk2 boot fails with RESOURCE_ALLOCATION_TOP_DOWN enabled</td></tr><tr><td>496</td><td>Missing malloc check in libpayload</td></tr><tr><td>484</td><td>No USB keyboard support with secondary payloads</td></tr><tr><td>414</td><td>X9SAE-V: No USB keyboard init on SeaBIOS using Radeon RX 6800XT</td></tr></tbody></table></figure> <h3 class="wp-block-heading">Platform-specific issues</h3> <figure class="wp-block-table"><table><thead><tr><th>Bug #</th><th>Subject</th></tr></thead><tbody><tr><td>509</td><td>SD Card hotplug not working on Apollo Lake</td></tr><tr><td>507</td><td>Windows GPU driver fails on Google guybrush & skyrim boards</td></tr><tr><td>506</td><td>APL/GML don’t boot OS when CPU microcode included “from tree”</td></tr><tr><td>505</td><td>Harcuvar CRB – 15 of 16 cores present in the operating system</td></tr><tr><td>499</td><td>T440p – EDK2 fails with RESOURCE_ALLOCATION_TOP_DOWN enabled</td></tr><tr><td>495</td><td>Stoney Chromebooks not booting PSPSecureOS</td></tr><tr><td>478</td><td>X200 booting Linux takes a long time with TSC</td></tr><tr><td>474</td><td>X200s crashes after graphic init with 8GB RAM</td></tr><tr><td>457</td><td>Haswell (t440p): CAR mem region conflicts with CBFS_SIZE > 8mb</td></tr><tr><td>453</td><td>Intel HDMI / DP Audio not present in Windows after libgfxinit</td></tr><tr><td>449</td><td>ThinkPad T440p fail to start, continuous beeping & LED blinking</td></tr><tr><td>448</td><td>Thinkpad T440P ACPI Battery Value Issues</td></tr><tr><td>446</td><td>Optiplex 9010 No Post</td></tr><tr><td>439</td><td>Lenovo X201 Turbo Boost not working (stuck on 2,4GHz)</td></tr><tr><td>427</td><td>x200: Two battery charging issues</td></tr><tr><td>412</td><td>x230 reboots on suspend</td></tr><tr><td>393</td><td>T500 restarts rather than waking up from suspend</td></tr><tr><td>350</td><td>I225 PCIe device not detected on Harcuvar</td></tr></tbody></table></figure> <h2 class="wp-block-heading">Plans for the next release</h2> <ul class="wp-block-list"> <li>Finish adding chipset device trees for all SOCs</li> <li>Improve code for options/setup</li> <li>Start reformatting C files with clang-format</li> <li>Add warning/error step for Makefiles at the end</li> </ul> <h2 class="wp-block-heading">coreboot Links and Contact Information</h2> <ul class="wp-block-list"> <li>Main Website: https://www.coreboot.org</li> <li>Downloads: https://coreboot.org/downloads.html</li> <li>Source control: https://review.coreboot.org</li> <li>Documentation: https://doc.coreboot.org</li> <li>Issue tracker: https://ticket.coreboot.org/projects/coreboot</li> <li>Donations: https://coreboot.org/donate.html</li> </ul> </div><!-- .entry-content --> <footer class="entry-footer"> <span class="posted-on"><span class="screen-reader-text">Posted on </span><a href="https://blogs.coreboot.org/blog/2023/11/28/coreboot-4-22-4-22-01-have-been-released/" rel="bookmark"><time class="entry-date published" datetime="2023-11-28T21:33:22+00:00">November 28, 2023</time><time class="updated" datetime="2023-11-28T21:33:23+00:00">November 28, 2023</time></a></span><span class="byline"><span class="author vcard"><span class="screen-reader-text">Author </span><a class="url fn n" href="https://blogs.coreboot.org/blog/author/felixsinger/">Felix Singer</a></span></span><span class="cat-links"><span class="screen-reader-text">Categories </span><a href="https://blogs.coreboot.org/blog/category/coreboot/" rel="category tag">coreboot</a></span> </footer><!-- .entry-footer --> </article><!-- #post-8534 --> <article id="post-8509" class="post-8509 post type-post status-publish format-standard hentry category-coreboot tag-gsoc"> <header class="entry-header"> <h2 class="entry-title"><a href="https://blogs.coreboot.org/blog/2023/11/16/updating-lz4-during-my-gsoc/" rel="bookmark">Updating LZ4 during my GSoC</a></h2> </header><!-- .entry-header --> <div class="entry-content"> <h3 class="wp-block-heading">Introduction</h3> <p>In this blog post, I will give an insight into my Google Summer of Code project, where I worked on coreboot. My target goals were updating compression and decompression algorithms LZ4 and LZMA to their newest version.</p> <p>In the whole process, I learned a lot about coreboot as an open-source community, and about GSoC, which could help students considering applying for a GSoC themselves.</p> <p>This blog won’t be addressing technical details, there will be a section at the end about my work and the results of it, but the rest of the blog will be a bit more meta.</p> <h3 class="wp-block-heading">What did I learn about open-source communities?</h3> <p>Before this project, I never contributed to any open-source project. My studies don’t involve much programming, therefore I’m not that professional, my programming skills are homebrewed. Now open source communities, especially as big as coreboot, really intimidated me (they still do somehow). There are many people, all of them probably better programmers than me, having more knowledge of the project as well. How could I help them with anything useful at all? And what if I push my first patch and it’s just embarrassing? Having a mentor helped, I think without someone to talk to, I would have never stuck my nose into any big open-source project.</p> <p>And all the people I met were very kind and helpful if needed. And I learned that critics, especially in text form, may sound harsher in my head than they are meant to.</p> <h3 class="wp-block-heading">Thoughts about Google’s Summer of Code</h3> <p>GSoC is a really good opportunity to get a feeling for working on open source. If you are a student searching for insight into open source, guided by a mentor, a GSoC project can be just right for you.</p> <p>But something I underestimated, was, how time-intensive such a project (even a medium one) is. I probably was too naive, but beforehand, I just talked myself into “Yeah this won’t be a problem, I can just work around two days a week for this, just shift stuff to other days.” Well, it turns out, that’s not how workload and mental load work. For me at least. I do work besides my studies and in the first weeks of GSoC, I was overwhelmed by the combination. Besides having fewer hours to do other things, just having more things to think about can be quite stressful under some conditions.</p> <p>GSoC allows you to stretch your project, so there is less work per week. In total, the project hours stay the same. This opportunity really helped me because I underestimated the load the weekly hours would apply.</p> <p>If I were to apply to GSoC again, I would double-check if such a commitment in terms of work is feasible for me. And that I would recommend to everyone thinking about applying. GSoC can be interesting and fun, but you need to be able to provide the time needed for the project.</p> <h3 class="wp-block-heading">What did I do and achieve?</h3> <p>I started my project by updating LZ4 code in coreboot. After that, I planned to move on to another compression algorithm, LZMA. My hopes were to increase the decompression speed and the compression ratio at the same time. Looking at the release notes for LZ4 since the version currently used by coreboot (spanning 8 years of releases), they stated an increase in speed and compression factor.</p> <p>To get an overview, I first searched for all places where LZ4 was used and checked the version which the code was from. I found out, that there are five files containing code from the LZ4 repository, where every file contains another subset of functions from the original file. 3 of these files were imported from LZ4 wrapper files.</p> <p>Then I fetched LZ4 code from the newest LZ4 release and merged it into the files where old LZ4 code was used. After merging, there were many LZ4 functions never used in our use case. Therefore I searched for each source file through each wrapper file to find out which functions were used and which I could remove. This way I could ensure there was no unused code in these files, providing a better overview</p> <p>After that, there still were many errors that needed to be resolved. That took the most time, being more complicated than I assumed. In the end, all tests passed, and building a rom and running it with QEMU worked just fine, my last ToDo was to test how much the new version was faster than the old if it was at all.</p> <p>Release notes stated many speed improvements, so I hoped this would show up after my work.</p> <p>The whole process took longer than I thought. Therefore I will miss the goal of updating LZMA. As I am writing this, my patch is open for review and I am in the process of creating statistics that may show that there is a speed improvement. If there is not, maybe there is no good reason to change to a newer LZ4 version. As one comment states, coreboot does require safe in-place decompression, which may be a problem with the new version and thus would have to be checked.</p> <p>My work is public on the coreboot Gerrit under this link <a href="https://review.coreboot.org/c/coreboot/+/77148">https://review.coreboot.org/c/coreboot/+/77148</a>. I do hope my patch will be merged, as I want to contribute to this project. But even if a merge may be rejected, that is part of open-source work too. I’ll try to improve on my next patch. This is my first open source contribution and it’s not perfect, but it certainly won’t be my last.</p> <h3 class="wp-block-heading">What could be done in the future?</h3> <p>As stated in a comment on my patch, in-place decompression is important for coreboot. There is a merged pull request from 2016 resolving that issue, but its functionality may have been lost in further development. Therefore, the new LZ4 version has to be checked for in-place safety.</p> <p>To tweak compression/decompression speeds and compression factor one might want to edit compression parameters. One could do this using a Kconfig entry.</p> <p>Also, it occurred that after building coreboot (running make in coreboot dictionary), when memory regions and sizes of the coreboot.rom are printed, there is no compression listed for the payload, even when it certainly has been compressed.</p> <h3 class="wp-block-heading">Statistics</h3> <p>I tested this on my laptop with KVM and QEMU, on an AMD® Ryzen 5 5500u. I changed my system’s CPU affiliation, to make 2 of my cores unused (they still got used, but not much, usually ~1%). Then I assigned these 2 CPUs to my VM to make different runs more comparable. Still, different runs got different timings, so I made 6 runs for the old LZ4 and the new LZ4 version each.</p> <figure class="wp-block-table"><table><thead><tr><th></th><th>Avg ramstage decompression time</th><th>Ramstage decompression time std dev</th><th>Avg payload decompression time</th><th>Payload decompression time std dev</th></tr></thead><tbody><tr><td>Current version</td><td>420µs</td><td>54µs</td><td>229µs</td><td>64µs</td></tr><tr><td>Updated version</td><td>520µs</td><td>113µs</td><td>219µs</td><td>4µs</td></tr></tbody></table></figure> <figure class="wp-block-table"><table><thead><tr><th></th><th>Ramstage compression ratio</th><th>Payload compression ratio</th></tr></thead><tbody><tr><td>Current version</td><td>1,507</td><td>1,452</td></tr><tr><td>Updated version</td><td>1,51</td><td>1,454</td></tr></tbody></table></figure> <p>These values indicate that there is a very small improvement in the compression ratio. Regarding decompression time, most tests have a relatively high standard deviation, which makes the results less statistically relevant. Ramstage decompression seems to have slowed down (~24%) while average payload decompression got 4-5% faster.</p> <p>All in all, these results are everything but exciting to me. Although a newer version may have other advantages, it seems that there is no decompression time improvement as I hoped and compression ratio improvements are so small, that they might not be noticeable.</p> </div><!-- .entry-content --> <footer class="entry-footer"> <span class="posted-on"><span class="screen-reader-text">Posted on </span><a href="https://blogs.coreboot.org/blog/2023/11/16/updating-lz4-during-my-gsoc/" rel="bookmark"><time class="entry-date published" datetime="2023-11-16T19:50:00+00:00">November 16, 2023</time><time class="updated" datetime="2023-11-16T20:21:14+00:00">November 16, 2023</time></a></span><span class="byline"><span class="author vcard"><span class="screen-reader-text">Author </span><a class="url fn n" href="https://blogs.coreboot.org/blog/author/pmacher/">Philipp Macher</a></span></span><span class="cat-links"><span class="screen-reader-text">Categories </span><a href="https://blogs.coreboot.org/blog/category/coreboot/" rel="category tag">coreboot</a></span><span class="tags-links"><span class="screen-reader-text">Tags </span><a href="https://blogs.coreboot.org/blog/tag/gsoc/" rel="tag">GSoC</a></span> </footer><!-- .entry-footer --> </article><!-- #post-8509 --> <article id="post-8443" class="post-8443 post type-post status-publish format-standard hentry category-coreboot"> <header class="entry-header"> <h2 class="entry-title"><a href="https://libreboot.org/news/libreboot20231101.html" rel="bookmark">Libreboot 20231101 released!</a></h2> </header><!-- .entry-header --> <div class="entry-content"> </div><!-- .entry-content --> <footer class="entry-footer"> <span class="posted-on"><span class="screen-reader-text">Posted on </span><a href="https://libreboot.org/news/libreboot20231101.html" rel="bookmark"><time class="entry-date published" datetime="2023-11-02T19:35:04+00:00">November 2, 2023</time><time class="updated" datetime="2023-11-03T17:22:57+00:00">November 3, 2023</time></a></span><span class="byline"><span class="author vcard"><span class="screen-reader-text">Author </span><a class="url fn n" href="https://blogs.coreboot.org/blog/author/news-for-libreboot-org/">News for libreboot.org</a></span></span><span class="cat-links"><span class="screen-reader-text">Categories </span><a href="https://blogs.coreboot.org/blog/category/coreboot/" rel="category tag">coreboot</a></span> </footer><!-- .entry-footer --> </article><!-- #post-8443 --> <article id="post-8435" class="post-8435 post type-post status-publish format-standard hentry category-coreboot"> <header class="entry-header"> <h2 class="entry-title"><a href="https://mjg59.dreamwidth.org/68350.html" rel="bookmark">Why ACPI?</a></h2> </header><!-- .entry-header --> <div class="entry-content"> "Why does ACPI exist" - - the greatest thread in the history of forums, locked by a moderator after 12,239 pages of heated debate, wait no let me start again. Why does ACPI exist? In the beforetimes power management on x86 was done by jumping to an opaque BIOS entry point and hoping it would do the right thing. It frequently didn't. We called this <a href="https://en.wikipedia.org/wiki/Advanced_Power_Management">Advanced Power Management</a> (Advanced because before this power management involved custom drivers for every machine and everyone agreed that this was a bad idea), and it involved the firmware having to save and restore the state of every piece of hardware in the system. This meant that assumptions about hardware configuration were baked into the firmware - failed to program your graphics card exactly the way the BIOS expected? Hurrah! It's only saved and restored a subset of the state that you configured and now potential data corruption for you. The developers of ACPI made the reasonable decision that, well, maybe since the OS was the one setting state in the first place, the OS should restore it. So far so good. But some state is fundamentally device specific, at a level that the OS generally ignores. How should this state be managed? One way to do that would be to have the OS know about the device specific details. Unfortunately that means you can't ship the computer without having OS support for it, which means having OS support for every device (exactly what we'd got away from with APM). This, uh, was not an option the PC industry seriously considered. The alternative is that you ship something that abstracts the details of the specific hardware and makes that abstraction available to the OS. This is what ACPI does, and it's also what things like Device Tree do. Both provide static information about how the platform is configured, which can then be consumed by the OS and avoid needing device-specific drivers or configuration to be built-in. The main distinction between Device Tree and ACPI is that Device Tree is purely a description of the hardware that exists, and so still requires the OS to know what's possible - if you add a new type of power controller, for instance, you need to add a driver for that to the OS before you can express that via Device Tree. ACPI decided to include an interpreted language to allow vendors to expose functionality to the OS without the OS needing to know about the underlying hardware. So, for instance, ACPI allows you to associate a device with a function to power down that device. That function may, when executed, trigger a bunch of register accesses to a piece of hardware otherwise not exposed to the OS, and that hardware may then cut the power rail to the device to power it down entirely. And that can be done without the OS having to know anything about the control hardware. How is this better than just calling into the firmware to do it? Because the fact that ACPI declares that it's going to access these registers means the OS can figure out that it shouldn't, because it might otherwise collide with what the firmware is doing. With APM we had no visibility into that - if the OS tried to touch the hardware at the same time APM did, boom, almost impossible to debug failures (This is why various hardware monitoring drivers refuse to load by default on Linux - the firmware declares that it's going to touch those registers itself, so Linux decides not to in order to avoid race conditions and potential hardware damage. In many cases the firmware offers a collaborative interface to obtain the same data, and a driver can be written to get that. <a href="https://bugzilla.kernel.org/show_bug.cgi?id=204807#c37">this bug comment</a> discusses this for a specific board) Unfortunately ACPI doesn't entirely remove opaque firmware from the equation - ACPI methods can still trigger System Management Mode, which is basically a fancy way to say "Your computer stops running your OS, does something else for a while, and you have no idea what". This has all the same issues that APM did, in that if the hardware isn't in exactly the state the firmware expects, bad things can happen. While historically there were a bunch of ACPI-related issues because the spec didn't define every single possible scenario and also there was no conformance suite (eg, should the interpreter be multi-threaded? Not defined by spec, but influences whether a specific implementation will work or not!), these days overall compatibility is pretty solid and the vast majority of systems work just fine - but we do still have some issues that are largely associated with System Management Mode. One example is a <a href="https://lore.kernel.org/all/20220429030501.1909-3-mario.limonciello@amd.com/">recent Lenovo one</a>, where the firmware appears to try to poke the NVME drive on resume. There's some indication that this is intended to deal with transparently unlocking self-encrypting drives on resume, but it seems to do so without taking IOMMU configuration into account and so things explode. It's kind of understandable why a vendor would implement something like this, but it's also kind of understandable that doing so without OS cooperation may end badly. This isn't something that ACPI enabled - in the absence of ACPI firmware vendors would just be doing this unilaterally with even less OS involvement and we'd probably have even more of these issues. Ideally we'd "simply" have hardware that didn't support transitioning back to opaque code, but we don't (ARM has basically the same issue with TrustZone). In the absence of the ideal world, by and large ACPI has been a net improvement in Linux compatibility on x86 systems. It certainly didn't remove the "Everything is Windows" mentality that many vendors have, but it meant we largely only needed to ensure that Linux behaved the same way as Windows in a finite number of ways (ie, the behaviour of the ACPI interpreter) rather than in every single hardware driver, and so the chances that a new machine will work out of the box are much greater than they were in the pre-ACPI period. There's an alternative universe where we decided to teach the kernel about every piece of hardware it should run on. Fortunately (or, well, unfortunately) we've seen that in the ARM world. Most device-specific simply never reaches mainline, and most users are stuck running ancient kernels as a result. Imagine every x86 device vendor shipping their own kernel optimised for their hardware, and now imagine how well that works out given the quality of their firmware. Does that really seem better to you? It's understandable why ACPI has a poor reputation. But it's also hard to figure out what would work better in the real world. We could have built something similar on top of <a href="https://en.wikipedia.org/wiki/Open_Firmware">Open Firmware</a> instead but the distinction wouldn't be terribly meaningful - we'd just have Forth instead of the ACPI bytecode language. Longing for a non-ACPI world without presenting something that's better and actually stands a reasonable chance of adoption doesn't make the world a better place. <img src="https://www.dreamwidth.org/tools/commentcount?user=mjg59&ditemid=68350" width="30" height="12" alt="comment count unavailable" style="vertical-align: middle;"/> comments </div><!-- .entry-content --> <footer class="entry-footer"> <span class="posted-on"><span class="screen-reader-text">Posted on </span><a href="https://mjg59.dreamwidth.org/68350.html" rel="bookmark"><time class="entry-date published" datetime="2023-11-01T06:30:06+00:00">November 1, 2023</time><time class="updated" datetime="2023-11-03T17:22:44+00:00">November 3, 2023</time></a></span><span class="byline"><span class="author vcard"><span class="screen-reader-text">Author </span><a class="url fn n" href="https://blogs.coreboot.org/blog/author/matthew-garrett/">Matthew Garrett</a></span></span><span class="cat-links"><span class="screen-reader-text">Categories </span><a href="https://blogs.coreboot.org/blog/category/coreboot/" rel="category tag">coreboot</a></span> </footer><!-- .entry-footer --> </article><!-- #post-8435 --> <article id="post-8428" class="post-8428 post type-post status-publish format-standard hentry category-coreboot"> <header class="entry-header"> <h2 class="entry-title"><a href="https://libreboot.org/news/libreboot20231021.html" rel="bookmark">Libreboot 20231021 released!</a></h2> </header><!-- .entry-header --> <div class="entry-content"> </div><!-- .entry-content --> <footer class="entry-footer"> <span class="posted-on"><span class="screen-reader-text">Posted on </span><a href="https://libreboot.org/news/libreboot20231021.html" rel="bookmark"><time class="entry-date published" datetime="2023-10-21T13:05:05+00:00">October 21, 2023</time><time class="updated" datetime="2023-10-30T11:06:54+00:00">October 30, 2023</time></a></span><span class="byline"><span class="author vcard"><span class="screen-reader-text">Author </span><a class="url fn n" href="https://blogs.coreboot.org/blog/author/news-for-libreboot-org/">News for libreboot.org</a></span></span><span class="cat-links"><span class="screen-reader-text">Categories </span><a href="https://blogs.coreboot.org/blog/category/coreboot/" rel="category tag">coreboot</a></span> </footer><!-- .entry-footer --> </article><!-- #post-8428 --> <article id="post-8446" class="post-8446 post type-post status-publish format-standard hentry category-coreboot"> <header class="entry-header"> <h2 class="entry-title"><a href="https://www.obe.tv/improving-the-boot-times-of-it-servers/?utm_source=rss&utm_medium=rss&utm_campaign=improving-the-boot-times-of-it-servers" rel="bookmark">Improving the boot times of IT servers with a custom BIOS</a></h2> </header><!-- .entry-header --> <div class="entry-content"> <img decoding="async" loading="lazy" class="aligncenter wp-image-10831" src="https://blogs.coreboot.org/files/2023/09/coreboot-2.png" alt="" width="500" height="258" />One of the big challenges with the use of IT hardware such as computer servers in broadcasting is excessively long boot times of up to ten minutes. In reactive broadcasting environments this may cause problems or be frustrating for operators. Most of the boot time in a server consists of the <a href="https://en.wikipedia.org/wiki/BIOS">BIOS</a> boot time plus the boot time of the Operating System. In our case the boot time of the OS is relatively small compared to the BIOS so this article will focus on BIOS changes. A computer BIOS (or something more modern like UEFI) is doing a very complex job setting up hardware and doing things like <a href="https://www.systemverilog.io/design/ddr4-initialization-and-calibration/">memory training</a>. However, most BIOSes on servers are written by third-party vendors and arguably there is an incentive for third-party BIOS vendors to add features (that some would see as unnecessary complexity) to their BIOSes which increases boot time. This is where <a href="https://coreboot.org/">coreboot</a> comes in. Coreboot is an Open Source BIOS implementation (and so much more) with a substantially smaller footprint compared to vendor BIOSes. This allows for faster boot times amongst many other benefits. But its downside is that every motherboard must be added manually, quite a challenge for a company with lots of <a href="http://obe.tv/turn-key-hardware-solutions/">different motherboards in use</a>. It also only supports entry-level servers for the time being. Servers with Xeon Scalable CPUs are not supported owing to limitations from Intel. Coreboot thankfully <a href="https://doc.coreboot.org/mainboard/supermicro/x11-lga1151-series/x11-lga1151-series.html">supported the X11 series from Supermicro</a>, and we had a similar old server in our lab, although we had an X11SSW-F, a model that was not supported. As these motherboards are similar, after some work understanding the differences between PCI Express (PCIe) slots and USB ports compared to other boards it was possible to <a href="https://review.coreboot.org/c/coreboot/+/77610">write a patch</a> that booted successfully. There was an obvious difference in boot time but it was time to measure. This was done by a <a href="https://en.wikipedia.org/wiki/Cron">cronjob</a> running every five minutes and logging the date of reboot and logging the first message from the Linux kernel in syslog. Note that we were only measuring “warm” boot times and the test was run 15 times. <table> <tbody> <tr> <td>Vendor BIOS boot time</td> <td>Coreboot BIOS boot time</td> </tr> <tr> <td>83±10s</td> <td>38±5s</td> </tr> </tbody> </table> <strong>Twice as fast!</strong> It’s likely there are possible settings changes to both the Vendor BIOS and Coreboot to reduce boot time further. The bigger issue is that in both BIOSes a substantial amount of time is spent in the closed <a href="https://www.intel.com/content/www/us/en/intelligent-systems/intel-firmware-support-package/intel-fsp-overview.html">Intel Firmware Support Package</a> that can’t be modified. We also need to check that Coreboot doesn’t affect functionality of servers, so we wrote a script to reboot the server and start up an 8-channel decoder every 30 minutes. After 730 reboots (around two weeks nonstop!), we saw from logs that every single reboot was successful and the decoders started successfully. We also have plans to add coreboot support to more modern motherboards and roll this out to customers on request. Coreboot also has some benefits for debugging PCIe related issues, but more on that another day. </div><!-- .entry-content --> <footer class="entry-footer"> <span class="posted-on"><span class="screen-reader-text">Posted on </span><a href="https://www.obe.tv/improving-the-boot-times-of-it-servers/?utm_source=rss&utm_medium=rss&utm_campaign=improving-the-boot-times-of-it-servers" rel="bookmark"><time class="entry-date published" datetime="2023-09-20T17:52:06+00:00">September 20, 2023</time><time class="updated" datetime="2023-11-03T17:25:05+00:00">November 3, 2023</time></a></span><span class="byline"><span class="author vcard"><span class="screen-reader-text">Author </span><a class="url fn n" href="https://blogs.coreboot.org/blog/author/open-broadcast-systems/">Open Broadcast Systems</a></span></span><span class="cat-links"><span class="screen-reader-text">Categories </span><a href="https://blogs.coreboot.org/blog/category/coreboot/" rel="category tag">coreboot</a></span> </footer><!-- .entry-footer --> </article><!-- #post-8446 --> <nav class="navigation pagination" aria-label="Posts pagination"> <h2 class="screen-reader-text">Posts pagination</h2> <div class="nav-links"><span aria-current="page" class="page-numbers current"><span class="meta-nav screen-reader-text">Page </span>1</span> <a class="page-numbers" href="https://blogs.coreboot.org/blog/category/coreboot/page/2/"><span class="meta-nav screen-reader-text">Page </span>2</a> <span class="page-numbers dots">…</span> <a class="page-numbers" href="https://blogs.coreboot.org/blog/category/coreboot/page/26/"><span class="meta-nav screen-reader-text">Page </span>26</a> <a class="next page-numbers" href="https://blogs.coreboot.org/blog/category/coreboot/page/2/">Next page</a></div> </nav> </main><!-- .site-main --> </section><!-- .content-area --> </div><!-- .site-content --> <footer id="colophon" class="site-footer" role="contentinfo"> <div class="site-info"> <a href="https://wordpress.org/">Proudly powered by WordPress</a> </div><!-- .site-info --> </footer><!-- .site-footer --> </div><!-- .site --> </body> </html>