Re: Interacting with a input kernel driver from user space

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday, November 14, 2011 03:17:17 PM Oliver Neukum wrote:
> Am Montag, 14. November 2011, 19:57:41 schrieb Dmitry Torokhov:
> > On Monday, November 14, 2011 10:24:17 AM Nuno Santos wrote:
> > > Hi,
> > > 
> > > I have defined my first attribute in the following way:
> > > 
> > > static ssize_t usbtouchscreen_update_sensibility(struct device *dev,
> > > 
> > >                                          struct device_attribute
> > >                                          *attr, const char *buf,
> > >                                          size_t count)
> > > 
> > > {
> > > 
> > >      printk(KERN_INFO "update sensibility called");
> > 
> > Updating sensibility is always a good thing but I gather you mean
> > sensitivity here...
> > 
> > BTW this should probably be a per-user setting and belong to the X
> > driver, not kernel driver. I.e. kernel streams all data and userspace
> > (X) decides what data do discard according to current user
> > preferences.
> 
> Hi,
> 
> before we define yet another interface specific to a driver, could we
> discuss whether this interface could be applicable to a wider range of
> devices?

... and whether it should be a kernel userspace at all...

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux