From: Tilman Schmidt <tilman@imap.cc>
To: Corey Minyard <cminyard@mvista.com>
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: Wed, 13 Dec 2006 00:50:07 +0100 [thread overview]
Message-ID: <457F402F.2050901@imap.cc> (raw)
In-Reply-To: <457D9066.1030308@mvista.com>
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
Am 11.12.2006 18:07 schrieb Corey Minyard:
> Tilman Schmidt wrote:
>> 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.
Could you be a bit more specific? If I write a module implementing a
line discipline, how would I go about having that line discipline
push itself onto a given serial port (specified for example through a
module parameter) immediately, during its own module initialization?
I can't seem to find an in-kernel interface for that.
Also, if I understand correctly, this would only work if the driver
is compiled as a module, but such a limitation seems to be frowned
upon within the kernel community. Any way around that?
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 --]
next prev parent reply other threads:[~2006-12-13 0:22 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 [this message]
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=457F402F.2050901@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