From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Subject: Re: [PATCH] Add the ability to layer another driver over the serial driver Date: Mon, 11 Dec 2006 17:40:04 +0000 Message-ID: <20061211174004.5605fb47@localhost.localdomain> References: <4533B8FB.5080108@mvista.com> <20061210201438.tilman@imap.cc> <457CB32A.2060804@mvista.com> <20061211102016.43e76da2@localhost.localdomain> <457D8E35.9050706@imap.cc> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from outpipe-village-512-1.bc.nu ([81.2.110.250]:41181 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1762988AbWLKRcZ (ORCPT ); Mon, 11 Dec 2006 12:32:25 -0500 In-Reply-To: <457D8E35.9050706@imap.cc> Sender: linux-serial-owner@vger.kernel.org List-Id: linux-serial@vger.kernel.org To: Tilman Schmidt Cc: Corey Minyard , Guennadi Liakhovetski , linux-serial@vger.kernel.org, Linux Kernel , Hansjoerg Lipp , Russell Doty On Mon, 11 Dec 2006 17:58:29 +0100 Tilman Schmidt wrote: > On Mon, 11 Dec 2006 10:20:16 +0000, Alan wrote: > > This looks wrong. You already have a kernel interface to serial drivers. > > It is called a line discipline. We use it for ppp, we use it for slip, we > > use it for a few other things such as attaching sync drivers to some > > devices. > > I was under the impression that line disciplines need a user space > process to open the serial device and push them onto it. Yes that is correct. You need a way for the user to tell you which port to use and to the permission and usage management for it anyway (as well as load the module and configure settings), so this seems quite reasonable.