Turn an android tablet into a drawing tablet

At the end of the project we should be able to use an android tablet as a drawing tablet in our Linux environment.

Plans of the Project

After some time I would like to move KF5 translation ahead again.

I want to understand the basics and architecture of KMS / DRM drivers in the kernel (also in mesa, but this project is more about the kernel-side). I will read docs and attempt to implement a virtual kernel-mode-setting driver (vkms) as described in Documentation/gpu/todo. This would be a KMS driver for a fake modesetting graphics device, just using normal system memory. This can be useful for learning, but judging from dri-developer discussions, also useful for testing hotplug races, plane blending and finding other KMS/DRI infrastructure bugs. Some items to implement:

Lenovo Tab 3 Business is nice piece of hardware with ARMv8 CPU and plenty of memory. It would be nice to try to boot some other OS. 1] collect information about HW and FW

The SMBIOS specification includes an informative annex providing conformance guidelines for DMI table implementations. I would like to write a checker tool to verify the conformance of DMI tables, based on this document. Such a tool could be useful for system firmware writers. We already have dmidecode which is able to locate and decode DMI tables. It should be fairly easy to reuse the same core and add an alternative structure parser, which would perform the checks instead of printing the decoded information.

As you know, SUSE acquired Openattic last year, which is a great storage management system. I want to learn and use openattic during this hack week.

We used trinity to make fuzzing test, but it hard to reproduce bugs. I'd like to try to use syzkaller or other fuzzy tools to find a stable process to reproduce fuzzy bugs.

Sometimes, you want a flexible way to handle certain situations involving C++ exceptions, particularly those for which alternative actions are either easily encapsulated, do not substantially interrupt the program flow, or must cross a foreign-function interface or thread boundary. A useful idiom is to rewrite attempts to perform an action with such forms of exception handling as instead returning a monadic value, like with C++17's std::optional<>: