All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Zinx Verituse <zinx@epicsol.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] cuecat serio driver for linux 2.6.0-test9
Date: Thu, 20 Nov 2003 11:32:49 +0000	[thread overview]
Message-ID: <20031120113249.A30030@infradead.org> (raw)
In-Reply-To: <20031120014514.GA4573@bliss>; from zinx@epicsol.org on Wed, Nov 19, 2003 at 07:45:14PM -0600

On Wed, Nov 19, 2003 at 07:45:14PM -0600, Zinx Verituse wrote:
> Well, my cuecat driver is ready for testing.
> 
> http://zinx.xmms.org/cuecat/cuecat-2.6-0.0.2.tar.gz
> 
> It does not use the same output format as the driver floating around
> for 2.2.x/2.4.x kernels.
> 
> It currently requires a patch which changes the order serio drivers
> are searched in (the newest driver is searched first now), and adds
> a function to walk through the serio port list.
> 
> I'm hoping the patch will be included in to the kernel at some point
> in time -- It's available separately at:
> 	http://zinx.xmms.org/cuecat/linux-2.6.0-test9-serio.diff
> 
> The driver has some pitfalls, such as standing between -all- serio
> devices capable of supporting a cuecat, and not just the ones with
> a cuecat on them (And it has no way to specify which ports to use),
> but hopefully I'll think of a good way to fix that before 0.0.3.
> 
> The major number is dynamicly allocated -- If you aren't using devfs,
> check /proc/devices.
> The minor number for reading all cuecats is 0, and the minor number
> for individual cuecats is their [driver-assigned] index plus 1.
> Recommended names are:
> 	/dev/cuecat/cuecats
> 	/dev/cuecat/0
> 	/dev/cuecat/1
> and so on.

Hmm?  A 2.6 input driver shouldn't create devices bz itself but rather use
the input core to communicated with the upper drivers like evdev or moused..


  reply	other threads:[~2003-11-20 11:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20  1:45 [ANNOUNCE] cuecat serio driver for linux 2.6.0-test9 Zinx Verituse
2003-11-20 11:32 ` Christoph Hellwig [this message]
2003-11-20 19:20   ` Zinx Verituse

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=20031120113249.A30030@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zinx@epicsol.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.