Andy Walls <awalls@xxxxxxxxx> writes: > Nonetheless I'd still rather debug a problem with a dead process in > userspace than an oops or panic (not that an end user cares) and avoid > the risk of filesystem corruption. I'll concentrate on IRQ-driven space/mark drivers/devices since it's what I've been using. They are: very simple hardware (as simple as a TSOP1836 3-pin receiver "chip" + a resistor), very simple driver (the hardware signals change in input state with IRQ). Something like maybe 50 lines of code + the (default) key mapping table. Anyway, you can't move the whole driver to userspace, as it has to handle IRQs with timestamps. It doesn't have to sleep. It's about the last thing I'd worry about WRT the stability. > So are we optimizing for the embedded/STB and HTPC with no keyboard use > case, or the desktop or HTPC with a keyboard for maintencance? IOW the question is: do we want to continue supporting keyboard-less machines? -- Krzysztof Halasa -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
