I need wider support of drivers in LKL.
I changed my arch/lkl/Kconfig to add SCSI, input, USB, TTY and to drop NO_DMA
FIY, the associated usecase is to have a userspace usbip client.
I implemented trivial dma_map_ops, which only trigger a warning when called. (perhaps it would be better to even panic())
This is enough to have mass-storage/serial port/... over usbip working.
The usecase would be to have wide driver support as an Android application. On Android, one can access to /dev/bus/usb/XXX/YYY, but not the kernel functions.
Would it be possible to source drivers/Kconfig? Or is it too much work?
Is it better to activate one section at a time?
I need wider support of drivers in LKL.
I changed my arch/lkl/Kconfig to add SCSI, input, USB, TTY and to drop NO_DMA
FIY, the associated usecase is to have a userspace usbip client.
I implemented trivial dma_map_ops, which only trigger a warning when called. (perhaps it would be better to even panic())
This is enough to have mass-storage/serial port/... over usbip working.
The usecase would be to have wide driver support as an Android application. On Android, one can access to /dev/bus/usb/XXX/YYY, but not the kernel functions.
Would it be possible to source drivers/Kconfig? Or is it too much work?
Is it better to activate one section at a time?