From: "Lars K.W. Gohlke" <lkwg82@gmx.de>
To: Tilman Schmidt <tilman@imap.cc>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>, linux-kernel@vger.kernel.org
Subject: Re: How to access correctly serial port inside module?
Date: Thu, 24 May 2007 19:19:57 +0200 [thread overview]
Message-ID: <4655C93D.40005@gmx.de> (raw)
In-Reply-To: <4655C554.7030000@imap.cc>
[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tilman Schmidt schrieb:
> Am 24.05.2007 12:22 schrieb Lars K.W. Gohlke:
>> 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 must admit that now I do not understand anything anymore.
> I thought you wanted to receive some data over an RS232 serial
> port and process it in your kernel module, but this doesn't
> look like that at all.
>
> So what is it you are trying to do?
> Do you just want to write something to a file in userspace and
> receive it in your kernel module?
I want to read from serial port (I mean the port, which is called
/dev/ttyS0 in user-space). Then I want copy_to_user() it through
/proc/serialPort
This is just to get familiar with driver programming (in kernelspace),
it could be better done in userspace - I know. But this is for learning.
It is a kind of synthetic problem, but after this, I hope too know how
to handle further ones.
Understood? It is a little bit strange, but hope it is explained well. ;)
If tell me that for /dev/ttyS0 I can adept it to /dev/ttyS1 etc..
thx
>
> Regards,
> Tilman
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32) - GPGrelay v0.959
iD8DBQFGVck/AAomYJ1taN8RAiYwAJ96kYK6byxHea5MhvO0zaEB1yAXQQCdGS9c
PFU39kx+d/xgj9QxusfEplc=
=OeRZ
-----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 17:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 13:00 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
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 [this message]
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
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=4655C93D.40005@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome