Linux assembly list
 help / color / mirror / Atom feed
From: Jack Dennon <jdennon@seasurf.net>
To: dAvId KeDrOsKy <davidkedrosky@rogers.com>
Cc: linux-assembly@vger.kernel.org
Subject: Re: int 16 ?
Date: Fri, 14 Feb 2003 12:10:50 -0800	[thread overview]
Message-ID: <3E4D4D4A.9D5A139@seasurf.net> (raw)
In-Reply-To: 200302140023.23837.davidkedrosky@rogers.com

When the PC boots up, the BIOS sets up an interrupt vector
table at 0000:0000 with int 0x16 pointing into the BIOS keyboard
driver. Linux uses this same vector table to access BIOS disk
routines that are used for booting the system. Linux then sets up
its own interrupt vector table and switches into protected mode.
None of the original BIOS interrupts are then available, nor
are they needed. There are several ways to read a single character
at a time. One of the easier ways is provided by the curses
library. Get on Amazon and look at the programming books
by Matthew & Stones, and maybe even by J. Dennon.


dAvId KeDrOsKy wrote:

> I was told there exists int 0x16, which can be used to read a single character
> at a time.  Does this interrupt exist in Linux and if so, where can I find
> some documentation on it?
>
> Thanks,
>
> Dave
> -
> To unsubscribe from this list: send the line "unsubscribe linux-assembly" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html




  parent reply	other threads:[~2003-02-14 20:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-14  5:23 int 16 ? dAvId KeDrOsKy
2003-02-14  8:07 ` Rudolf Marek
2003-02-14 20:10 ` Jack Dennon [this message]
2003-02-15 18:17   ` Rodrigo F. Baroni
2003-02-15 21:36     ` Jack Dennon
2003-02-16  6:29       ` Pea Jay

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=3E4D4D4A.9D5A139@seasurf.net \
    --to=jdennon@seasurf.net \
    --cc=davidkedrosky@rogers.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