linux-kernel - Re: How to access correctly serial port inside module?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <46557500.3070205@gmx.de>
Date:	Thu, 24 May 2007 13:20:32 +0200
From:	"Lars K.W. Gohlke" <lkwg82@....de>
To:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
CC:	Tilman Schmidt <tilman@...p.cc>, linux-kernel@...r.kernel.org
Subject: Re: How to access correctly serial port inside module?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jan Engelhardt schrieb:
> On May 24 2007 12:45, Lars K.W. Gohlke wrote:
>
>> Date: Thu, 24 May 2007 12:45:06 +0200
>> From: Lars K.W. Gohlke <lkwg82@....de>
>> To: Jan Engelhardt <jengelh@...ux01.gwdg.de>
>> Cc: Tilman Schmidt <tilman@...p.cc>, linux-kernel@...r.kernel.org
>> Subject: Re: How to access correctly serial port inside module?
>>
>> -----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-----
>>
>
> 	Jan

for example I want to print out it with printk().

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32) - GPGrelay v0.959

iD8DBQFGVXUBAAomYJ1taN8RAix3AJ0Q8GTuMg2eJsFbD/fdQFN8SnmoqgCgrHDO
gTj9ygAshefP33OY7a3MGyk=
=Mt6g
-----END PGP SIGNATURE-----

View attachment "lkwg82.vcf" of type "text/x-vcard" (125 bytes)