linux-assembly.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: linuxassembly@evobsyniva.com
To: linux-assembly@vger.kernel.org
Subject: Re: Keyboard and Mouse library
Date: Thu, 17 Jul 2003 15:26:53 -0400	[thread overview]
Message-ID: <oprsgyy3sclmcbdf@smtp-server.woh.rr.com> (raw)
In-Reply-To: <3F16D2B1.129DF50B@wp.pl>

On Thu, 17 Jul 2003 18:45:37 +0200, Maciej Hrebien <m_hrebien@wp.pl> wrote:

>> Doing an strace on stty reveals that it calls two mystery ioctls 0x5401 
>> and
>> 0x5403, and looking around the kernel source I figured out they are 
>> TCGETS
>> and TCSETSW, however I've been unsuccessful in tracking down any more
>> information than that.  The two ioctls lead to drivers/char/tty_ioctl.c,
>> which calls a function set_termios, which calls change_termios, which 
>> calls
>> ???.set_termios, and that's about where my ability to read C code comes 
>> to
>> an end.
>
> I don't know if i understand you right, but if want to switch off line
> buffering on terminal see man 3 termios routines or do ioctl on stdin.
> TCGETS gets the current termios structure, TCSETS sets. You modify
> c_*flag(s) and here you are. I also think c_lflag&=~ICANON may be
> usefull for you in this case. Is this what you wanted?

That's it.  I knew it was an ioctl, and that it was TCSETS, but I couldn't 
find that sturcture anywhere.  I just didn't know it was called termios, 
and so I didn't know what to look up in man.  

  reply	other threads:[~2003-07-17 19:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15 13:19 Q: -fpic and $_GLOBAL_OFFSET_TABLE_ Oleg Nesterov
2003-07-15 23:24 ` hp
2003-07-16 10:03 ` Keyboard and Mouse library jeff
2003-07-15 19:54   ` Luciano Miguel Ferreira Rocha
2003-07-15 23:15   ` hp
2003-07-16  6:49     ` hp
2003-07-17  7:17     ` jeff
2003-07-16  3:09   ` linuxassembly
2003-07-16  6:46     ` hp
2003-07-16  8:07       ` linuxassembly
2003-07-17 16:45         ` Maciej Hrebien
2003-07-17 19:26           ` linuxassembly [this message]
2003-07-17 20:11             ` Maciej Hrebien
2003-07-17 22:12             ` hp
2003-07-17 12:29     ` jeff
2003-07-17 20:14       ` Konstantin Boldyshev

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=oprsgyy3sclmcbdf@smtp-server.woh.rr.com \
    --to=linuxassembly@evobsyniva.com \
    --cc=linux-assembly@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).