Ideas#
How to participate?
Contributors are expected to go through the list of ideas dropdown below and join the discussion by clicking on the
Discuss on forum
button. All ideas have colorful badges for Complexity
and
Size
for making the selection process easier for contributors. Anyone is welcome to
introduce new ideas via the forum gsoc-ideas tag.
Only ideas with sufficiently experienced mentor backing as deemed by the administrators will
be added here.
Complexity |
Size |
---|---|
High complexity |
350 hours |
Medium complexity |
175 hours |
Low complexity |
90 hours |
FPGA gateware improvements Medium complexity 175 hours
BeagleV-Fire features RISC-V 64-bit CPU cores and FPGA fabric. In that FPGA fabric, we’d like to implement a RISC-V 32-bit CPU core with operations optimized for low-latency GPIO. This is similar to the programmable real-time unit (PRU) RISC cores popularized on BeagleBone Black.
Linux kernel improvements Medium complexity 350 hours
Utilize the beagle-tester
application and Buildroot
along with device-tree and udev symlink concepts within
the OpenBeagle continuous integration server context to create a regression test suite for the Linux kernel
and device-tree overlays on various Beagle computers.
Linux kernel improvements Medium complexity 175 hours
These are the drivers that are used to enable Linux to use a BeagleConnect Freedom as a SubGHz IEEE802.15.4 radio (gateway). They need to be part of upstream Linux to simplify on-going support. There are several gaps that are known before they are acceptable upstream.
Automation and industrial I/O Medium complexity 175 hours
librobotcontrol
support for newer boardsPreliminary librobotcontrol support for BeagleBone AI, BeagleBone AI-64 and BeagleV-Fire has been drafted, but it needs to be cleaned up. We can also work on support for Raspberry Pi if UCSD releases their Hat for it.
Visit our forum to see newer ideas being discussed!
Tip
You can also check our our Old GSoC Ideas and Past Projects for inspiration.