From: "Xing Wei" <weixing@hanwang.com.cn>
To: "dmitry.torokhov" <dmitry.torokhov@gmail.com>
Cc: "linux-input" <linux-input@vger.kernel.org>,
"linux-kernel" <linux-kernel@vger.kernel.org>,
"jkosina" <jkosina@suse.cz>
Subject: Re: [PATCH v3] input: Add support for Hanwang tablet
Date: Thu, 2 Sep 2010 12:29:50 +0800 [thread overview]
Message-ID: <201009021229501252232@hanwang.com.cn> (raw)
On Wed, Sep 01, 2010 mitry Torokhov wrote:
> Hi Xing,
>
> On Wed, Sep 01, 2010 at 02:55:44PM +0800, Xing Wei wrote:
> > Hi Dmitry, it works well and I really appreciate your work.
> > BTN_3 - BTN_8 & ABS_DISTANCE events are not handled & used in our X system driver by now,
> > sorry for my mistake.
> >
>
> Just to avoid confusion - are BTN_3 - BTN_8 not used by your X driver or
> the hardware does not really report them? Because if it the former then
> we should continue reporting them - some other user (as in
> program/driver) might be interested in these.
>
> Also, why do you develop your own X driver? Does not X's evdev driver
> work properly for you?
>
> Thanks.
>
>
Hi Dmitry, the hardware does really report BTN_3 - BTN_8.
And I try to let the evdev driver(remove my X driver & .conf file ) take over the device,
but seem like it has no reflection to the pressure and roll wheel pad,just run like a generic mouse.
Our products are just used under Windows and Mac before,
really new to kernel-input and X system,correct me if something wrong.
Thanks.
next reply other threads:[~2010-09-02 4:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 4:29 Xing Wei [this message]
2010-09-02 6:20 ` [PATCH v3] input: Add support for Hanwang tablet Dmitry Torokhov
2010-09-02 6:24 ` Dmitry Torokhov
2010-09-02 6:30 ` Peter Hutterer
-- strict thread matches above, loose matches on Subject: below --
2010-09-01 6:55 Xing Wei
2010-09-02 0:28 ` Dmitry Torokhov
2010-08-31 8:14 Xing Wei
2010-09-01 2:02 ` 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=201009021229501252232@hanwang.com.cn \
--to=weixing@hanwang.com.cn \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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