linux-assembly.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maciej Hrebien <m_hrebien@wp.pl>
To: linux-assembly@vger.kernel.org
Subject: Re: Keyboard and Mouse library
Date: Thu, 17 Jul 2003 18:45:37 +0200	[thread overview]
Message-ID: <3F16D2B1.129DF50B@wp.pl> (raw)
In-Reply-To: oprsd8vhuulmcbdf@smtp-server.woh.rr.com

linuxassembly@evobsyniva.com wrote:
> 
> On Wed, 16 Jul 2003 07:46:30 +0100, hp <lx@lxhp.in-berlin.de> wrote:
> 
> > linuxassembly@evobsyniva.com am Mittwoch, 16. Juli 2003 04:09:
> >> On Wed, 16 Jul 2003 03:03:15 -0700, jeff <jko@save-net.com> wrote:
> >>
> >> There are some mysterious ioctls that control this as well, but they
> >> don't
> >> seem to be documented anywhere at all.  However, you can simply call the
> >
> > man 4 console_ioctl (or console_ioctls, old vers.)
> 
> The only thing I see that might apply is KDGKBENT and KDSKBSENT.  They
> might be related, but I can't tell, and suspect they are not.  There's no
> mention of anything that might remove the line buffering, or the byte 3
> leading to a sigkill thing.  As I mentioned, setting the keyboard in raw
> mode doesn't remove these things, it just mucks them up.  Instead of
> control-C sending a sigkill, it becomes the number 2 key, who's scan code
> is 3.
> 
> 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?

-- 
Maciej Hrebien


  reply	other threads:[~2003-07-17 16:45 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 [this message]
2003-07-17 19:26           ` linuxassembly
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=3F16D2B1.129DF50B@wp.pl \
    --to=m_hrebien@wp.pl \
    --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).