From: Corey Minyard <cminyard@mvista.com>
To: Tilman Schmidt <tilman@imap.cc>
Cc: Alan <alan@lxorguk.ukuu.org.uk>,
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: Mon, 11 Dec 2006 11:07:50 -0600 [thread overview]
Message-ID: <457D9066.1030308@mvista.com> (raw)
In-Reply-To: <457D8E35.9050706@imap.cc>
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. Is there
> a way for a driver to attach to a serial port through the line
> discipline interface from kernel space, eg. from an initialization,
> module load, or probe function?
>
Module initialization functions run in a task context, so that's
generally not a problem. The probe function depends on the driver,
I guess, but most I have seen are in task context.
-Corey
next prev parent reply other threads:[~2006-12-11 17:07 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 [this message]
2006-12-12 23:50 ` Tilman Schmidt
2006-12-11 17:40 ` Alan
2006-12-13 0:21 ` Tilman Schmidt
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=457D9066.1030308@mvista.com \
--to=cminyard@mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 \
--cc=tilman@imap.cc \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.