public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Christian Walter <christian.walter@osfw.foundation>
To: devel@edk2.groups.io
Subject: [edk2-devel] Introduction OSFF ByteTalks Vol.1 - Webinar Series about Open-Source Firmware
Date: Mon, 26 Feb 2024 13:17:13 +0100	[thread overview]
Message-ID: <3380d7cd-c4e2-49fe-af5c-dc47ba5f91c9@osfw.foundation> (raw)

[-- Attachment #1: Type: text/plain, Size: 2103 bytes --]

Dear EDKII-Community,

The Open-Source Firmware Foundation (OSFF) is pleased to announce 
ByteTalks, a new series of online webinars focused on the open-source 
firmware community. ByteTalks aims to provide a platform for learning, 
sharing, and discussing the latest developments in open-source firmware. 
Each session features talks by experienced professionals, practical 
tutorials, and a chance for participants to ask questions and engage 
with the speakers. Whether you're deeply involved in firmware 
development or just interested in learning more about the field, 
ByteTalks offers valuable insights and connections to help you grow. 
Join us to explore the evolving world of open-source firmware together.

Announcing OSFF ByteTalks Vol. 1: “*FSP Customization - Remove 
non-mandatory components in the Intel FSP*”

In the realm of open-source firmware, creating a custom Firmware Support 
Package (FSP) binary is a pivotal step for developers aiming to enhance 
hardware compatibility and performance. The process involves 
understanding the hardware's initialization requirements, integrating 
coreboot or similar open-source firmware solutions, and customizing the 
FSP to meet specific system needs. Our guests Subrata and Vincent will 
talk about the process on customizing the Intel FSP and removing 
non-mandatory components.

For more information, check out the event page here: 
https://osfw.foundation/events/bytetalks-vol.-1/

In case you have any questions, feel free to reach out to me. In case 
you are also interested in joining the ByteTalks series as a speaker, 
feel free to reach out to me as well :)

Best,

Chris

-- 
*Christian Walter*



Open-Source Firmware Foundation
Email: christian.walter@osfw.foundation


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#115954): https://edk2.groups.io/g/devel/message/115954
Mute This Topic: https://groups.io/mt/104581212/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #2: Type: text/html, Size: 4017 bytes --]

                 reply	other threads:[~2024-02-26 13:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3380d7cd-c4e2-49fe-af5c-dc47ba5f91c9@osfw.foundation \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox