DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=date:from:to:cc:subject:message-id:references:mime-version
         :content-type:content-disposition:in-reply-to:user-agent;
        b=i2i8iRVWInpgxl9iLUAkCqqjCfzfpBl8+RXd0Jfd4kCr6t4w9BH57meL3/1btVWbPN
         INXJcKynA79IFG0Wh+ej/OpBlMawUiKQl2M9vgdRPNsmfUElrlWL85WhOiLr2IHAdYJ4
         9QskWdkiGbt3yCbvhqXLvrHpxdgvOS5YApBv8=
Date: Wed, 30 Mar 2011 22:25:26 -0700
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Peter Hutterer <peter.hutterer@who-t.net>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uinput: Allow for 0/0 min/max on absolute axes.
Message-ID: <20110331052526.GA31630@core.coreip.homeip.net>
References: <20110331050503.GA9318@barra.bne.redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110331050503.GA9318@barra.bne.redhat.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 751
Lines: 21

On Thu, Mar 31, 2011 at 03:05:03PM +1000, Peter Hutterer wrote:
> Some devices provide absolute axes with min/max of 0/0 (e.g. wacom's
> ABS_MISC axis). Current uinput restrictions do not allow duplication of
> these devices and require hacks in userspace to work around this.
> 
> If the kernel accepts physical devices with a min/max of 0/0, uinput
> shouldn't disallow the same range.
> 

Right, we should treat 0/0 as unlimited, or not specified, not
applicable.

Applied, thank you Peter.

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/