From: Rahul Iyer <idlisambar@gmail.com>
To: Rajat Jain <rajat.noida.india@gmail.com>
Cc: Linux Newbie <linux-newbie@vger.kernel.org>,
kernelnewbies <kernelnewbies@nl.linux.org>
Subject: Re: Issuing BIOS interrupts in Linux
Date: Fri, 04 Aug 2006 18:20:33 -0700 [thread overview]
Message-ID: <1154740833.11701.1.camel@uranium.hq.netapp.com> (raw)
In-Reply-To: <b115cb5f0608040400m7c644503p6d40bc8faea8a80a@mail.gmail.com>
In a single sentence,
"you cannot".
The reason is that bios interrupts can only be used in real mode and not
in protected mode. Linux runs in protected mode, and so this would not
be possible.
What is it you are trying to do? Maybe there's a better way to do it...
(by using the block device subsystem, for instance)
-rahul
On Fri, 2006-08-04 at 16:30 +0530, Rajat Jain wrote:
> Hi List,
>
> I want to issue BIOS interrupts in Linux (both user space & kernel
> space are fine). More specifically I want to issue BIOS interrupt 13h
> for accessing disk using the BIOS routines. How can I do so (issue the
> BIOS interrupt)?
>
> In the file /proc/interrupts on my system, the interrupt 13 h (19
> decimal) is used by some USB driver:
>
> 16: 0 Phys-irq uhci_hcd:usb1, uhci_hcd:usb4
> 17: 2 Phys-irq peth0
> 18: 637572 Phys-irq eth1
> 19: 0 Phys-irq uhci_hcd:usb2
> 20: 1275249 Phys-irq uhci_hcd:usb3
>
> So will I be able to use the BIOS routine in this case?
>
> TIA,
>
> Rajat
>
> --
> Kernelnewbies: Help each other learn about the Linux kernel.
> Archive: http://mail.nl.linux.org/kernelnewbies/
> FAQ: http://kernelnewbies.org/faq/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2006-08-05 1:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 11:00 Issuing BIOS interrupts in Linux Rajat Jain
2006-08-05 1:20 ` Rahul Iyer [this message]
[not found] ` <292693080608050553x756e4276k33c5afa80f686f44@mail.gmail.com>
2006-08-05 13:11 ` Rajat Jain
2006-08-05 14:54 ` Rik van Riel
2006-08-05 15:26 ` Rajat Jain
2006-08-05 16:33 ` Nilesh Agrawal
2006-08-09 1:50 ` David H. Lynch Jr.
2006-08-09 5:14 ` Rajat Jain
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=1154740833.11701.1.camel@uranium.hq.netapp.com \
--to=idlisambar@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-newbie@vger.kernel.org \
--cc=rajat.noida.india@gmail.com \
/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