On Mon, 7 Jan 2013 18:40:22 +0100, Thomas Petazzoni wrote: > > > Not having a kernel driver means that gazillions of applications > > > re-invent the same piece of code over and over again, have to hardcode > > > the GPIO numbers for a given piece of hardware, while the kernel > > > abstract all of this very nicely. > > > > That sounds like a wonderful use of a userspace library to do this > > properly. Much like libusb does, right? > > > > I still think as this can be done in userspace, it probably should be. > > Understood. Patches discarded.
Thinking more about this. How would your userspace library know on which GPIOs your 7-seg segment device is connected? Should it parse the Device Tree from userspace? Given by the user-space application who would have to hardcode the GPIO numbers, completely defeating the hardware abstraction layer that the kernel intends to be? Thanks, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com _______________________________________________ devicetree-discuss mailing list [email protected] https://lists.ozlabs.org/listinfo/devicetree-discuss
