Am Donnerstag, den 20.05.2021, 15:31 +0200 schrieb Johan Hovold: Hi, > Isn't that already handled by lircd using uinput? The problem with that reasoning, though it is true, is 1) We would need to remove a lot of subsystems if we took that to the logical conclusion. 2) It makes runtime PM much harder 3) We end up with two classes of LIRC devices > I hear you, but we still need to have those discussions from time to > time to make sure our architecture is sane. One of the problems today > with the kernel development process appears to be that too few > questions > are asked. If it builds, ship it... Indeed, so, could we force a line discipline on a device on the kernel level? Code duplication is bad. > But I think I've got that point across by now. Yes and and we need to think about the conclusion we draw from that point. It seems to me that an architecture that pushes data through the whole tty layer into a demon, then through uinput is definitely not elegant. So what else can we do, so that devices that are internally a serial chip plus additional stuff but externally unrelated devices? It looks to me we are in need of creativity beyond two options here. Regards Oliver
