public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor@insightbb.com>
To: "Marek Vašut" <marek.vasut@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Stowaway 2.6.17.1
Date: Sun, 6 Aug 2006 22:28:07 -0400	[thread overview]
Message-ID: <200608062228.07964.dtor@insightbb.com> (raw)
In-Reply-To: <200608052152.05840.marek.vasut@gmail.com>

On Saturday 05 August 2006 15:52, Marek Vašut wrote:
> Hi,
> this patch adds support for stowaway and stowaway compatible (eg. dicota 
> inutPDA) serial keyboards. I made it on kernel 2.6.16, but it applies cleanly 
> on 2.6.17.1 too. I tested it on palm zire71 and friend reported me that it 
> works on palm tungsten T3.
>

Hi,

Looks pretty good, I have a question though:

> +       if (data < 0x80) {
> +       /* invalid scan codes are probably the init sequence, so we ignore them */
> +           if (skbd->keycode[data & SKBD_KEY]) { 
> +                   input_regs(skbd->dev, regs);
> +                   input_report_key(skbd->dev, skbd->keycode[data & SKBD_KEY], 1);
> +                   input_sync(skbd->dev); 
> +           }
> +           else if (data == 0xe7) /* end of init sequence */
> +                   printk(KERN_INFO "input: %s on %s\n", skbd->dev->name, serio->phys);

How does "init sequence" gets here? Normally inputattach initializes
hardware and then creates proper serio port...
 
> +       err = serio_open(serio, drv);
> +       if (err)
> +               goto fail;
> +
> +       input_register_device(skbd->dev);
> +       return 0;

You need to handle errors from input_register_device() too.

-- 
Dmitry

  reply	other threads:[~2006-08-07  2:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-05 19:52 [PATCH] Stowaway 2.6.17.1 Marek Vašut
2006-08-07  2:28 ` Dmitry Torokhov [this message]
2006-08-07 18:09 ` Andrew Morton

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=200608062228.07964.dtor@insightbb.com \
    --to=dtor@insightbb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marek.vasut@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