From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hannes Reinecke Date: Tue, 14 Jun 2005 07:47:48 +0000 Subject: Re: Input sysbsystema and hotplug Message-Id: <42AE8BA4.5020702@suse.de> List-Id: References: <200506131607.51736.dtor_core@ameritech.net> <200506131705.30159.dtor_core@ameritech.net> <42AE8820.2010102@suse.de> <200506140242.08982.dtor_core@ameritech.net> In-Reply-To: <200506140242.08982.dtor_core@ameritech.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: Dmitry Torokhov Cc: linux-hotplug-devel@lists.sourceforge.net, Kay Sievers , Greg KH , Vojtech Pavlik , LKML , Andrew Morton Dmitry Torokhov wrote: > On Tuesday 14 June 2005 02:32, Hannes Reinecke wrote: >>And yes, we should break compability and come up with a clean >>implementation. >=20 > But those pesky users scream every time we break their mice ;) >=20 >>And as the original input event is an abomination I=20 >>don't see the point in keeping compability with a broken interface. >> >=20 > Why is it abomination (aside from using old mechanism to call > hotplug)? It looks like it transmits all data necessary to load > appropriate input handler... >=20 Because there are _two_ events with the name 'input'. Both run under the same name but carry different information. One is required to load the module and the other is required to create the device node. That's what I call an abomination. Cheers, Hannes --=20 Dr. Hannes Reinecke hare@suse.de SuSE Linux AG S390 & zSeries Maxfeldstra=DFe 5 +49 911 74053 688 90409 N=FCrnberg http://www.suse.de ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotp= ut a projector? How fast can you ride your desk chair down the office luge tra= ck? If you want to score the big prize, get to know the little guy. =20 Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261306AbVFNHsN (ORCPT ); Tue, 14 Jun 2005 03:48:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261311AbVFNHsM (ORCPT ); Tue, 14 Jun 2005 03:48:12 -0400 Received: from cantor2.suse.de ([195.135.220.15]:40409 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S261306AbVFNHrw (ORCPT ); Tue, 14 Jun 2005 03:47:52 -0400 Message-ID: <42AE8BA4.5020702@suse.de> Date: Tue, 14 Jun 2005 09:47:48 +0200 From: Hannes Reinecke Organization: SuSE Linux AG User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.5) Gecko/20050317 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dmitry Torokhov Cc: linux-hotplug-devel@lists.sourceforge.net, Kay Sievers , Greg KH , Vojtech Pavlik , LKML , Andrew Morton Subject: Re: Input sysbsystema and hotplug References: <200506131607.51736.dtor_core@ameritech.net> <200506131705.30159.dtor_core@ameritech.net> <42AE8820.2010102@suse.de> <200506140242.08982.dtor_core@ameritech.net> In-Reply-To: <200506140242.08982.dtor_core@ameritech.net> X-Enigmail-Version: 0.90.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Dmitry Torokhov wrote: > On Tuesday 14 June 2005 02:32, Hannes Reinecke wrote: >>And yes, we should break compability and come up with a clean >>implementation. > > But those pesky users scream every time we break their mice ;) > >>And as the original input event is an abomination I >>don't see the point in keeping compability with a broken interface. >> > > Why is it abomination (aside from using old mechanism to call > hotplug)? It looks like it transmits all data necessary to load > appropriate input handler... > Because there are _two_ events with the name 'input'. Both run under the same name but carry different information. One is required to load the module and the other is required to create the device node. That's what I call an abomination. Cheers, Hannes -- Dr. Hannes Reinecke hare@suse.de SuSE Linux AG S390 & zSeries Maxfeldstraße 5 +49 911 74053 688 90409 Nürnberg http://www.suse.de