diff options
Diffstat (limited to 'Documentation/devel/project-ideas.rst')
| -rw-r--r-- | Documentation/devel/project-ideas.rst | 12 |
1 files changed, 4 insertions, 8 deletions
diff --git a/Documentation/devel/project-ideas.rst b/Documentation/devel/project-ideas.rst index a3643298ab..4127b2556b 100644 --- a/Documentation/devel/project-ideas.rst +++ b/Documentation/devel/project-ideas.rst @@ -20,10 +20,8 @@ For GSoC, following barebox developers are mentoring: - Rouven Czerwinski (IRC: ``Emantor``) This list can be edited and extended by sending patches to the mailing list. -Other interesting ideas: Support for new file systems (EROFS, extfat, btrfs). -Switch device framework (currently scripts write into a ``/dev/switch`` file -to configure passthrough), Improvements for barebox-efi (e.g. as a coreboot -payload), ... etc. +Other interesting ideas: Support for new file systems (EROFS, extfat, btrfs), +improvements for barebox-efi (e.g. as a coreboot payload), ... etc. Ideas listed below should contain a title, description, expected outcomes, skills (and HW if any) required and a difficulty rating. @@ -158,8 +156,6 @@ on top of a block device which caches blocks previously read from the hardware driver, often by means of DMA. There are a number of improvements possible to increase throughput of barebox I/O: - - Support for higher MMC speed modes: The maximum currently supported - is 50/52 MHz and no DDR. - More efficient erase: Communication protocols like Android Fastboot encode large blocks of zeros specially. MMCs with erase-to-zero capability could perform such erases in the background instead @@ -187,13 +183,13 @@ barebox to a new board, for new users who are only interested in trying it out: The browser runs Tinyemu, a virtual machine in which barebox executes as if on real hardware and the user can manipulate the (virtual) hardware from the barebox shell and learn about barebox -conveniences: barebox.org/jsbarebox/ +conveniences: barebox.org/demo/ The project is about streamlining this demo: CPU usage currently is quite high and teaching barebox to idle the CPU (as we do on sandbox) didn't help. This needs to be analyzed with the profiling tools provided with modern browsers. The remainder of the project can then -focus on improving the jsbarebox tutorial. e.g. by adding new +focus on improving the tutorial inside the demo. e.g. by adding new peripherals to the virtual machine. Expected outcome is snappier and less CPU-intensive barebox demo. |