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: <Pine.LNX.4.61.0705282036030.11140@yvahk01.tjqt.qr>
Date:	Mon, 28 May 2007 21:03:00 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Tilman Schmidt <tilman@...p.cc>
cc:	"Lars K.W. Gohlke" <lkwg82@....de>, linux-kernel@...r.kernel.org
Subject: Re: How to access correctly serial port inside module?

On May 28 2007 19:05, Tilman Schmidt wrote:
>Am 24.05.2007 21:15 schrieb Lars K.W. Gohlke:
>> Jan Engelhardt schrieb:
>[code proposal]
>>> [I've warned about it... ;-) ]
>> 
>> is it the way to access from kernelspace the userspace fs?
>> the not-correct-way?
>
>Yes, indeed.
>
>> If it is so, I will wait for another solution ;)
>
>I'm not sure waiting will help. The roasted pigeons will not come
>flying into your mouth.
>
>The possible solutions have been sketched out for you:
>
>a) open the device file from the kernel (described by Jan):
>   actively discouraged by the kernelnewbies.org FAQ document,
>   and probably won't even work IMHO

It does work. "It just needs work." :)
See https://dev.computergmbh.de/svn/quad_dsp/trunk/ for an example.

	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/