From: "Lars K.W. Gohlke" <lkwg82@gmx.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Tilman Schmidt <tilman@imap.cc>, linux-kernel@vger.kernel.org
Subject: Re: How to access correctly serial port inside module?
Date: Thu, 24 May 2007 12:45:06 +0200 [thread overview]
Message-ID: <46556CB2.8010709@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0705241224510.31549@yvahk01.tjqt.qr>
[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jan Engelhardt schrieb:
> 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
date is an example
and you got it, I want to do "cat </dev/ttyS0" in-kernel.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32) - GPGrelay v0.959
iD8DBQFGVWy0AAomYJ1taN8RAu7/AJ9+1irJURFy5KFy/wzHqSXXD5sRgACfSi49
ec5AnOQoTz2nCt//siaiTNs=
=uj4G
-----END PGP SIGNATURE-----
[-- Attachment #2: lkwg82.vcf --]
[-- Type: text/x-vcard, Size: 124 bytes --]
begin:vcard
fn:Lars K.W. Gohlke
n:Gohlke;Lars K.W.
email;internet:lkwg82@gmx.de
x-mozilla-html:FALSE
version:2.1
end:vcard
next prev parent reply other threads:[~2007-05-24 10:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 13:00 How to access correctly serial port inside module? Lars K.W. Gohlke
2007-05-14 17:40 ` Lars K.W. Gohlke
2007-05-14 20:00 ` Jan Engelhardt
2007-05-14 20:25 ` Lars K.W. Gohlke
2007-05-14 23:00 ` Tilman Schmidt
2007-05-15 8:43 ` Jan Engelhardt
2007-05-22 22:17 ` Tilman Schmidt
2007-05-24 10:22 ` Lars K.W. Gohlke
2007-05-24 10:26 ` Jan Engelhardt
2007-05-24 10:45 ` Lars K.W. Gohlke [this message]
2007-05-24 10:50 ` Jan Engelhardt
2007-05-24 11:20 ` Lars K.W. Gohlke
2007-05-24 17:03 ` Tilman Schmidt
2007-05-24 17:19 ` Lars K.W. Gohlke
2007-05-24 17:29 ` Jan Engelhardt
2007-05-24 19:15 ` Lars K.W. Gohlke
2007-05-28 17:05 ` Tilman Schmidt
2007-05-28 19:03 ` Jan Engelhardt
2007-05-30 7:07 ` Lars K.W. Gohlke
2007-05-30 7:46 ` Lars K.W. Gohlke
2007-05-30 9:38 ` Tilman Schmidt
[not found] ` <851fc09e0705162315w3380ddabh9b9f0b2198cb8457@mail.gmail.com>
2007-05-22 21:55 ` Tilman Schmidt
2007-06-03 20:28 ` Lars K.W. Gohlke
2007-06-05 21:41 ` Tilman Schmidt
2007-06-06 8:27 ` Lars K.W. Gohlke
2007-06-07 22:25 ` Lars K.W. Gohlke
2007-06-08 0:27 ` Tilman Schmidt
2007-05-14 22:37 ` Tilman Schmidt
2007-05-24 10:51 ` Lars K.W. Gohlke
-- strict thread matches above, loose matches on Subject: below --
2007-06-05 7:55 Lars K.W. Gohlke
2007-06-07 22:27 Lars K.W. Gohlke
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=46556CB2.8010709@gmx.de \
--to=lkwg82@gmx.de \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--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.