public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Corey Minyard <cminyard@mvista.com>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	linux-serial@vger.kernel.org,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Hansjoerg Lipp <hjlipp@web.de>, Russell Doty <rdoty@redhat.com>
Subject: Re: [PATCH] Add the ability to layer another driver over the serial driver
Date: Wed, 13 Dec 2006 01:21:32 +0100	[thread overview]
Message-ID: <457F478C.2010702@imap.cc> (raw)
In-Reply-To: <20061211174004.5605fb47@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]

Am 11.12.2006 18:40 schrieb Alan:
> On Mon, 11 Dec 2006 17:58:29 +0100
> Tilman Schmidt <tilman@imap.cc> 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.

I'm afraid I'm not familiar with Linux' SLIP implementation.
So there's a line discipline called "slip" which, when pushed
onto a serial port, registers as a network device, right? How
does it get - and stay - pushed? Is there a daemon process which
opens the serial port, pushes the line discipline onto it, and
then just sleeps, keeping the serial port open so that the line
discipline stays put? Can you point me to the source for such a
daemon for reference?

What I am actually looking for is a way to port an existing driver
which directly programs an i8250 serial port, to cooperate more
cleanly with the existing serial port drivers of Linux (and, at
the same time, shed the dependency on the specific serial port
hardware.) If that requires a permanently running (or sleeping)
userspace daemon, then so be it. (Although I admit I'd rather do
without.)

Thanks
Tilman

-- 
Tilman Schmidt                          E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]

  reply	other threads:[~2006-12-13  0:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-16 16:53 [PATCH] Add the ability to layer another driver over the serial driver Corey Minyard
2006-12-10 19:19 ` Tilman Schmidt
2006-12-10 20:21   ` Guennadi Liakhovetski
2006-12-11  1:23     ` Corey Minyard
2006-12-11 10:20       ` Alan
2006-12-11 14:52         ` Corey Minyard
2006-12-11 15:19           ` Alan
2006-12-11 16:29             ` Corey Minyard
2006-12-11 17:15               ` Alan
2006-12-11 17:22                 ` Corey Minyard
2006-12-19 19:27             ` Corey Minyard
2006-12-11 16:58         ` Tilman Schmidt
2006-12-11 17:07           ` Corey Minyard
2006-12-12 23:50             ` Tilman Schmidt
2006-12-11 17:40           ` Alan
2006-12-13  0:21             ` Tilman Schmidt [this message]
2006-12-11 19:01         ` Guennadi Liakhovetski
2006-12-11 19:15           ` Alan
2006-12-11 20:16             ` Guennadi Liakhovetski

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=457F478C.2010702@imap.cc \
    --to=tilman@imap.cc \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cminyard@mvista.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=hjlipp@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=rdoty@redhat.com \
    /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