From: "Marvin Häuser" <mhaeuser@posteo.de>
To: devel@edk2.groups.io, tejesh.anand@hotmail.com
Cc: Andrew Fish <afish@apple.com>, Leif Lindholm <leif@nuviainc.com>,
nathaniel.l.desimone@intel.com,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [GSoC 2022] How to begin contributing?
Date: Wed, 30 Mar 2022 21:18:53 +0000 [thread overview]
Message-ID: <82a068ff-683f-e07d-1206-dfb908ebc6a1@posteo.de> (raw)
In-Reply-To: <uP6U.1647559269212480114.8kY0@groups.io>
Hey Tejesh,
Sorry your mail doesn't get much activity. I think parsing-related
things are most important:
- String functions in BaseLib:
https://github.com/tianocore/edk2/blob/55637a2894babca97945eeca1da0d431f74f8627/MdePkg/Library/BaseLib/String.c
- DevicePathLib:
https://github.com/tianocore/edk2/tree/55637a2894babca97945eeca1da0d431f74f8627/MdePkg/Library/UefiDevicePathLib
I/O and protocols could also be interesting:
- Many firmware have this in prod, maybe UART:
https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Library/BaseSerialPortLib16550/BaseSerialPortLib16550.c
Maybe security guarantees:
- TCG Measuring is frankly very overcomplicated, but key:
https://github.com/tianocore/edk2/blob/master/SecurityPkg/Library/DxeTpm2MeasureBootLib/DxeTpm2MeasureBootLib.c
- Basically SMAP in software:
https://github.com/tianocore/edk2/blob/55637a2894babca97945eeca1da0d431f74f8627/StandaloneMmPkg/Library/StandaloneMmMemLib/StandaloneMmMemLib.c
Good luck with your proposal!
Best regards,
Marvin
On 18.03.22 00:21, Tejesh Anand wrote:
> Hello all, My name is Tejesh Anand, a first year computer engineering
> student. I'm interested applying for the task of writing more unit
> tests for edk2. I wanted to ask if anyone had any advice for a first
> issue to begin to contribute with?
>
> Thanks in advance!
>
prev parent reply other threads:[~2022-03-30 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 23:21 [GSoC 2022] How to begin contributing? Tejesh Anand
2022-03-30 21:18 ` Marvin Häuser [this message]
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=82a068ff-683f-e07d-1206-dfb908ebc6a1@posteo.de \
--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