> > There is lots of stuff we probe and bind via user space - most things > > these days in fact. That's much of why we have notifiers and udev. It's > > frequently a win in flexibility, security and configurability to do stuff > > via user daemons. We do it for example with all the volume management, > > raid and disk encryption. > > Because volumes are something users really want to configure. They > can change their hardware configuration every now and then. And > there are removable media to be considered. Like USB bluetooth dongles, like systems with external SPI ports, or plug in SPI devices, or plug in gps devices on other interfaces ? > In our UART cases the underlaying hardware can't be reconfigured. So > there is no need to load this burden of config to the user. Plenty of uarts it can be or the BT can be muxed with other device endpoints. > For BT or GPS I just want it to work the same on all devices (independently > on how the specific chip is connected). Kernel should unify such things. > Or it would not be a Un(iplexed)ix. I think you are confusing Unix and Multics. Unix is nothing to do with Linux and Unix was about creating a beautiful system not by having a huge crap filled kernel, but by having only the minimum necessary in the kernel. Unix was not about what was put in but what was left out. "We used to sit around in the Unix Room saying, 'What can we throw out? Why is there this option?" - Doug McIlroy GPS is a train wreck for commonality. Most GPS requires custom binary only user space code often obfuscated in order to meet the regulations governing GPS technology to stop third parties using it for missile guidance. Alan -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
