linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
	linux-input <linux-input@vger.kernel.org>,
	Jiri Slaby <jslaby@suse.cz>
Subject: Re: new modular hid?
Date: Tue, 13 Jan 2009 01:08:51 -0800	[thread overview]
Message-ID: <20090113010658.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0901130958230.5377@jikos.suse.cz>

On Tue, Jan 13, 2009 at 10:00:52AM +0100, Jiri Kosina wrote:
> On Tue, 13 Jan 2009, Jiri Kosina wrote:
> 
> > > I would agree with Michael here, it looks like we went a bit overboard 
> > > with HID quirks. I think sensible solution would be to merge quirks into 
> > > 3-4 files (one per device type) and maybe even compile keyboard quirks 
> > > into hid core.
> > It might seem a too bit too much fine-grained right now, but my 
> > longer-term plan was to have more sophisticated drivers also register 
> > themselves to the HID bus, make use of the common parser, etc (Wacom comes 
> > to mind, for example). 
> > Having the quirks grouped together rather than nicely separate would then 
> > bring us close to the previous total mess, when unrelated quirks were 
> > glued together randomly in the spaghetti-code-way, which I really would 
> > like to avoid as much as possible, it started to become unmaintainable.
> 
> That being said, we of course need to think about the initrd issue brought 
> up by Michael.
> 
> Compiling everything into single driver back again in the end would of 
> course be a solution, but I am afraid that it'd be quite difficult with 
> the bus infrastructure in place.

Not everything, just keyboards so they work even if userspace is not
quite there yet. We just need to make sure we initialize hid bus before
we register sub-drivers.

-- 
Dmitry

  reply	other threads:[~2009-01-13  9:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12 20:05 new modular hid? Michael Tokarev
2009-01-12 23:54 ` Jiri Kosina
2009-01-13  5:43   ` Dmitry Torokhov
2009-01-13  8:50     ` Jiri Kosina
2009-01-13  9:00       ` Jiri Kosina
2009-01-13  9:08         ` Dmitry Torokhov [this message]
2009-01-14 13:26         ` Michael Tokarev
2009-01-14 13:39           ` Jiri Kosina

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=20090113010658.ZZRA012@mailhub.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=jslaby@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /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).