On Sun, Apr 26, 2015 at 04:40:50PM +0200, Hans de Goede wrote: > Hi, Please always provide context in your replies so people know what you're talking about. > I've a feeling everyone in this thread is ignoring the > raspberry pi use-case. Where the board is specifically > designed for educational purposes and used with lots of > peripherals which are usually programmed from userspace > using e.g. python bindings for i2c-dev or spidev, for > such a setup we really want spidev to be loaded on the > spibus by default and we really do not have a proper > compatible for a child device. No, that's a different problem - the context you describe just happens to be your use case but it's in no way universal, there are plenty of expansion boards out there that have devices that use real drivers connected to them normally (and some of those could even be used in the educational contexts you describe). I think the underlying need here is either for a better way of registering things or better tooling around device tree overlays to address the usability issues.
Attachment:
signature.asc
Description: Digital signature
