Thank you for the reply. I think I will stick with one of the suggested
project ideas for GSoC, but I will definitely continue to work on ports
for my hardware on the side.
Regarding the Ghidra loader project idea, is there an assigned mentor?
I have some questions regarding the scope of the project. In addition
to a loader for firmware images, I think scripts for importing common
UEFI types/structures/GUIDs could be useful. Similar scripts [1, 2] are
available for IDA Pro. Having such tools for Ghidra could assist with
UEFI reverse engineering.
Thank you again. I look forward to contributing to this project.
On Thu, Mar 28, 2019 at 11:16 AM Martin Roth <gaumless(a)gmail.com> wrote:
I think that porting the gigabyte platform could be at least part of
a GSOC project. The port by itself probably wouldn't be enough to be
considered a full project, since much of the work can already be done
automatically by autoport.
I'd probably discourage the HP port due to the age of the platform and
the possible difficulty with the embedded controller, but wouldn't
strictly rule it out as a gsoc project.
On Wed, Mar 27, 2019 at 12:40 PM Alex James <theracermaster(a)gmail.com>
I am a student interested in contributing to coreboot as part of GSoC
2019. I have
seen the ideas list on the documentation page, and I am
considering working on fixing issues reported by Coverity Scan, and maybe
additional work on firmware RE tools. However, I would like to know if
ports to new mainboards/systems would be an acceptable project. I have an
Ivy Bridge desktop (Gigabyte GA-Z77X-UD5H) as well as a Arrandale laptop
(HP Pavilion dv7), and I am interested in porting coreboot to these
platforms. I do have some experience with UEFI programming in C (as well as
coreboot mailing list -- coreboot(a)coreboot.org
To unsubscribe send an email to coreboot-leave(a)coreboot.org