All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Douglas Gilbert <dougg@torque.net>, linux-kernel@vger.kernel.org
Subject: Re: dead keyboard in lk 2.5.25
Date: Sun, 7 Jul 2002 23:26:23 +0200	[thread overview]
Message-ID: <20020707232623.A10762@ucw.cz> (raw)
In-Reply-To: <20020707164554.B15933@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Sun, Jul 07, 2002 at 04:45:54PM +0100

On Sun, Jul 07, 2002 at 04:45:54PM +0100, Russell King wrote:
> On Sun, Jul 07, 2002 at 10:20:16AM -0400, Douglas Gilbert wrote:
> > --- linux/drivers/input/serio/i8042.c	Sat Jul  6 08:57:35 2002
> > +++ linux/drivers/input/serio/i8042.c2525fix	Sun Jul  7 09:52:50 2002
> > @@ -269,8 +269,11 @@
> >   */
> >  
> >  	if (request_irq(values->irq, i8042_interrupt, 0, "i8042", NULL)) {
> > -		printk(KERN_ERR "i8042.c: Can't get irq %d for %s\n", values->irq, values->name);
> > -		return -1;
> > +		free_irq(values->irq, NULL);
> > +		if (request_irq(values->irq, i8042_interrupt, 0, "i8042", NULL)) {
> > +			printk(KERN_ERR "i8042.c: Can't get irq %d for %s\n", values->irq, values->name);
> > +			return -1;
> > +		}
> >  	}
> >  
> >  /*
> 
> Hmm, interesting concept.  "If someone else is using my resource, I'll
> free it for them, and re-claim it".  It sounds very much like a hack
> rather than a fix to me.
> 
> I'd guess the real solution would be to stop pc_keyb being initialised
> when you're trying to use i8042.c.  Vojtech?

The real solution is to delete pc_keyb.c. But that'll take some time
yet. i8042.c is there so that the build problems, and other obvious
stuff gets fixed. Later we can start actually using it.

-- 
Vojtech Pavlik
SuSE Labs

      reply	other threads:[~2002-07-07 21:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-07 14:20 dead keyboard in lk 2.5.25 Douglas Gilbert
2002-07-07 15:45 ` Russell King
2002-07-07 21:26   ` Vojtech Pavlik [this message]

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=20020707232623.A10762@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=dougg@torque.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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.