4 ms·
It's not so much that kernel development is all that difficult, but 99% of the things you could make that would be useful would be device drivers. And device dr
by phendrenad2 5y ago
It's not so much that kernel development is all that difficult, but 99% of the things you could make that would be useful would be device drivers. And device driver development requires an understanding of digital logic and the domain-specific "hardware APIs" (registers and stuff) exposed by various types of hardware.
- SilverRed 5y agoSo you would basically either have to be from the company that made the hardware, or have the full documentation for it, or be an insanely talented reverse engineer.
- goodcanadian 5y agoWell, the one good example I have from a few years ago was a relatively simple ADC PCI card. I did have documentation from the company. They had a Windows driver, but for Linux, their advice was direct memory writes (which requires root privileges). I didn't want the application to run as root, so I wrote a Linux diver for the card.
- mytailorisrich 5y agoYou need to have the datasheet. These are usually a Google search away and the way people develop drivers even in professional settings. For simple devices (e.g. I2C/SPI sensors) the functionality, number of registers, and procedures are usually very limited and it is not difficult.
- zsmi 5y agoFor simple devices probably user space is just fine. i.e. https://www.kernel.org/doc/Documentation/spi/spidev https://www.kernel.org/doc/Documentation/spi/spidev Usually only if you need an IRQ or something does it require kernel space.