mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Michael Schmitz" <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: "Geert Uytterhoeven" <geert@linux-m68k.org>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Michael Schmitz" <schmitz@debian.org>,
	"Roman Zippel" <zippel@linux-m68k.org>
Subject: Re: [patch 04/33] m68k: Atari keyboard and mouse support.
Date: Thu, 3 May 2007 15:06:54 -0400	[thread overview]
Message-ID: <d120d5000705031206l2c675c22t5aab3eb648aa1cf8@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0705031832450.9408@xplor.biophys.uni-duesseldorf.de>

Hi Michael,

On 5/3/07, Michael Schmitz <schmitz@mail.biophys.uni-duesseldorf.de> wrote:
> >
> > > +
> > > +       if (!(atakbd_dev = input_allocate_device()))
> > > +               return -ENOMEM;
> > > +
> > > +       // need to init core driver if not already done so
> > > +       if (atari_keyb_init())
> >
> > Memory leak
>
> How so? If the core has been initialized already this will just return ...
>

You just allocated atakbd_dev. If atari_keyb_init() fails you leak it.

> > > +       for (i = 1; i < 0x72; i++) {
> > > +               atakbd_keycode[i] = i;
> > > +               set_bit(atakbd_keycode[i], atakbd_dev->keybit);
> >
> > It looks like this driver is not using standard input event codes. If
> > Roman does not want to adjust keymaps on Amiga and Atari that should
> > be handled in legacy keyboard driver (drivers/char/keyboard.c). As it
> > is programs using /dev/input/eventX have no chance of working.
>
> The translation map should not have been overwritten like above, is that
> what you mean?
> My original patch didn't have that bit; scancodes were translated to
> input keycodes using atakbd_keycode[scancode] instead. I'll have that
> reverted...
>

Does KEY_1 actually  maps to scancode 2 on atari?


Thanks,

-- 
Dmitry

  parent reply	other threads:[~2007-05-03 19:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070501195052.390551603@mail.of.borg>
     [not found] ` <20070501195129.842338339@mail.of.borg>
2007-05-01 20:46   ` Dmitry Torokhov
2007-05-03 17:07     ` Michael Schmitz
2007-05-03 17:33       ` Roman Zippel
2007-05-03 19:17         ` Dmitry Torokhov
2007-05-03 19:41           ` Roman Zippel
2007-05-03 20:32             ` Dmitry Torokhov
2007-05-03 21:01               ` Roman Zippel
2007-05-03 19:06       ` Dmitry Torokhov [this message]
2007-05-04 10:25         ` Michael Schmitz
2007-05-01 20:32 [patch 00/33] m68k patches for 2.6.22 Geert Uytterhoeven
2007-05-01 20:32 ` [patch 04/33] m68k: Atari keyboard and mouse support Geert Uytterhoeven
2007-05-01 20:57   ` Christoph Hellwig
2007-05-01 21:09     ` Dmitry Torokhov
2007-05-03 10:34       ` Michael Schmitz
2007-05-03 10:47     ` Michael Schmitz
2007-05-03 10:50       ` Christoph Hellwig
2007-05-03 10:54         ` Michael Schmitz

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=d120d5000705031206l2c675c22t5aab3eb648aa1cf8@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=schmitz@debian.org \
    --cc=schmitz@opal.biophys.uni-duesseldorf.de \
    --cc=torvalds@linux-foundation.org \
    --cc=zippel@linux-m68k.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

all inboxes | Powered by JetHome®