linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Hutterer <peter.hutterer@who-t.net>
To: Nikolai Kondrashov <spbnick@gmail.com>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Jiri Kosina <jkosina@suse.cz>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	DIGImend-devel <DIGImend-devel@lists.sourceforge.net>
Subject: Re: [PATCH 0/2] HID: huion: add libinput support
Date: Wed, 25 Feb 2015 07:45:48 +1000	[thread overview]
Message-ID: <20150224214548.GA6969@jelly.redhat.com> (raw)
In-Reply-To: <54EC5EFD.5040505@gmail.com>

On Tue, Feb 24, 2015 at 01:22:37PM +0200, Nikolai Kondrashov wrote:
> On 02/24/2015 12:34 AM, Benjamin Tissoires wrote:
> >On Feb 23 2015 or thereabouts, Peter Hutterer wrote:
> >>yeah, but the thing is: those emails are only necessary _once_  per tablet.
> >>if they're not in the database, you'll get those questions for the lifetime
> >>of the tablet :)
> >>
> >>Also note that libwacom_new_from_path() has a fallback option, you can get a
> >>generic tablet from it and then proceed as normal. gnome-settings-daemon
> >>already uses this.
> >>
> >
> >I also expects that the settings configuration tool under wayland will
> >rely on the actual capability of the devices. This way, even if the
> >tablet is not registered in libwacom, we will still be able to show a
> >default configuration UI.
> >
> >I really believe the registering in libwacom will be just to have a
> >prettier interface, not a requirement.
> 
> Well, that sounds awesome! Just what I was looking for :)
> 
> What about X.org though? Last time I tried I couldn't configure a
> Wacom-handled Huion with the Gnome applet.

hard to say, settings-daemon/control-center use the xorg wacom driver
properties, so in theory it should work. Best to file a gnome bug for it
and CC me on it, there's no obvious definitive answer I can think of right
now.

Cheers,
   Peter

  reply	other threads:[~2015-02-24 21:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 22:54 [PATCH 0/2] HID: huion: add libinput support Benjamin Tissoires
2015-02-17 22:54 ` [PATCH 1/2] HID: huion: enable button mode reporting Benjamin Tissoires
2015-02-18 10:11   ` Nikolai Kondrashov
2015-02-18 20:24     ` Benjamin Tissoires
2015-02-19 11:37       ` Nikolai Kondrashov
2015-02-18 12:17   ` Nikolai Kondrashov
2015-02-18 20:25     ` Benjamin Tissoires
2015-02-17 22:54 ` [PATCH 2/2] HID: huion: split the stylus and pad in 2 nodes Benjamin Tissoires
2015-02-18 10:17   ` Nikolai Kondrashov
2015-02-18  9:25 ` [PATCH 0/2] HID: huion: add libinput support Nikolai Kondrashov
2015-02-18 20:04   ` Benjamin Tissoires
2015-02-19 11:54     ` Nikolai Kondrashov
2015-02-20  5:34       ` Peter Hutterer
2015-02-22 12:33         ` Nikolai Kondrashov
2015-02-22 23:28           ` Peter Hutterer
2015-02-23 22:34             ` Benjamin Tissoires
2015-02-24 11:22               ` Nikolai Kondrashov
2015-02-24 21:45                 ` Peter Hutterer [this message]
2015-02-23 22:44       ` Benjamin Tissoires
2015-02-24 11:27         ` Nikolai Kondrashov

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=20150224214548.GA6969@jelly.redhat.com \
    --to=peter.hutterer@who-t.net \
    --cc=DIGImend-devel@lists.sourceforge.net \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spbnick@gmail.com \
    /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).