public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: matthieu castet <castet.matthieu@free.fr>
Cc: linux-kernel@vger.kernel.org, Adam Belay <ambx1@neo.rr.com>,
	bjorn.helgaas@hp.com, Dmitry Torokhov <dtor_core@ameritech.net>
Subject: Re: [PATCH] PNP support for i8042 driver
Date: Fri, 4 Feb 2005 19:28:16 +0100	[thread overview]
Message-ID: <20050204182816.GA3573@ucw.cz> (raw)
In-Reply-To: <4203B2D9.7080904@free.fr>

On Fri, Feb 04, 2005 at 06:37:29PM +0100, matthieu castet wrote:
> Hi,
> 
> Vojtech Pavlik wrote:
> >On Sat, Nov 13, 2004 at 02:23:53PM +0100, matthieu castet wrote:
> >
> >>Hi,
> >>this patch add PNP support for the i8042 driver in 2.6.10-rc1-mm5. Acpi 
> >>is try before the pnp driver so if you don't disable ACPI or apply 
> >>others pnpacpi patches, it won't change anything.
> >>
> >>Please review it and apply if possible
> >
> >
> >Ok, my thoughts on this:
> >
> >	It's OK to keep the device allocated to this driver via the PnP
> >        subsystem, and not bother with releasing the code via
> >	__initcall.
> >
> >	I agree that if there is a way to enumerate the device, (like
> >	PnP, ACPI or OpenFirmware), we should use that instead of
> >	probing and using a platform device for the controller.
> >
> >	I think that we should drop the ACPI support from i8042, in
> >	favor of pnpacpi, because PnP is more generic and if the
> > 	keyboard device was listed in PnPBIOS instead of ACPI, it'll
> >	still work.
> >
> Any news about this ?
 
Sort of fell off my radar, can you resend?

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2005-02-04 18:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-13 13:23 [PATCH] PNP support for i8042 driver matthieu castet
2004-11-14  6:48 ` Dmitry Torokhov
2004-11-14 12:22   ` matthieu castet
2004-11-15 14:41     ` Dmitry Torokhov
2004-11-15 19:51       ` matthieu castet
2004-11-15 20:28         ` Dmitry Torokhov
2004-11-15 22:52           ` matthieu castet
2004-11-15 23:09             ` matthieu castet
2004-11-16  5:52             ` Adam Belay
2004-11-16  6:27             ` Dmitry Torokhov
2004-11-16  5:37   ` Adam Belay
2004-11-16  5:44     ` Greg KH
2004-11-16  6:06     ` Dmitry Torokhov
2004-11-16  6:24       ` Adam Belay
2004-11-17 10:07 ` Vojtech Pavlik
2005-02-04 17:37   ` matthieu castet
2005-02-04 18:28     ` Vojtech Pavlik [this message]
2005-02-04 22:54       ` matthieu castet
2005-02-05 13:48       ` matthieu castet
2005-02-05 18:51         ` Dmitry Torokhov

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=20050204182816.GA3573@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=ambx1@neo.rr.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=castet.matthieu@free.fr \
    --cc=dtor_core@ameritech.net \
    --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