From: Michael Buesch <freesoftwaredeveloper@web.de>
To: root@chaos.analogic.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: modifying line state manually on ttyS
Date: Mon, 7 Apr 2003 17:48:50 +0200 [thread overview]
Message-ID: <200304071748.50910.freesoftwaredeveloper@web.de> (raw)
In-Reply-To: <Pine.LNX.4.53.0304071139390.18753@chaos>
On Monday 07 April 2003 17:51, Richard B. Johnson wrote:
> This means that you can't control TxD directly. I suggest that
> you use the parallel printer-port. This port allows you to set
That's my problem. parallel-port is used by a printer and I don't
wanna by an expensive extension card for second parport. :)
> Now, if you really need the +/- 12 volts that you think you
> will get out of a UART, please measure it first. Many new computers
> use I/O chips that only provide +/- 5 volts! Anyway, you can use the
That's no problem, because I "down-volt" it to 4.7V before using it.
> calls. You probably want to disable the SIGHUP signal before
> you muck with those bits. Some versions of Linux will send the
> hangup signal to the TTY owner even though it's not the controlling
> terminal for the process. This could cause your program to exit
> for "unknown" reasons; signal(SIGHUP, SIG_IGN) prevents such problems.
Thanks for this important information.
Regards
Michael Buesch.
--
My homepage: http://www.8ung.at/tuxsoft
fighting for peace is like fu**ing for virginity
next prev parent reply other threads:[~2003-04-07 15:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 15:02 modifying line state manually on ttyS Michael Buesch
2003-04-07 14:16 ` Alan Cox
2003-04-07 15:42 ` Michael Buesch
2003-04-07 15:34 ` Sergei Organov
2003-04-07 16:32 ` Michael Buesch
2003-04-07 17:01 ` Sergei Organov
2003-04-07 17:16 ` Michael Buesch
2003-04-07 15:51 ` Richard B. Johnson
2003-04-07 15:48 ` Michael Buesch [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-07 16:22 Ed Vance
2003-04-07 16:48 ` Michael Buesch
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=200304071748.50910.freesoftwaredeveloper@web.de \
--to=freesoftwaredeveloper@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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