Date: Wed, 10 Mar 2004 08:36:56 -0800 From: Jason Dictos <jason.dictos@yosemitetech.com> To: 'Sergey 'DoubleF' Zaharchenko' <doublef@tele-kom.ru>, Jason Dictos <jason.dictos@yosemitetech.com> Cc: "''freebsd-questions@freebsd.org' '" <freebsd-questions@freebsd.org> Subject: RE: Using int 13 while BSD is running Message-ID: <E50A109EE98AA049BAA09D725DB0714F01AD3BB1@mail.tapeware.com>
next in thread | raw e-mail | index | archive | help
The goal here is simply this: To be able to write to a systems hard drive with just bios support. I dont' want to have to deal with bundling every known ide/scsi/raid adapter driver in a bsd kernel. Here's something that I found though that may be exactly what I have been looking for: http://sourceforge.net/projects/lrmi/ I'll be doing some tests with this to see how it works out. Thanks, -Jason -----Original Message----- From: Sergey 'DoubleF' Zaharchenko [mailto:doublef@tele-kom.ru] Sent: Wednesday, March 10, 2004 5:51 AM To: Jason Dictos Cc: Dan Nelson; ''freebsd-questions@freebsd.org' ' Subject: Re: Using int 13 while BSD is running On Tue, 9 Mar 2004 22:12:31 -0800 Jason Dictos <jason.dictos@yosemitetech.com> 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 <dnelson@allantgroup.com> 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. ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E50A109EE98AA049BAA09D725DB0714F01AD3BB1>