From: David Given <dg@cowlark.com>
To: Linux-8086@Vger.Kernel.Org
Subject: Re: Using int 13 calls in elks
Date: Thu, 11 Mar 2004 11:08:36 +0000 [thread overview]
Message-ID: <200403111108.36081.dg@cowlark.com> (raw)
In-Reply-To: <E50A109EE98AA049BAA09D725DB0714F01AD3BDA@mail.tapeware.com>
On Thursday 11 March 2004 05:51, you wrote:
[...]
> I have some code to port from an MSDOS based application who's main goal
> was to write partition data to a bios addressable disk. Currently under
> linux/bsd, I haven't found any way to call int 13 style calls from within
> the protected mode operating system, however I hear that elks has some bios
> disk drivers. Basically our goal with this application is to be able to
> write/read from bios addressable disks in a multi threaded environment.
>
> Can elks help me out here?
Yup; but you want to do things the Unix way, not the DOS way.
ELKS has a BIOS disk driver. /dev/bda, bdb, etc IIRC. (Names might be a little
off.) To access the disk directly, just open the device (as root), seek to
the appropriate place, and do read() and write(). Easy!
If you want to look *within* a partition, the /dev/bda1, bda2, etc point to
those.
Big Linux won't let you make BIOS calls *at all* (largely because most of the
BIOS' data structures don't exist), but there are native Linux drivers
available for practically all BIOS-addressable devices. What's the thing you
want to access?
--
+- David Given --McQ-+
| dg@cowlark.com | Quidquid latine dictum sit, altum viditur.
| (dg@tao-group.com) |
+- www.cowlark.com --+
next prev parent reply other threads:[~2004-03-11 11:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 5:51 Using int 13 calls in elks Jason Dictos
2004-03-11 11:08 ` David Given [this message]
2004-03-11 11:44 ` Gábor Lénárt
2004-03-11 18:29 ` Bill Marcum
-- strict thread matches above, loose matches on Subject: below --
2004-03-11 16:05 Jason Dictos
2004-03-11 16:22 Jason Dictos
2004-03-11 20:54 ` Alan Cox
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=200403111108.36081.dg@cowlark.com \
--to=dg@cowlark.com \
--cc=Linux-8086@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.