public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafał Maj" <forlist@limcore.com>
To: linux-kernel@vger.kernel.org
Subject: Calling BIOS interrupt from kernel (and debugging / reverse engeneering)
Date: Wed, 22 Aug 2007 09:49:15 +0200	[thread overview]
Message-ID: <20070822094915.41afa2af@lore.lcone> (raw)


Hello,
I know it is not good to call BIOS interrupt from Linux (kernel nor
userspace) and we should use I/O ports instead;

But, is it at all doable? To call a BIOS interrupt from Linux kernel?

If so then how to?

In example, say we have not documented device returning data in AL
after call to interrupt 0x15 with AX=0x1234 for example; And we want to
use this BIOS interrupt and then printk() returned value in AL.

AFAIK vm86() is one step to do it, but its hard to find good complete
example at least for me.

Btw, is it possible to reverse engineering such a BIOS call? Besides
using some hardware-debugger of bus etc.

Thanks











             reply	other threads:[~2007-08-22  7:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22  7:49 Rafał Maj [this message]
2007-08-22 11:39 ` Calling BIOS interrupt from kernel (and debugging / reverse engeneering) Matthew Garrett

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=20070822094915.41afa2af@lore.lcone \
    --to=forlist@limcore.com \
    --cc=linux-kernel@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