public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: John Appleby <john@dnsworld.co.uk>
Cc: John Appleby <johna@unickz.com>, linux-kernel@vger.kernel.org
Subject: Re: Serio keyboard issues 2.5.70
Date: Wed, 4 Jun 2003 23:47:32 +0100	[thread overview]
Message-ID: <20030604234732.E22460@flint.arm.linux.org.uk> (raw)
In-Reply-To: <434747C01D5AC443809D5FC540501131569A@bobcat.unickz.com>; from john@dnsworld.co.uk on Wed, Jun 04, 2003 at 11:44:17PM +0100

On Wed, Jun 04, 2003 at 11:44:17PM +0100, John Appleby wrote:
> 
> > > and I get nothing past "add_tail". I'd expect it to recognize my dev
> and
> > > attempt to connect to it.
> > 
> > Do you drop out the bottom of the function?  If you have no hardware
> ports
> > registered, I'd expect this to be the case.
> 
> Yeah; I thought though what I was doing was registering the port.
> 
> I'm clearly missing something really obvious here. Are you saying that I
> should have registered the port somewhere else?
> 
> Sorry for the dumb questions but there's no serio documentation yet hit
> the tree, I presume as it's pretty new for non-USB devices.

You need to register:

- serio device drivers (the things which drive the hardware) using
  serio_register_port()
- serio protocol drivers (the things which interpret the bytes,
  like atkbd.c) using serio_register_device()

So, for a PS/2 keyboard connected to a some special hardware interface,
you'd use atkbd.c which registers itself with serio using
serio_register_device().  Your device driver for the "special hardware"
registers itself with serio_register_port().

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2003-06-04 22:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <434747C01D5AC443809D5FC5405011310970EA@bobcat.unickz.com>
2003-06-04 22:44 ` Serio keyboard issues 2.5.70 John Appleby
2003-06-04 22:47   ` Russell King [this message]
2003-06-04 22:59 Perez-Gonzalez, Inaky
2003-06-04 23:03 ` Russell King
     [not found] <434747C01D5AC443809D5FC54050113109709D@bobcat.unickz.com>
2003-06-04 20:08 ` John Appleby
  -- strict thread matches above, loose matches on Subject: below --
2003-06-04 19:51 Perez-Gonzalez, Inaky
     [not found] <434747C01D5AC443809D5FC540501131097083@bobcat.unickz.com>
2003-06-04 19:23 ` John Appleby
2003-06-04 22:23   ` Russell King

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=20030604234732.E22460@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=john@dnsworld.co.uk \
    --cc=johna@unickz.com \
    --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