All of lore.kernel.org
 help / color / mirror / Atom feed
From: jeff <jko@bctonline.com>
To: linux-assembly@vger.kernel.org
Subject: Re: Keyboard and Mouse library
Date: Thu, 17 Jul 2003 05:29:34 -0700	[thread overview]
Message-ID: <200307170523.54402.jko@bctonline.com> (raw)
In-Reply-To: <oprsdu2dzklmcbdf@smtp-server.woh.rr.com>

On Tuesday 15 July 2003 08:09 pm, linuxassembly@evobsyniva.com wrote:

> sys_ioctl STDIN, KDSKBMODE, K_RAW
>
> Afterwards you'll be in raw mode.  Unfortunatly, whatever is in the kernel
> that the stty command controls is still mucking things up, and continutes
> to translate byte 13 into a byte 10, and byte 127 into a byte 8, and keeps
> all input from you until a byte 13 comes along which may be causing you to
> think it isn't working since you can't read anything from stdin.i

It is possible to turn the buffering of characters off in termios and this
works for normal reads.  My problem is an error code when trying
to set raw mode.  Here is the code

 mov  eax,54      ;ioctl
 mov ebx,0         ;stdin
 mov ecx,0x4b45  ;KDSKBMODE
 mov edx,0        ;raw mode
 int   0x80

returns code -22 which i assume is "invalid arguement"

In some sample code they opened stdin and used the
returned handle for stdin.  This did not work either.

 Cheers, jeff


  parent reply	other threads:[~2003-07-17 12:29 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
2003-07-17 20:11             ` Maciej Hrebien
2003-07-17 22:12             ` hp
2003-07-17 12:29     ` jeff [this message]
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=200307170523.54402.jko@bctonline.com \
    --to=jko@bctonline.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.