From owner-freebsd-questions@FreeBSD.ORG Wed Mar 10 05:55:54 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DD3716A4CE for ; Wed, 10 Mar 2004 05:55:54 -0800 (PST) Received: from mx.tele-kom.ru (mx.tele-kom.ru [213.80.148.6]) by mx1.FreeBSD.org (Postfix) with SMTP id ECF8D43D46 for ; Wed, 10 Mar 2004 05:55:52 -0800 (PST) (envelope-from doublef@tele-kom.ru) Received: (qmail 92455 invoked by uid 555); 10 Mar 2004 16:55:50 +0300 Received: from hal.localdomain (213.80.149.137) by t-k.ru with TeleMail/2 id 1078926949-92413 for jason.dictos@yosemitetech.com; Wed, 10 Mar 16:55:49 2004 +0300 (MSK) Date: Wed, 10 Mar 2004 16:50:49 +0300 From: Sergey 'DoubleF' Zaharchenko To: Jason Dictos Message-Id: <20040310165049.3595bf00@Hal.localdomain> In-Reply-To: References: X-Mailer: Sylpheed version 0.9.9claws (GTK+ 1.2.10; i386-portbld-freebsd4.8) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Signature=_Wed__10_Mar_2004_16_50_49_+0300_3Gpmt48+oi9bsC0a" cc: Dan Nelson cc: "''freebsd-questions@freebsd.org' '" Subject: Re: Using int 13 while BSD is running X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Mar 2004 13:55:54 -0000 --Signature=_Wed__10_Mar_2004_16_50_49_+0300_3Gpmt48+oi9bsC0a Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit On Tue, 9 Mar 2004 22:12:31 -0800 Jason Dictos probably wrote: > Aren't the nodes "/dev/ad[0-9] (ide) or /dev/da[0-9] (scsi/usb)" created by > their device drivers, i.e. protected mode device drives? That would mean > that I would have to make sure that the hardware is supported by a device > driver, whereas if I had raw int 13 access I would be garanteed access to > the drive the system booted from, and any other bios addressable device, > without having to load any driver for the hardware. > > -Jason Argh, I didn't get your point first. I thought your hardware wasn't supported by int 13h, and you were trying to get FreeBSD drivers to work for you in real mode... Any real HDD's out there not supported by FreeBSD but supported by BIOS'en? Somewere around then Dan Nelson probably replied: > I guess it's possible, since you have to use the bios to make VESA > video calls, and they work. /sys/i386/isa/vesa.c has most of the stuff > you would need. Also see the i386_vm86() userland function; you may not > even need to mess around inside the kernel. That's v86 mode, not real mode. Sometimes it makes a difference. It depends on how that particular BIOS was written. To Jason: take care not to *write* anything to the disk via int 13h. I still don't think I understand why you are using FreeBSD for this specific purpose. Why if you just spend time escaping from the OS? -- DoubleF All I ask is a chance to prove that money can't make me happy. --Signature=_Wed__10_Mar_2004_16_50_49_+0300_3Gpmt48+oi9bsC0a Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFATx1Fwo7hT/9lVdwRArTDAJ9EAVXw0lB0hvIiY6HlI/ZGDA4SjgCfTelP xr/dpG6x30/57n9+ekaA2eY= =Xsiw -----END PGP SIGNATURE----- --Signature=_Wed__10_Mar_2004_16_50_49_+0300_3Gpmt48+oi9bsC0a--