linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Xing Wei <weixing@hanwang.com.cn>
Cc: jkosina <jkosina@suse.cz>,
	linux-input <linux-input@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] input: Add support for Hanwang tablet
Date: Mon, 30 Aug 2010 09:34:46 -0700	[thread overview]
Message-ID: <20100830163446.GB17325@core.coreip.homeip.net> (raw)
In-Reply-To: <201008302133119064558@hanwang.com.cn>

On Mon, Aug 30, 2010 at 09:33:12PM +0800, Xing Wei wrote:
> On Mon, 30 Aug 2010, Jiri Kosina Wrote: 
> > > On Mon, 30 Aug 2010, Xing Wei wrote:
> > >  
> > > +config TABLET_USB_HANWANG
> > > +	tristate "Hanwang Art Master III tablet support (USB)"
> > > +	depends on USB_ARCH_HAS_HCD
> > > +	select USB
> > > +	help
> > > +	  Say Y here if you want to use the USB version of the Hanwang Art
> > > +	  Master III tablet.  Make sure to say Y to "Mouse support"
> > > +	  (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
> > > +	  (CONFIG_INPUT_EVDEV) as well.
> > 
> > Is there any reason why you don't have these (MOUSEDEV and EVDEV) as 
> > explicit Kconfig dependencies?
> > 
> > Thanks,
> > 
> 
> I just reference the other USB tablet on this Kconfig,like aiptek,acecad,wacom.
> Actually it depends on EVDEV at least now.
> I can submit another patch if necessarry.
> 

Actually I think we should just drop references to particular input
handlers in the Kconfig as, strictly speaking, the driver does not
depend on either of them.

The text in other tablets came from time when whole input layer was a
novelty and nobody was sure what should be enabled. Nowadays every
distribution (I hope) has evdev enabled as it becomes main interface
between X and kernel and the legacy mouse and keyboard interfaces
(MOUSEDEV) are fading away.

While we are talking about the patch - I am usually OK with extending past
80 column limit, but some of the lines are pretty excessive. I'd prefer
not going above 95-100 unless it is a message string - we do not want to
break those.

Thanks.

-- 
Dmitry

  reply	other threads:[~2010-08-30 16:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30 13:33 [PATCH v2] input: Add support for Hanwang tablet Xing Wei
2010-08-30 16:34 ` Dmitry Torokhov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-08-30 11:03 Xing Wei
2010-08-30 12:12 ` Jiri Kosina
2010-08-30 14:55 ` Dmitry Torokhov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100830163446.GB17325@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=weixing@hanwang.com.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).