Hi On Tue, Sep 2, 2014 at 2:43 PM, Hans de Goede <[email protected]> wrote: > Hi, > > It is useful for userspace to know that they're not dealing with a regular > mouse but rather with a pointing stick (e.g. a trackpoint) so that userspace > can e.g. automatically enable middle button scrollwheel emulation. > > It is impossible to tell the difference from the evdev info without resorting > to putting a list of device / driver names in userspace, this is undesirable.
..so it is better to put that table into the kernel? I thought the plan was to avoid putting more hardware tables into the kernel. All those tables are always loaded into RAM, whereas solutions like udev hwdb can provide the exact same features in user-space but avoid loading it into RAM, except if used. hwdb is pretty nice to store information about hardware. It is not meant for configuration or volatile data, but rather as read-only lookup table for hardware information. You could easily extend the hwdb with a trackpoint variable that marks specific devices as trackpoints. Anyhow, if you guys want it in the kernel, go ahead. I just don't see the advantage of having it in kernel-space. Thanks David -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
