[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.61.0705241224510.31549@yvahk01.tjqt.qr>
Date: Thu, 24 May 2007 12:26:44 +0200 (MEST)
From: Jan Engelhardt <jengelh@...ux01.gwdg.de>
To: "Lars K.W. Gohlke" <lkwg82@....de>
cc: Tilman Schmidt <tilman@...p.cc>, linux-kernel@...r.kernel.org
Subject: Re: How to access correctly serial port inside module?
On May 24 2007 12:22, Lars K.W. Gohlke wrote:
>
> ok, I have read everything and also have read the chapters about
> tty_drivers. However I'm not really understand, how to ... .
>
> I will summarize the concrete scenario, which will lead to the
> understanding and further solution of deadling with serial driver.
>
> [scenario]
>
> 1. in userspace I'm doing: > date > /dev/ttyS0
> 2. in kernelspace I want to print out this date.
>
> [/scenario]
>
> I'm really new to kernel coding, that's why I maybe understand some
> functions not the proper way.
>
> I'm a bit confused.
So am I. Usually, you connect two different machines with a serial cable.
(Leaving out the special case of connecting ttyS0-ttyS1 on the same machine.)
This poses the first question: whose kernelspace? the sender or
the receiver side? And by "this date" do you perhaps mean
"whatever was sent", or specifically a date? And print to _where_?
Up to now, it looks like you want to do "cat </dev/ttyS0" in-kernel.
Jan
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists