digimend-kernel-drivers VS printf

- DIGImend and OpenTabletDriver look pretty similar in github activity(?)

I somehow can't watch any video on browser and discord after I try to install pen tablet driver DIGImend from source and I don't know what did I do wrong, I have try to restart pc / install some necessary package like ffmpeg / update driver / restart my wifi adapter and follow this solutions but none of them work and I don't want to reinstall my OS. PC details: OS : Garuda linux Kernel: 6.2.7-zen1-1-zen DE: GNOME 43.3 CPU: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx (8) @ 2.10 GPU: AMD ATI Radeon Vega Series / Radeon Vega Mobile Series Memory: 5863MiB

There is this project on GitHub (and their website) providing drivers for various graphics tablets on Linux. A while ago it helped me a ton with my 'Gaomon M106K' (which I believe is just a rebranded Huion tablet). Maybe you can get it yours working with this too.

I've never tried using it with a Pi, but the Digimend drivers work for my Huion tablet on Arch.

If your tablet isn't supported by the native drivers, you may try either the OpenTabletDriver or the DIGImend drivers.

I have a majestic piece of Chinese genius known as Ugee M708 aka XP-Pen Star 03 aka Parblo A610 aka UC-Logic TABLET 1060 aka, UC-LOIC 1060 (which is what it reports itself as) and it works fine, but requires Digimend drivers to be installed.

[this issue](https://github.com/DIGImend/digimend-kernel-drivers/issues/340)

https://github.com/mpaland/printf i think this would work

Seems unlikely. My spot check of the the two vfprintf implementations shows no flow from one to the other, and shows that part of the Cosmopolitan code has an older lineage than nolibc.

The nolibc source has many reference to copyright held by "Willy Tarreau", under LGPL-2.1 OR MIT license, with a copyright date starting in 2017.

The string "Tarreau" does not exist in the Cosmopolitan library, so that's a strong negative there. Let's look closer.

The file organization is quite different. And so is the implementation. So that's another negative.

Compare the vfprintf in nolibc at https://elixir.bootlin.com/linux/v6.2-rc4/source/tools/inclu... (a 'minimal vfprintf()') with the one in cosmopolitan starting at https://github.com/jart/cosmopolitan/blob/master/libc/stdio/....

Right away we can see nolibc places many functions in the same file while Cosmopolitan uses a one-function-per-filename organization.

Cosmopolitan's fvprintf locks the file (which nolibc doesn't need to do) then calls vfprintf_unlocked which calls __fmt at https://github.com/jart/cosmopolitan/blob/master/libc/fmt/fm... , which is the actual implementation. It look very different from NOLIBC's.

Okay, so perhaps that's they way now but not at the beginning?

We can also go back to Cosmopolitan's original implementation and see how vfprintf goes through https://github.com/jart/cosmopolitan/blob/c91b3c50068224929c... to call "palandprintf", which https://github.com/jart/cosmopolitan/blob/c91b3c50068224929c... says is copyright "Marco Paland" from 2014-2019.

That's a few years older than the start of nolibc, available from https://github.com/mpaland/printf , and part of https://github.com/embeddedartistry/libc , a "libc targeted for embedded systems usage".

Thus, multiple factors seem to agree that nolibc code is not used in the Cosmopolitan library.

I wrap this C implementation in a C++ Logger class and use it to "print" into a simple buffer. Then the static buffer is periodically unrolled into a transport layer using a static Logger::transmit() function in my BSP. I'm working with very little flash, so the linked implementation is essential.

There are many good and tiny printf's fir embedded on GitHub. https://github.com/mpaland/printf eg Better than the bsd printf mostly

I'm sure sprintf itself is working in their library, so try to find other issues first, BUT, as a last resort you can try another lib: https://github.com/mpaland/printf/

looked at that account, found this one too