From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263944AbUE3P6G (ORCPT ); Sun, 30 May 2004 11:58:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263975AbUE3P6G (ORCPT ); Sun, 30 May 2004 11:58:06 -0400 Received: from twilight.ucw.cz ([81.30.235.3]:5760 "EHLO midnight.ucw.cz") by vger.kernel.org with ESMTP id S263944AbUE3P57 (ORCPT ); Sun, 30 May 2004 11:57:59 -0400 Date: Sun, 30 May 2004 17:58:21 +0200 From: Vojtech Pavlik To: Dmitry Torokhov Cc: linux-kernel@vger.kernel.org, Sau Dan Lee , tuukkat@ee.oulu.fi Subject: Re: SERIO_USERDEV patch for 2.6 Message-ID: <20040530155821.GC1479@ucw.cz> References: <20040530134246.GA1828@ucw.cz> <200405301009.21202.dtor_core@ameritech.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200405301009.21202.dtor_core@ameritech.net> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sun, May 30, 2004 at 10:09:18AM -0500, Dmitry Torokhov wrote: > On Sunday 30 May 2004 08:42 am, Vojtech Pavlik wrote: > > > > Anyway, looking at the patch, it's not bad, and it's quite close to what > > I was considering to write. I'd like to keep it separate from the > > serio.c file, although it's obvious it'll require to be linked to it > > statically, because it needs hooks there - it cannot be a regular serio > > driver. > > > > Do we really have to have this stuff directly in serio? How about being able > to mark some serio ports as working in raw mode (i8042.raw=0,1,1,0) and have > separate (serio_raw?) module bind to such ports We don't have to. But it'd be rather convenient to have it. It would work for all serio ports, not just i8042, etc, etc. And if kept in a separate file (serio-dev.c), it wouldn't mess up things too much. -- Vojtech Pavlik SuSE Labs, SuSE CR