|
netlink interface for ethtoola project by mkubecek There seems to be an overall consensus that the ioctl interface used by ethtool is a poor design as it's inflexible, error prone and notoriously hard to extend. It should clearly be replaced by netlink and obsoleted. Unfortunately not much actual work has been done in that direction until this project started. The project started in Hackweek 16 (fall 2017) and has been worked on since, both in Hackweek 17-19 and outside. First two parts of kernel implementation are in mainline since 5.6-rc1, first part of userspace implementation (ethtool utility) has been submitted to upstream at the end of Hackweek 19 (2020-02-16). 
|
perf-bench ipca project by dbueso The state of the art of sysv/posix ipc benchmarking is a combination of ad-hoc programs scattered over the internet. While some mechanisms, such as sysv semaphores, have a lot of coverage, others really lack (message queues), and some are simply non-existent; albeit some of the legacy flavors we aren't too concerned with, other than them being functionally correct. Consolidate all this by taking the good benchmarks and implement new ones where needed, such as message queues, everything around the 'perf bench' framework. This will both improve the lives of us who hack on kenrel ipc as well as improve coverage overall. Eventually mmtests should be updated as well. 
|
work on sunxi a64 cpufreq driver (for teres-1, pine64)an idea by mbrugger With the teres-1 [1] laptop we have a first arm64 device we could use as end-users. Much work to run mainline kernel + u-boot was done already. But power consumption of the laptop is not optimal (~2 hours of battery life time). The idea is to support cpufreq for the A64 SoC upstream, which would enable the teres-1, pine64 and pinebook to run more power efficient. up to now it seems nobody is working on the driver [2]. |
Out-of-the-box SPD supportan invention by jdelvare In order to see the SPD (detailed memory information) data, the user currently has to manually load the needed kernel driver. Which driver to load depends on the memory type. Depending on the driver user, the devices may even have to be instantiated manually and this is a non-trivial multi-step task. Plus you need to be root to do it. I would like to attempt to automatize all this at least in the most common and simple cases like Intel x86 desktop. The idea would be to figure out the memory type and the I2C address of the SPD EEPROMs based on DMI data. If the DMI data is of good quality then it should be possible to automatically figure out which driver to use and to instantiate the devices at boot time. 
|
ethtool ops for netdevsima project by mkubecek This can be seen as a subproject of ethtool netlink interface but from the technical view it's independent. Every new piece of software is going to be buggy and with frequent changes and rewrites, new regressions are introduced. Automated selftests can help a lot but as ethtool deals with hardware devices, we do not want these tests to depend on a specific hardware. The netdevsim driver was created as a virtual device which (unlike e.g. dummy) cannot be used for actual network traffic but implements various configuration interfaces so that it can be used for their (automated) testing.
|
Investigate C-Sky architecturean invention by a_faerber The youngest architecture addition to the mainline Linux kernel was C-Sky (arch/csky/). I have a GX6605S board booting a downstream 4.9 kernel. It uses a proprietary GxLoader bootloader (similarities with U-Boot exist but no sources...) with uImage and gx6605s.dtb files in a FAT partition on USB stick. 
|
openSUSE/SLE/Mainline U-boot for some not-yet-supported ARM64 boards