[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <457F402F.2050901@imap.cc>
Date: Wed, 13 Dec 2006 00:50:07 +0100
From: Tilman Schmidt <tilman@...p.cc>
To: Corey Minyard <cminyard@...sta.com>
CC: Alan <alan@...rguk.ukuu.org.uk>,
Guennadi Liakhovetski <g.liakhovetski@....de>,
linux-serial@...r.kernel.org,
Linux Kernel <linux-kernel@...r.kernel.org>,
Hansjoerg Lipp <hjlipp@....de>, Russell Doty <rdoty@...hat.com>
Subject: Re: [PATCH] Add the ability to layer another driver over the serial
driver
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@...p.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
Download attachment "signature.asc" of type "application/pgp-signature" (254 bytes)
Powered by blists - more mailing lists