From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264524AbUDULwc (ORCPT ); Wed, 21 Apr 2004 07:52:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264536AbUDULwb (ORCPT ); Wed, 21 Apr 2004 07:52:31 -0400 Received: from ee.oulu.fi ([130.231.61.23]:24731 "EHLO ee.oulu.fi") by vger.kernel.org with ESMTP id S264524AbUDULwa (ORCPT ); Wed, 21 Apr 2004 07:52:30 -0400 Date: Wed, 21 Apr 2004 14:52:10 +0300 (EEST) From: Tuukka Toivonen X-X-Sender: tuukkat@stekt37 To: Sau Dan Lee cc: Neil Brown , arjanv@redhat.com, Andrew Morton , b-gruber@gmx.de, linux-kernel@vger.kernel.org Subject: Re: /dev/psaux-Interface In-Reply-To: Message-ID: References: <20040419015221.07a214b8.akpm@osdl.org> <1082372020.4691.9.camel@laptop.fenrus.com> <16518.20890.380763.581386@cse.unsw.edu.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Quite heated discussion, which is why I've avoided it =) But just to clarify my intentions... Dmitry raised some valid issues about the problems in the current version of psaux driver. I might try fixing some/all of them, however I believe I got a better idea. On Wed, 21 Apr 2004, Sau Dan Lee wrote: >I second! Let's free /dev/psaux. We want the /dev/psaux as in 2.4, >2.2, 2.0, ... We don't want a faked, censored one as in 2.6.0--5. We shouldn't want _the_ /dev/psaux, but something similar, possibly better. What I'm after (and probably Sau Dan Lee too) is direct access to at least psaux-port. My idea is to modify serio to expose all (or at least all unconnected) ports into userspace, where programs can write/read them just like the /dev/psaux before. Then it's just matter of symlinking /dev/psaux into correct device. The biggest problem as I see is that this is much more intrusive change and a standalone kernel driver (as psaux.ko currently is) is impossible. I'll be back when I have some code, before that, all suggestions are welcome (special thanks for Dmitry for insights).